date:20180119

apport information

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

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

Title:
  KVM + Virtio kernel panic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I received the following kernel panic on a KVM VM which is acting as
  an OpenStack compute node. I'm unable to consistently reproduce this,
  but I do consistently get various kernel panics (this is only one of
  them). Is anyone able to shed any light on what might be happening
  here?

  Ubuntu Server 16.04 cloud image.
  Kernel Version: 4.4.0-98-generic

  
  [19927.255474] general protection fault:  [#1] SMP
  [19927.256033] Modules linked in: vhost_net vhost macvtap macvlan xt_REDIRECT 
nf_nat_redirect xt_mark ip6table_mangle iptable_nat nf_nat_ipv4 nf_nat 
xt_connmark iptable_mangle ip6table_raw nf_conntrack_ipv6 xt_CT xt_mac 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_comment xt_physdev xt_set 
xt_conntrack ip_set_hash_net ip_set nfnetlink iptable_raw veth ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables 
br_netfilter bridge stp llc vport_gre ip_gre ip_tunnel gre vport_vxlan vxlan 
ip6_udp_tunnel udp_tunnel openvswitch nf_defrag_ipv6 nf_conntrack ppdev kvm_amd 
kvm input_leds serio_raw joydev irqbypass parport_pc parport ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [19927.256033] CPU: 3 PID: 2801 Comm: vna_agent Not tainted 4.4.0-98-generic 
#121-Ubuntu
  [19927.256033] Hardware name: RDO OpenStack Compute, BIOS 1.9.1-5.el7_3.3 
04/01/2014
  [19927.256033] task: 88023551c600 ti: 8800bb9ac000 task.ti: 
8800bb9ac000
  [19927.256033] RIP: 0010:[]  [] 
cmpxchg_double_slab.isra.54+0x24/0xe0
  [19927.256033] RSP: :88023fd83a40  EFLAGS: 00010206
  [19927.256033] RAX: 009a660a158b487e RBX: 880233955a00 RCX: 
c01902a30f48c088
  [19927.256033] RDX: c01902a30f48c089 RSI: 8106b846 RDI: 
4000
  [19927.256033] RBP: 88023fd83a88 R08: 880233955a00 R09: 
c01902a30f48c088
  [19927.256033] R10: 009a660a158b487e R11: 8801cf5bfc00 R12: 
009a660a158b487e
  [19927.256033] R13: 8106b846 R14:  R15: 
880237001700
  [19927.256033] FS:  7fbf85e38740() GS:88023fd8() 
knlGS:
  [19927.256033] CS:  0010 DS:  ES:  CR0: 80050033
  [19927.256033] CR2: 7ffcaa2ca468 CR3: ba76 CR4: 
003406e0
  [19927.256033] Stack:
  [19927.256033]   880233d4f008  
880233cabc80
  [19927.256033]  c9e48004 0001 88023fd83ac0 
8175ff24
  [19927.256033]  0f48c088 88023fd83b50 811ef3fb 
880233d4f008
  [19927.256033] Call Trace:
  [19927.256033]  
  [19927.256033]  [] ? sch_direct_xmit+0x74/0x220
  [19927.256033]  [] __slab_free+0xcb/0x2c0
  [19927.256033]  [] ? __dev_queue_xmit+0x286/0x590
  [19927.256033]  [] kmem_cache_free+0x1d4/0x1e0
  [19927.256033]  [] kfree_skbmem+0x59/0x60
  [19927.256033]  [] consume_skb+0x34/0x90
  [19927.256033]  [] arp_process+0x80/0x750
  [19927.256033]  [] arp_rcv+0x133/0x1c0
  [19927.256033]  [] ? packet_rcv+0x44/0x440
  [19927.256033]  [] __netif_receive_skb_core+0x704/0xa60
  [19927.256033]  [] ? __build_skb+0x2a/0xe0
  [19927.256033]  [] __netif_receive_skb+0x18/0x60
  [19927.256033]  [] netif_receive_skb_internal+0x32/0xa0
  [19927.256033]  [] napi_gro_receive+0xc3/0xf0
  [19927.256033]  [] virtnet_receive+0x4a6/0x8f0
  [19927.256033]  [] virtnet_poll+0x1d/0x80
  [19927.256033]  [] net_rx_action+0x21e/0x360
  [19927.256033]  [] ? skb_recv_done+0x43/0x50
  [19927.256033]  [] __do_softirq+0x101/0x290
  [19927.256033]  [] irq_exit+0xa3/0xb0
  [19927.256033]  [] do_IRQ+0x54/0xd0
  [19927.256033]  [] common_interrupt+0x82/0x82
  [19927.256033]  
  [19927.256033]  [] ? native_safe_halt+0x6/0x10
  [19927.256033]  [] kvm_wait+0x52/0x60
  [19927.256033]  [] 
__pv_queued_spin_lock_slowpath+0x1d6/0x210
  [19927.256033]  [] _raw_spin_lock+0x21/0x30
  [19927.256033]  [] handle_mm_fault+0x60b/0x1820
  [19927.256033]  [] ? hrtimer_try_to_cancel+0x29/0x130
  [19927.256033]  [] ? do_nanosleep+0x96/0xf0
  [19927.256033]  [] ? hrtimer_nanosleep+0xdc/0x210
  [19927.256033]  [] __do_page_fault+0x197/0x400
  [19927.256033]  [] trace_do_page_fault+0x37/0xe0
  [19927.256033]  [] do_async_page_fault+0x19/0x70
  [19927.256033]  [] async_page_fault+0x28/0x30

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

apport information

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

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

Title:
  KVM + Virtio kernel panic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I received the following kernel panic on a KVM VM which is acting as
  an OpenStack compute node. I'm unable to consistently reproduce this,
  but I do consistently get various kernel panics (this is only one of
  them). Is anyone able to shed any light on what might be happening
  here?

  Ubuntu Server 16.04 cloud image.
  Kernel Version: 4.4.0-98-generic

  
  [19927.255474] general protection fault:  [#1] SMP
  [19927.256033] Modules linked in: vhost_net vhost macvtap macvlan xt_REDIRECT 
nf_nat_redirect xt_mark ip6table_mangle iptable_nat nf_nat_ipv4 nf_nat 
xt_connmark iptable_mangle ip6table_raw nf_conntrack_ipv6 xt_CT xt_mac 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_comment xt_physdev xt_set 
xt_conntrack ip_set_hash_net ip_set nfnetlink iptable_raw veth ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables 
br_netfilter bridge stp llc vport_gre ip_gre ip_tunnel gre vport_vxlan vxlan 
ip6_udp_tunnel udp_tunnel openvswitch nf_defrag_ipv6 nf_conntrack ppdev kvm_amd 
kvm input_leds serio_raw joydev irqbypass parport_pc parport ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [19927.256033] CPU: 3 PID: 2801 Comm: vna_agent Not tainted 4.4.0-98-generic 
#121-Ubuntu
  [19927.256033] Hardware name: RDO OpenStack Compute, BIOS 1.9.1-5.el7_3.3 
04/01/2014
  [19927.256033] task: 88023551c600 ti: 8800bb9ac000 task.ti: 
8800bb9ac000
  [19927.256033] RIP: 0010:[]  [] 
cmpxchg_double_slab.isra.54+0x24/0xe0
  [19927.256033] RSP: :88023fd83a40  EFLAGS: 00010206
  [19927.256033] RAX: 009a660a158b487e RBX: 880233955a00 RCX: 
c01902a30f48c088
  [19927.256033] RDX: c01902a30f48c089 RSI: 8106b846 RDI: 
4000
  [19927.256033] RBP: 88023fd83a88 R08: 880233955a00 R09: 
c01902a30f48c088
  [19927.256033] R10: 009a660a158b487e R11: 8801cf5bfc00 R12: 
009a660a158b487e
  [19927.256033] R13: 8106b846 R14:  R15: 
880237001700
  [19927.256033] FS:  7fbf85e38740() GS:88023fd8() 
knlGS:
  [19927.256033] CS:  0010 DS:  ES:  CR0: 80050033
  [19927.256033] CR2: 7ffcaa2ca468 CR3: ba76 CR4: 
003406e0
  [19927.256033] Stack:
  [19927.256033]   880233d4f008  
880233cabc80
  [19927.256033]  c9e48004 0001 88023fd83ac0 
8175ff24
  [19927.256033]  0f48c088 88023fd83b50 811ef3fb 
880233d4f008
  [19927.256033] Call Trace:
  [19927.256033]  
  [19927.256033]  [] ? sch_direct_xmit+0x74/0x220
  [19927.256033]  [] __slab_free+0xcb/0x2c0
  [19927.256033]  [] ? __dev_queue_xmit+0x286/0x590
  [19927.256033]  [] kmem_cache_free+0x1d4/0x1e0
  [19927.256033]  [] kfree_skbmem+0x59/0x60
  [19927.256033]  [] consume_skb+0x34/0x90
  [19927.256033]  [] arp_process+0x80/0x750
  [19927.256033]  [] arp_rcv+0x133/0x1c0
  [19927.256033]  [] ? packet_rcv+0x44/0x440
  [19927.256033]  [] __netif_receive_skb_core+0x704/0xa60
  [19927.256033]  [] ? __build_skb+0x2a/0xe0
  [19927.256033]  [] __netif_receive_skb+0x18/0x60
  [19927.256033]  [] netif_receive_skb_internal+0x32/0xa0
  [19927.256033]  [] napi_gro_receive+0xc3/0xf0
  [19927.256033]  [] virtnet_receive+0x4a6/0x8f0
  [19927.256033]  [] virtnet_poll+0x1d/0x80
  [19927.256033]  [] net_rx_action+0x21e/0x360
  [19927.256033]  [] ? skb_recv_done+0x43/0x50
  [19927.256033]  [] __do_softirq+0x101/0x290
  [19927.256033]  [] irq_exit+0xa3/0xb0
  [19927.256033]  [] do_IRQ+0x54/0xd0
  [19927.256033]  [] common_interrupt+0x82/0x82
  [19927.256033]  
  [19927.256033]  [] ? native_safe_halt+0x6/0x10
  [19927.256033]  [] kvm_wait+0x52/0x60
  [19927.256033]  [] 
__pv_queued_spin_lock_slowpath+0x1d6/0x210
  [19927.256033]  [] _raw_spin_lock+0x21/0x30
  [19927.256033]  [] handle_mm_fault+0x60b/0x1820
  [19927.256033]  [] ? hrtimer_try_to_cancel+0x29/0x130
  [19927.256033]  [] ? do_nanosleep+0x96/0xf0
  [19927.256033]  [] ? hrtimer_nanosleep+0xdc/0x210
  [19927.256033]  [] __do_page_fault+0x197/0x400
  [19927.256033]  [] trace_do_page_fault+0x37/0xe0
  [19927.256033]  [] do_async_page_fault+0x19/0x70
  [19927.256033]  [] async_page_fault+0x28/0x30
  [19927.256033] Code: 0f 1f 80 00 00

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

apport information

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

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

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

Title:
  KVM + Virtio kernel panic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I received the following kernel panic on a KVM VM which is acting as
  an OpenStack compute node. I'm unable to consistently reproduce this,
  but I do consistently get various kernel panics (this is only one of
  them). Is anyone able to shed any light on what might be happening
  here?

  Ubuntu Server 16.04 cloud image.
  Kernel Version: 4.4.0-98-generic

  
  [19927.255474] general protection fault:  [#1] SMP
  [19927.256033] Modules linked in: vhost_net vhost macvtap macvlan xt_REDIRECT 
nf_nat_redirect xt_mark ip6table_mangle iptable_nat nf_nat_ipv4 nf_nat 
xt_connmark iptable_mangle ip6table_raw nf_conntrack_ipv6 xt_CT xt_mac 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_comment xt_physdev xt_set 
xt_conntrack ip_set_hash_net ip_set nfnetlink iptable_raw veth ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables 
br_netfilter bridge stp llc vport_gre ip_gre ip_tunnel gre vport_vxlan vxlan 
ip6_udp_tunnel udp_tunnel openvswitch nf_defrag_ipv6 nf_conntrack ppdev kvm_amd 
kvm input_leds serio_raw joydev irqbypass parport_pc parport ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [19927.256033] CPU: 3 PID: 2801 Comm: vna_agent Not tainted 4.4.0-98-generic 
#121-Ubuntu
  [19927.256033] Hardware name: RDO OpenStack Compute, BIOS 1.9.1-5.el7_3.3 
04/01/2014
  [19927.256033] task: 88023551c600 ti: 8800bb9ac000 task.ti: 
8800bb9ac000
  [19927.256033] RIP: 0010:[]  [] 
cmpxchg_double_slab.isra.54+0x24/0xe0
  [19927.256033] RSP: :88023fd83a40  EFLAGS: 00010206
  [19927.256033] RAX: 009a660a158b487e RBX: 880233955a00 RCX: 
c01902a30f48c088
  [19927.256033] RDX: c01902a30f48c089 RSI: 8106b846 RDI: 
4000
  [19927.256033] RBP: 88023fd83a88 R08: 880233955a00 R09: 
c01902a30f48c088
  [19927.256033] R10: 009a660a158b487e R11: 8801cf5bfc00 R12: 
009a660a158b487e
  [19927.256033] R13: 8106b846 R14:  R15: 
880237001700
  [19927.256033] FS:  7fbf85e38740() GS:88023fd8() 
knlGS:
  [19927.256033] CS:  0010 DS:  ES:  CR0: 80050033
  [19927.256033] CR2: 7ffcaa2ca468 CR3: ba76 CR4: 
003406e0
  [19927.256033] Stack:
  [19927.256033]   880233d4f008  
880233cabc80
  [19927.256033]  c9e48004 0001 88023fd83ac0 
8175ff24
  [19927.256033]  0f48c088 88023fd83b50 811ef3fb 
880233d4f008
  [19927.256033] Call Trace:
  [19927.256033]  
  [19927.256033]  [] ? sch_direct_xmit+0x74/0x220
  [19927.256033]  [] __slab_free+0xcb/0x2c0
  [19927.256033]  [] ? __dev_queue_xmit+0x286/0x590
  [19927.256033]  [] kmem_cache_free+0x1d4/0x1e0
  [19927.256033]  [] kfree_skbmem+0x59/0x60
  [19927.256033]  [] consume_skb+0x34/0x90
  [19927.256033]  [] arp_process+0x80/0x750
  [19927.256033]  [] arp_rcv+0x133/0x1c0
  [19927.256033]  [] ? packet_rcv+0x44/0x440
  [19927.256033]  [] __netif_receive_skb_core+0x704/0xa60
  [19927.256033]  [] ? __build_skb+0x2a/0xe0
  [19927.256033]  [] __netif_receive_skb+0x18/0x60
  [19927.256033]  [] netif_receive_skb_internal+0x32/0xa0
  [19927.256033]  [] napi_gro_receive+0xc3/0xf0
  [19927.256033]  [] virtnet_receive+0x4a6/0x8f0
  [19927.256033]  [] virtnet_poll+0x1d/0x80
  [19927.256033]  [] net_rx_action+0x21e/0x360
  [19927.256033]  [] ? skb_recv_done+0x43/0x50
  [19927.256033]  [] __do_softirq+0x101/0x290
  [19927.256033]  [] irq_exit+0xa3/0xb0
  [19927.256033]  [] do_IRQ+0x54/0xd0
  [19927.256033]  [] common_interrupt+0x82/0x82
  [19927.256033]  
  [19927.256033]  [] ? native_safe_halt+0x6/0x10
  [19927.256033]  [] kvm_wait+0x52/0x60
  [19927.256033]  [] 
__pv_queued_spin_lock_slowpath+0x1d6/0x210
  [19927.256033]  [] _raw_spin_lock+0x21/0x30
  [19927.256033]  [] handle_mm_fault+0x60b/0x1820
  [19927.256033]  [] ? hrtimer_try_to_cancel+0x29/0x130
  [19927.256033]  [] ? do_nanosleep+0x96/0xf0
  [19927.256033]  [] ? hrtimer_nanosleep+0xdc/0x210
  [19927.256033]  [] __do_page_fault+0x197/0x400
  [19927.256033]  [] trace_do_page_fault+0x37/0xe0
  [19927.256033]  [] do_async_page_fault+0x19/0x70

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

apport information

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

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

Title:
  KVM + Virtio kernel panic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I received the following kernel panic on a KVM VM which is acting as
  an OpenStack compute node. I'm unable to consistently reproduce this,
  but I do consistently get various kernel panics (this is only one of
  them). Is anyone able to shed any light on what might be happening
  here?

  Ubuntu Server 16.04 cloud image.
  Kernel Version: 4.4.0-98-generic

  
  [19927.255474] general protection fault:  [#1] SMP
  [19927.256033] Modules linked in: vhost_net vhost macvtap macvlan xt_REDIRECT 
nf_nat_redirect xt_mark ip6table_mangle iptable_nat nf_nat_ipv4 nf_nat 
xt_connmark iptable_mangle ip6table_raw nf_conntrack_ipv6 xt_CT xt_mac 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_comment xt_physdev xt_set 
xt_conntrack ip_set_hash_net ip_set nfnetlink iptable_raw veth ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables 
br_netfilter bridge stp llc vport_gre ip_gre ip_tunnel gre vport_vxlan vxlan 
ip6_udp_tunnel udp_tunnel openvswitch nf_defrag_ipv6 nf_conntrack ppdev kvm_amd 
kvm input_leds serio_raw joydev irqbypass parport_pc parport ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [19927.256033] CPU: 3 PID: 2801 Comm: vna_agent Not tainted 4.4.0-98-generic 
#121-Ubuntu
  [19927.256033] Hardware name: RDO OpenStack Compute, BIOS 1.9.1-5.el7_3.3 
04/01/2014
  [19927.256033] task: 88023551c600 ti: 8800bb9ac000 task.ti: 
8800bb9ac000
  [19927.256033] RIP: 0010:[]  [] 
cmpxchg_double_slab.isra.54+0x24/0xe0
  [19927.256033] RSP: :88023fd83a40  EFLAGS: 00010206
  [19927.256033] RAX: 009a660a158b487e RBX: 880233955a00 RCX: 
c01902a30f48c088
  [19927.256033] RDX: c01902a30f48c089 RSI: 8106b846 RDI: 
4000
  [19927.256033] RBP: 88023fd83a88 R08: 880233955a00 R09: 
c01902a30f48c088
  [19927.256033] R10: 009a660a158b487e R11: 8801cf5bfc00 R12: 
009a660a158b487e
  [19927.256033] R13: 8106b846 R14:  R15: 
880237001700
  [19927.256033] FS:  7fbf85e38740() GS:88023fd8() 
knlGS:
  [19927.256033] CS:  0010 DS:  ES:  CR0: 80050033
  [19927.256033] CR2: 7ffcaa2ca468 CR3: ba76 CR4: 
003406e0
  [19927.256033] Stack:
  [19927.256033]   880233d4f008  
880233cabc80
  [19927.256033]  c9e48004 0001 88023fd83ac0 
8175ff24
  [19927.256033]  0f48c088 88023fd83b50 811ef3fb 
880233d4f008
  [19927.256033] Call Trace:
  [19927.256033]  
  [19927.256033]  [] ? sch_direct_xmit+0x74/0x220
  [19927.256033]  [] __slab_free+0xcb/0x2c0
  [19927.256033]  [] ? __dev_queue_xmit+0x286/0x590
  [19927.256033]  [] kmem_cache_free+0x1d4/0x1e0
  [19927.256033]  [] kfree_skbmem+0x59/0x60
  [19927.256033]  [] consume_skb+0x34/0x90
  [19927.256033]  [] arp_process+0x80/0x750
  [19927.256033]  [] arp_rcv+0x133/0x1c0
  [19927.256033]  [] ? packet_rcv+0x44/0x440
  [19927.256033]  [] __netif_receive_skb_core+0x704/0xa60
  [19927.256033]  [] ? __build_skb+0x2a/0xe0
  [19927.256033]  [] __netif_receive_skb+0x18/0x60
  [19927.256033]  [] netif_receive_skb_internal+0x32/0xa0
  [19927.256033]  [] napi_gro_receive+0xc3/0xf0
  [19927.256033]  [] virtnet_receive+0x4a6/0x8f0
  [19927.256033]  [] virtnet_poll+0x1d/0x80
  [19927.256033]  [] net_rx_action+0x21e/0x360
  [19927.256033]  [] ? skb_recv_done+0x43/0x50
  [19927.256033]  [] __do_softirq+0x101/0x290
  [19927.256033]  [] irq_exit+0xa3/0xb0
  [19927.256033]  [] do_IRQ+0x54/0xd0
  [19927.256033]  [] common_interrupt+0x82/0x82
  [19927.256033]  
  [19927.256033]  [] ? native_safe_halt+0x6/0x10
  [19927.256033]  [] kvm_wait+0x52/0x60
  [19927.256033]  [] 
__pv_queued_spin_lock_slowpath+0x1d6/0x210
  [19927.256033]  [] _raw_spin_lock+0x21/0x30
  [19927.256033]  [] handle_mm_fault+0x60b/0x1820
  [19927.256033]  [] ? hrtimer_try_to_cancel+0x29/0x130
  [19927.256033]  [] ? do_nanosleep+0x96/0xf0
  [19927.256033]  [] ? hrtimer_nanosleep+0xdc/0x210
  [19927.256033]  [] __do_page_fault+0x197/0x400
  [19927.256033]  [] trace_do_page_fault+0x37/0xe0
  [19927.256033]  [] do_async_page_fault+0x19/0x70
  [19927.256033]  [] async_page_fault+0x28/0x30
  [19927.256033] Code: 0f 1f

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

apport information

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

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

Title:
  KVM + Virtio kernel panic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I received the following kernel panic on a KVM VM which is acting as
  an OpenStack compute node. I'm unable to consistently reproduce this,
  but I do consistently get various kernel panics (this is only one of
  them). Is anyone able to shed any light on what might be happening
  here?

  Ubuntu Server 16.04 cloud image.
  Kernel Version: 4.4.0-98-generic

  
  [19927.255474] general protection fault:  [#1] SMP
  [19927.256033] Modules linked in: vhost_net vhost macvtap macvlan xt_REDIRECT 
nf_nat_redirect xt_mark ip6table_mangle iptable_nat nf_nat_ipv4 nf_nat 
xt_connmark iptable_mangle ip6table_raw nf_conntrack_ipv6 xt_CT xt_mac 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_comment xt_physdev xt_set 
xt_conntrack ip_set_hash_net ip_set nfnetlink iptable_raw veth ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables 
br_netfilter bridge stp llc vport_gre ip_gre ip_tunnel gre vport_vxlan vxlan 
ip6_udp_tunnel udp_tunnel openvswitch nf_defrag_ipv6 nf_conntrack ppdev kvm_amd 
kvm input_leds serio_raw joydev irqbypass parport_pc parport ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [19927.256033] CPU: 3 PID: 2801 Comm: vna_agent Not tainted 4.4.0-98-generic 
#121-Ubuntu
  [19927.256033] Hardware name: RDO OpenStack Compute, BIOS 1.9.1-5.el7_3.3 
04/01/2014
  [19927.256033] task: 88023551c600 ti: 8800bb9ac000 task.ti: 
8800bb9ac000
  [19927.256033] RIP: 0010:[]  [] 
cmpxchg_double_slab.isra.54+0x24/0xe0
  [19927.256033] RSP: :88023fd83a40  EFLAGS: 00010206
  [19927.256033] RAX: 009a660a158b487e RBX: 880233955a00 RCX: 
c01902a30f48c088
  [19927.256033] RDX: c01902a30f48c089 RSI: 8106b846 RDI: 
4000
  [19927.256033] RBP: 88023fd83a88 R08: 880233955a00 R09: 
c01902a30f48c088
  [19927.256033] R10: 009a660a158b487e R11: 8801cf5bfc00 R12: 
009a660a158b487e
  [19927.256033] R13: 8106b846 R14:  R15: 
880237001700
  [19927.256033] FS:  7fbf85e38740() GS:88023fd8() 
knlGS:
  [19927.256033] CS:  0010 DS:  ES:  CR0: 80050033
  [19927.256033] CR2: 7ffcaa2ca468 CR3: ba76 CR4: 
003406e0
  [19927.256033] Stack:
  [19927.256033]   880233d4f008  
880233cabc80
  [19927.256033]  c9e48004 0001 88023fd83ac0 
8175ff24
  [19927.256033]  0f48c088 88023fd83b50 811ef3fb 
880233d4f008
  [19927.256033] Call Trace:
  [19927.256033]  
  [19927.256033]  [] ? sch_direct_xmit+0x74/0x220
  [19927.256033]  [] __slab_free+0xcb/0x2c0
  [19927.256033]  [] ? __dev_queue_xmit+0x286/0x590
  [19927.256033]  [] kmem_cache_free+0x1d4/0x1e0
  [19927.256033]  [] kfree_skbmem+0x59/0x60
  [19927.256033]  [] consume_skb+0x34/0x90
  [19927.256033]  [] arp_process+0x80/0x750
  [19927.256033]  [] arp_rcv+0x133/0x1c0
  [19927.256033]  [] ? packet_rcv+0x44/0x440
  [19927.256033]  [] __netif_receive_skb_core+0x704/0xa60
  [19927.256033]  [] ? __build_skb+0x2a/0xe0
  [19927.256033]  [] __netif_receive_skb+0x18/0x60
  [19927.256033]  [] netif_receive_skb_internal+0x32/0xa0
  [19927.256033]  [] napi_gro_receive+0xc3/0xf0
  [19927.256033]  [] virtnet_receive+0x4a6/0x8f0
  [19927.256033]  [] virtnet_poll+0x1d/0x80
  [19927.256033]  [] net_rx_action+0x21e/0x360
  [19927.256033]  [] ? skb_recv_done+0x43/0x50
  [19927.256033]  [] __do_softirq+0x101/0x290
  [19927.256033]  [] irq_exit+0xa3/0xb0
  [19927.256033]  [] do_IRQ+0x54/0xd0
  [19927.256033]  [] common_interrupt+0x82/0x82
  [19927.256033]  
  [19927.256033]  [] ? native_safe_halt+0x6/0x10
  [19927.256033]  [] kvm_wait+0x52/0x60
  [19927.256033]  [] 
__pv_queued_spin_lock_slowpath+0x1d6/0x210
  [19927.256033]  [] _raw_spin_lock+0x21/0x30
  [19927.256033]  [] handle_mm_fault+0x60b/0x1820
  [19927.256033]  [] ? hrtimer_try_to_cancel+0x29/0x130
  [19927.256033]  [] ? do_nanosleep+0x96/0xf0
  [19927.256033]  [] ? hrtimer_nanosleep+0xdc/0x210
  [19927.256033]  [] __do_page_fault+0x197/0x400
  [19927.256033]  [] trace_do_page_fault+0x37/0xe0
  [19927.256033]  [] do_async_page_fault+0x19/0x70
  [19927.256033]  [] async_page_fault+0x28/0x30
  [19927.256033] Code:

[Kernel-packages] [Bug 1744169] Re: KVM + Virtio kernel panic

apport information

** Tags added: apport-collected ec2-images

** Description changed:

  I received the following kernel panic on a KVM VM which is acting as an
  OpenStack compute node. I'm unable to consistently reproduce this, but I
  do consistently get various kernel panics (this is only one of them). Is
  anyone able to shed any light on what might be happening here?
  
  Ubuntu Server 16.04 cloud image.
  Kernel Version: 4.4.0-98-generic
  
  
  [19927.255474] general protection fault:  [#1] SMP
  [19927.256033] Modules linked in: vhost_net vhost macvtap macvlan xt_REDIRECT 
nf_nat_redirect xt_mark ip6table_mangle iptable_nat nf_nat_ipv4 nf_nat 
xt_connmark iptable_mangle ip6table_raw nf_conntrack_ipv6 xt_CT xt_mac 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_comment xt_physdev xt_set 
xt_conntrack ip_set_hash_net ip_set nfnetlink iptable_raw veth ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables 
br_netfilter bridge stp llc vport_gre ip_gre ip_tunnel gre vport_vxlan vxlan 
ip6_udp_tunnel udp_tunnel openvswitch nf_defrag_ipv6 nf_conntrack ppdev kvm_amd 
kvm input_leds serio_raw joydev irqbypass parport_pc parport ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [19927.256033] CPU: 3 PID: 2801 Comm: vna_agent Not tainted 4.4.0-98-generic 
#121-Ubuntu
  [19927.256033] Hardware name: RDO OpenStack Compute, BIOS 1.9.1-5.el7_3.3 
04/01/2014
  [19927.256033] task: 88023551c600 ti: 8800bb9ac000 task.ti: 
8800bb9ac000
  [19927.256033] RIP: 0010:[]  [] 
cmpxchg_double_slab.isra.54+0x24/0xe0
  [19927.256033] RSP: :88023fd83a40  EFLAGS: 00010206
  [19927.256033] RAX: 009a660a158b487e RBX: 880233955a00 RCX: 
c01902a30f48c088
  [19927.256033] RDX: c01902a30f48c089 RSI: 8106b846 RDI: 
4000
  [19927.256033] RBP: 88023fd83a88 R08: 880233955a00 R09: 
c01902a30f48c088
  [19927.256033] R10: 009a660a158b487e R11: 8801cf5bfc00 R12: 
009a660a158b487e
  [19927.256033] R13: 8106b846 R14:  R15: 
880237001700
  [19927.256033] FS:  7fbf85e38740() GS:88023fd8() 
knlGS:
  [19927.256033] CS:  0010 DS:  ES:  CR0: 80050033
  [19927.256033] CR2: 7ffcaa2ca468 CR3: ba76 CR4: 
003406e0
  [19927.256033] Stack:
  [19927.256033]   880233d4f008  
880233cabc80
  [19927.256033]  c9e48004 0001 88023fd83ac0 
8175ff24
  [19927.256033]  0f48c088 88023fd83b50 811ef3fb 
880233d4f008
  [19927.256033] Call Trace:
  [19927.256033]  
  [19927.256033]  [] ? sch_direct_xmit+0x74/0x220
  [19927.256033]  [] __slab_free+0xcb/0x2c0
  [19927.256033]  [] ? __dev_queue_xmit+0x286/0x590
  [19927.256033]  [] kmem_cache_free+0x1d4/0x1e0
  [19927.256033]  [] kfree_skbmem+0x59/0x60
  [19927.256033]  [] consume_skb+0x34/0x90
  [19927.256033]  [] arp_process+0x80/0x750
  [19927.256033]  [] arp_rcv+0x133/0x1c0
  [19927.256033]  [] ? packet_rcv+0x44/0x440
  [19927.256033]  [] __netif_receive_skb_core+0x704/0xa60
  [19927.256033]  [] ? __build_skb+0x2a/0xe0
  [19927.256033]  [] __netif_receive_skb+0x18/0x60
  [19927.256033]  [] netif_receive_skb_internal+0x32/0xa0
  [19927.256033]  [] napi_gro_receive+0xc3/0xf0
  [19927.256033]  [] virtnet_receive+0x4a6/0x8f0
  [19927.256033]  [] virtnet_poll+0x1d/0x80
  [19927.256033]  [] net_rx_action+0x21e/0x360
  [19927.256033]  [] ? skb_recv_done+0x43/0x50
  [19927.256033]  [] __do_softirq+0x101/0x290
  [19927.256033]  [] irq_exit+0xa3/0xb0
  [19927.256033]  [] do_IRQ+0x54/0xd0
  [19927.256033]  [] common_interrupt+0x82/0x82
  [19927.256033]  
  [19927.256033]  [] ? native_safe_halt+0x6/0x10
  [19927.256033]  [] kvm_wait+0x52/0x60
  [19927.256033]  [] 
__pv_queued_spin_lock_slowpath+0x1d6/0x210
  [19927.256033]  [] _raw_spin_lock+0x21/0x30
  [19927.256033]  [] handle_mm_fault+0x60b/0x1820
  [19927.256033]  [] ? hrtimer_try_to_cancel+0x29/0x130
  [19927.256033]  [] ? do_nanosleep+0x96/0xf0
  [19927.256033]  [] ? hrtimer_nanosleep+0xdc/0x210
  [19927.256033]  [] __do_page_fault+0x197/0x400
  [19927.256033]  [] trace_do_page_fault+0x37/0xe0
  [19927.256033]  [] do_async_page_fault+0x19/0x70
  [19927.256033]  [] async_page_fault+0x28/0x30
  [19927.256033] Code: 0f 1f 80 00 00 00 00 55 49 89 d2 48 89 e5 53 48 83 e4 f0 
48 83 ec 40 f7 c7 00 00 00 40 74 2c 48 89 ca 4c 89 d0 4c 89 c3 4c 89 c9  48 
0f c7 4e 10 0f 94 c0 41 89 c0 b8 01 00 00 00 45 84 c0 75
  [19927.256033] RIP  [] cmpxchg_double_slab.isra.54+0x24/0xe0
  [19927.256033]  RSP 
  [19927.296033] general protection fault:

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

apport information

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

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

Title:
  KVM + Virtio kernel panic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I received the following kernel panic on a KVM VM which is acting as
  an OpenStack compute node. I'm unable to consistently reproduce this,
  but I do consistently get various kernel panics (this is only one of
  them). Is anyone able to shed any light on what might be happening
  here?

  Ubuntu Server 16.04 cloud image.
  Kernel Version: 4.4.0-98-generic

  
  [19927.255474] general protection fault:  [#1] SMP
  [19927.256033] Modules linked in: vhost_net vhost macvtap macvlan xt_REDIRECT 
nf_nat_redirect xt_mark ip6table_mangle iptable_nat nf_nat_ipv4 nf_nat 
xt_connmark iptable_mangle ip6table_raw nf_conntrack_ipv6 xt_CT xt_mac 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_comment xt_physdev xt_set 
xt_conntrack ip_set_hash_net ip_set nfnetlink iptable_raw veth ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables 
br_netfilter bridge stp llc vport_gre ip_gre ip_tunnel gre vport_vxlan vxlan 
ip6_udp_tunnel udp_tunnel openvswitch nf_defrag_ipv6 nf_conntrack ppdev kvm_amd 
kvm input_leds serio_raw joydev irqbypass parport_pc parport ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [19927.256033] CPU: 3 PID: 2801 Comm: vna_agent Not tainted 4.4.0-98-generic 
#121-Ubuntu
  [19927.256033] Hardware name: RDO OpenStack Compute, BIOS 1.9.1-5.el7_3.3 
04/01/2014
  [19927.256033] task: 88023551c600 ti: 8800bb9ac000 task.ti: 
8800bb9ac000
  [19927.256033] RIP: 0010:[]  [] 
cmpxchg_double_slab.isra.54+0x24/0xe0
  [19927.256033] RSP: :88023fd83a40  EFLAGS: 00010206
  [19927.256033] RAX: 009a660a158b487e RBX: 880233955a00 RCX: 
c01902a30f48c088
  [19927.256033] RDX: c01902a30f48c089 RSI: 8106b846 RDI: 
4000
  [19927.256033] RBP: 88023fd83a88 R08: 880233955a00 R09: 
c01902a30f48c088
  [19927.256033] R10: 009a660a158b487e R11: 8801cf5bfc00 R12: 
009a660a158b487e
  [19927.256033] R13: 8106b846 R14:  R15: 
880237001700
  [19927.256033] FS:  7fbf85e38740() GS:88023fd8() 
knlGS:
  [19927.256033] CS:  0010 DS:  ES:  CR0: 80050033
  [19927.256033] CR2: 7ffcaa2ca468 CR3: ba76 CR4: 
003406e0
  [19927.256033] Stack:
  [19927.256033]   880233d4f008  
880233cabc80
  [19927.256033]  c9e48004 0001 88023fd83ac0 
8175ff24
  [19927.256033]  0f48c088 88023fd83b50 811ef3fb 
880233d4f008
  [19927.256033] Call Trace:
  [19927.256033]  
  [19927.256033]  [] ? sch_direct_xmit+0x74/0x220
  [19927.256033]  [] __slab_free+0xcb/0x2c0
  [19927.256033]  [] ? __dev_queue_xmit+0x286/0x590
  [19927.256033]  [] kmem_cache_free+0x1d4/0x1e0
  [19927.256033]  [] kfree_skbmem+0x59/0x60
  [19927.256033]  [] consume_skb+0x34/0x90
  [19927.256033]  [] arp_process+0x80/0x750
  [19927.256033]  [] arp_rcv+0x133/0x1c0
  [19927.256033]  [] ? packet_rcv+0x44/0x440
  [19927.256033]  [] __netif_receive_skb_core+0x704/0xa60
  [19927.256033]  [] ? __build_skb+0x2a/0xe0
  [19927.256033]  [] __netif_receive_skb+0x18/0x60
  [19927.256033]  [] netif_receive_skb_internal+0x32/0xa0
  [19927.256033]  [] napi_gro_receive+0xc3/0xf0
  [19927.256033]  [] virtnet_receive+0x4a6/0x8f0
  [19927.256033]  [] virtnet_poll+0x1d/0x80
  [19927.256033]  [] net_rx_action+0x21e/0x360
  [19927.256033]  [] ? skb_recv_done+0x43/0x50
  [19927.256033]  [] __do_softirq+0x101/0x290
  [19927.256033]  [] irq_exit+0xa3/0xb0
  [19927.256033]  [] do_IRQ+0x54/0xd0
  [19927.256033]  [] common_interrupt+0x82/0x82
  [19927.256033]  
  [19927.256033]  [] ? native_safe_halt+0x6/0x10
  [19927.256033]  [] kvm_wait+0x52/0x60
  [19927.256033]  [] 
__pv_queued_spin_lock_slowpath+0x1d6/0x210
  [19927.256033]  [] _raw_spin_lock+0x21/0x30
  [19927.256033]  [] handle_mm_fault+0x60b/0x1820
  [19927.256033]  [] ? hrtimer_try_to_cancel+0x29/0x130
  [19927.256033]  [] ? do_nanosleep+0x96/0xf0
  [19927.256033]  [] ? hrtimer_nanosleep+0xdc/0x210
  [19927.256033]  [] __do_page_fault+0x197/0x400
  [19927.256033]  [] trace_do_page_fault+0x37/0xe0
  [19927.256033]  [] do_async_page_fault+0x19/0x70
  [19927.256033]  [] async_page_fault+0x28/0x30
  [19927.256033] Code:

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

apport information

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

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

Title:
  KVM + Virtio kernel panic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I received the following kernel panic on a KVM VM which is acting as
  an OpenStack compute node. I'm unable to consistently reproduce this,
  but I do consistently get various kernel panics (this is only one of
  them). Is anyone able to shed any light on what might be happening
  here?

  Ubuntu Server 16.04 cloud image.
  Kernel Version: 4.4.0-98-generic

  
  [19927.255474] general protection fault:  [#1] SMP
  [19927.256033] Modules linked in: vhost_net vhost macvtap macvlan xt_REDIRECT 
nf_nat_redirect xt_mark ip6table_mangle iptable_nat nf_nat_ipv4 nf_nat 
xt_connmark iptable_mangle ip6table_raw nf_conntrack_ipv6 xt_CT xt_mac 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_comment xt_physdev xt_set 
xt_conntrack ip_set_hash_net ip_set nfnetlink iptable_raw veth ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables 
br_netfilter bridge stp llc vport_gre ip_gre ip_tunnel gre vport_vxlan vxlan 
ip6_udp_tunnel udp_tunnel openvswitch nf_defrag_ipv6 nf_conntrack ppdev kvm_amd 
kvm input_leds serio_raw joydev irqbypass parport_pc parport ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [19927.256033] CPU: 3 PID: 2801 Comm: vna_agent Not tainted 4.4.0-98-generic 
#121-Ubuntu
  [19927.256033] Hardware name: RDO OpenStack Compute, BIOS 1.9.1-5.el7_3.3 
04/01/2014
  [19927.256033] task: 88023551c600 ti: 8800bb9ac000 task.ti: 
8800bb9ac000
  [19927.256033] RIP: 0010:[]  [] 
cmpxchg_double_slab.isra.54+0x24/0xe0
  [19927.256033] RSP: :88023fd83a40  EFLAGS: 00010206
  [19927.256033] RAX: 009a660a158b487e RBX: 880233955a00 RCX: 
c01902a30f48c088
  [19927.256033] RDX: c01902a30f48c089 RSI: 8106b846 RDI: 
4000
  [19927.256033] RBP: 88023fd83a88 R08: 880233955a00 R09: 
c01902a30f48c088
  [19927.256033] R10: 009a660a158b487e R11: 8801cf5bfc00 R12: 
009a660a158b487e
  [19927.256033] R13: 8106b846 R14:  R15: 
880237001700
  [19927.256033] FS:  7fbf85e38740() GS:88023fd8() 
knlGS:
  [19927.256033] CS:  0010 DS:  ES:  CR0: 80050033
  [19927.256033] CR2: 7ffcaa2ca468 CR3: ba76 CR4: 
003406e0
  [19927.256033] Stack:
  [19927.256033]   880233d4f008  
880233cabc80
  [19927.256033]  c9e48004 0001 88023fd83ac0 
8175ff24
  [19927.256033]  0f48c088 88023fd83b50 811ef3fb 
880233d4f008
  [19927.256033] Call Trace:
  [19927.256033]  
  [19927.256033]  [] ? sch_direct_xmit+0x74/0x220
  [19927.256033]  [] __slab_free+0xcb/0x2c0
  [19927.256033]  [] ? __dev_queue_xmit+0x286/0x590
  [19927.256033]  [] kmem_cache_free+0x1d4/0x1e0
  [19927.256033]  [] kfree_skbmem+0x59/0x60
  [19927.256033]  [] consume_skb+0x34/0x90
  [19927.256033]  [] arp_process+0x80/0x750
  [19927.256033]  [] arp_rcv+0x133/0x1c0
  [19927.256033]  [] ? packet_rcv+0x44/0x440
  [19927.256033]  [] __netif_receive_skb_core+0x704/0xa60
  [19927.256033]  [] ? __build_skb+0x2a/0xe0
  [19927.256033]  [] __netif_receive_skb+0x18/0x60
  [19927.256033]  [] netif_receive_skb_internal+0x32/0xa0
  [19927.256033]  [] napi_gro_receive+0xc3/0xf0
  [19927.256033]  [] virtnet_receive+0x4a6/0x8f0
  [19927.256033]  [] virtnet_poll+0x1d/0x80
  [19927.256033]  [] net_rx_action+0x21e/0x360
  [19927.256033]  [] ? skb_recv_done+0x43/0x50
  [19927.256033]  [] __do_softirq+0x101/0x290
  [19927.256033]  [] irq_exit+0xa3/0xb0
  [19927.256033]  [] do_IRQ+0x54/0xd0
  [19927.256033]  [] common_interrupt+0x82/0x82
  [19927.256033]  
  [19927.256033]  [] ? native_safe_halt+0x6/0x10
  [19927.256033]  [] kvm_wait+0x52/0x60
  [19927.256033]  [] 
__pv_queued_spin_lock_slowpath+0x1d6/0x210
  [19927.256033]  [] _raw_spin_lock+0x21/0x30
  [19927.256033]  [] handle_mm_fault+0x60b/0x1820
  [19927.256033]  [] ? hrtimer_try_to_cancel+0x29/0x130
  [19927.256033]  [] ? do_nanosleep+0x96/0xf0
  [19927.256033]  [] ? hrtimer_nanosleep+0xdc/0x210
  [19927.256033]  [] __do_page_fault+0x197/0x400
  [19927.256033]  [] trace_do_page_fault+0x37/0xe0
  [19927.256033]  [] do_async_page_fault+0x19/0x70
  [19927.256033]  [] async_page_fault+0x28/0x30
  [19927.256033] Code: 0f 1f 80 00 00 00

[Kernel-packages] [Bug 1742721] Re: linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic fail to boot

2018-01-19 Thread Sanchola

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

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

Title:
  linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic
  fail to boot

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  In Progress

Bug description:
  == SRU Justification ==
  The following mainline commit introduced a regression in v4.11-rc1:
  c075b6f2d357ea9 ("staging: sm750fb: Replace POKE32 and PEEK32 by inline 
functions")

  This regression caused the bug reporters system to crash and exhibited no 
display 
  output.

  A "Reverse" bisect was performed and it was found that this regression is
  fixed by commit 16808dcf605e6, which was added to mainline in v4.15-rc1.

  
  == Fix ==
  commit 16808dcf605e6302319a8c3266789b76d4c0983b
  Author: Huacai Chen 
  Date:   Mon Nov 6 08:43:03 2017 +0800

  staging: sm750fb: Fix parameter mistake in poke32

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

  
  ## Original Bug Description#
  I've updated the machine to the linux-hwe kernels, and experienced an almost 
instant crash when booting.  Nothing is shown on the VGA output, so no stack 
traces are available.

  I've tried booting a few kernels with the following results:

  - linux-image-4.8.0-56-generic + linux-image-extra-4.8.0-56-generic: boots up 
fine
  - linux-image-4.13.0-26-generic + linux-image-extra-4.13.0-26-generic:  fails 
to boot
  - linux-image-4.13.0-21-generic: boots up, but since no r8169, no networking
  - linux-image-4.13.0-21-generic + linux-image-extra-4.13.0-21-generic:  fails 
to boot
  - linux-image-4.10.0-42-generic + linux-image-extra-4.10.0-42-generic:  boots 
up fine

  After that I've tried some mainline kernels from
  http://kernel.ubuntu.com/~kernel-ppa/mainline to check if the problem
  is the upstream or ubuntu patches:

  - linux-image-4.14.13-041413-generic_4.14.13-041413.201801101001_amd64.deb: 
boots up fine
  - linux-image-4.13.13-041313-generic_4.13.13-041313.201711150531_amd64.deb: 
fails to boot
  - linux-image-4.13.16-041316-generic_4.13.16-041316.201711240901_amd64.deb: 
boots up fine
  - linux-image-4.13.14-041314-generic_4.13.14-041314.201711180632_amd64.deb: 
fails to boot
  - linux-image-4.13.15-041315-generic_4.13.15-041315.201711211030_amd64.deb: 
boots up fine

  So, it seems, the problem is fixed either in patches between 4.13.14
  and 4.13.15 upstream, or ubuntu configs/patches applied to mainline
  kernels.

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

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

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

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

apport-collect 1744169

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

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

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

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

** Tags added: xenial

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

Title:
  KVM + Virtio kernel panic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I received the following kernel panic on a KVM VM which is acting as
  an OpenStack compute node. I'm unable to consistently reproduce this,
  but I do consistently get various kernel panics (this is only one of
  them). Is anyone able to shed any light on what might be happening
  here?

  Ubuntu Server 16.04 cloud image.
  Kernel Version: 4.4.0-98-generic

  
  [19927.255474] general protection fault:  [#1] SMP
  [19927.256033] Modules linked in: vhost_net vhost macvtap macvlan xt_REDIRECT 
nf_nat_redirect xt_mark ip6table_mangle iptable_nat nf_nat_ipv4 nf_nat 
xt_connmark iptable_mangle ip6table_raw nf_conntrack_ipv6 xt_CT xt_mac 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_comment xt_physdev xt_set 
xt_conntrack ip_set_hash_net ip_set nfnetlink iptable_raw veth ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables 
br_netfilter bridge stp llc vport_gre ip_gre ip_tunnel gre vport_vxlan vxlan 
ip6_udp_tunnel udp_tunnel openvswitch nf_defrag_ipv6 nf_conntrack ppdev kvm_amd 
kvm input_leds serio_raw joydev irqbypass parport_pc parport ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [19927.256033] CPU: 3 PID: 2801 Comm: vna_agent Not tainted 4.4.0-98-generic 
#121-Ubuntu
  [19927.256033] Hardware name: RDO OpenStack Compute, BIOS 1.9.1-5.el7_3.3 
04/01/2014
  [19927.256033] task: 88023551c600 ti: 8800bb9ac000 task.ti: 
8800bb9ac000
  [19927.256033] RIP: 0010:[]  [] 
cmpxchg_double_slab.isra.54+0x24/0xe0
  [19927.256033] RSP: :88023fd83a40  EFLAGS: 00010206
  [19927.256033] RAX: 009a660a158b487e RBX: 880233955a00 RCX: 
c01902a30f48c088
  [19927.256033] RDX: c01902a30f48c089 RSI: 8106b846 RDI: 
4000
  [19927.256033] RBP: 88023fd83a88 R08: 880233955a00 R09: 
c01902a30f48c088
  [19927.256033] R10: 009a660a158b487e R11: 8801cf5bfc00 R12: 
009a660a158b487e
  [19927.256033] R13: 8106b846 R14:  R15: 
880237001700
  [19927.256033] FS:  7fbf85e38740() GS:88023fd8() 
knlGS:
  [19927.256033] CS:  0010 DS:  ES:  CR0: 80050033
  [19927.256033] CR2: 7ffcaa2ca468 CR3: ba76 CR4: 
003406e0
  [19927.256033] Stack:
  [19927.256033]   880233d4f008  
880233cabc80
  [19927.256033]  c9e48004 0001 88023fd83ac0 
8175ff24
  [19927.256033]  0f48c088 88023fd83b50 811ef3fb 
880233d4f008
  [19927.256033] Call Trace:
  [19927.256033]  
  [19927.256033]  [] ? sch_direct_xmit+0x74/0x220
  [19927.256033]  [] __slab_free+0xcb/0x2c0
  [19927.256033]  [] ? __dev_queue_xmit+0x286/0x590
  [19927.256033]  [] kmem_cache_free+0x1d4/0x1e0
  [19927.256033]  [] kfree_skbmem+0x59/0x60
  [19927.256033]  [] consume_skb+0x34/0x90
  [19927.256033]  [] arp_process+0x80/0x750
  [19927.256033]  [] arp_rcv+0x133/0x1c0
  [19927.256033]  [] ? packet_rcv+0x44/0x440
  [19927.256033]  [] __netif_receive_skb_core+0x704/0xa60
  [19927.256033]  [] ? __build_skb+0x2a/0xe0
  [19927.256033]  [] __netif_receive_skb+0x18/0x60
  [19927.256033]  [] netif_receive_skb_internal+0x32/0xa0
  [19927.256033]  [] napi_gro_receive+0xc3/0xf0
  [19927.256033]  [] virtnet_receive+0x4a6/0x8f0
  [19927.256033]  [] virtnet_poll+0x1d/0x80
  [19927.256033]  [] net_rx_action+0x21e/0x360
  [19927.256033]  [] ? skb_recv_done+0x43/0x50
  [19927.256033]  [] __do_softirq+0x101/0x290
  [19927.256033]  [] irq_exit+0xa3/0xb0
  [19927.256033]  [] do_IRQ+0x54/0xd0
  [19927.256033]  [] common_interrupt+0x82/0x82
  [19927.256033]  
  [19927.256033]  [] ? native_safe_halt+0x6/0x10
  [19927.256033]  [] kvm_wait+0x52/0x60
  [19927.256033]  []

[Kernel-packages] [Bug 1744169] Re: KVM + Virtio kernel panic

2018-01-19 Thread Brian Murray

** Package changed: kernel-package (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/1744169

Title:
  KVM + Virtio kernel panic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I received the following kernel panic on a KVM VM which is acting as
  an OpenStack compute node. I'm unable to consistently reproduce this,
  but I do consistently get various kernel panics (this is only one of
  them). Is anyone able to shed any light on what might be happening
  here?

  Ubuntu Server 16.04 cloud image.
  Kernel Version: 4.4.0-98-generic

  
  [19927.255474] general protection fault:  [#1] SMP
  [19927.256033] Modules linked in: vhost_net vhost macvtap macvlan xt_REDIRECT 
nf_nat_redirect xt_mark ip6table_mangle iptable_nat nf_nat_ipv4 nf_nat 
xt_connmark iptable_mangle ip6table_raw nf_conntrack_ipv6 xt_CT xt_mac 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_comment xt_physdev xt_set 
xt_conntrack ip_set_hash_net ip_set nfnetlink iptable_raw veth ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables 
br_netfilter bridge stp llc vport_gre ip_gre ip_tunnel gre vport_vxlan vxlan 
ip6_udp_tunnel udp_tunnel openvswitch nf_defrag_ipv6 nf_conntrack ppdev kvm_amd 
kvm input_leds serio_raw joydev irqbypass parport_pc parport ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [19927.256033] CPU: 3 PID: 2801 Comm: vna_agent Not tainted 4.4.0-98-generic 
#121-Ubuntu
  [19927.256033] Hardware name: RDO OpenStack Compute, BIOS 1.9.1-5.el7_3.3 
04/01/2014
  [19927.256033] task: 88023551c600 ti: 8800bb9ac000 task.ti: 
8800bb9ac000
  [19927.256033] RIP: 0010:[]  [] 
cmpxchg_double_slab.isra.54+0x24/0xe0
  [19927.256033] RSP: :88023fd83a40  EFLAGS: 00010206
  [19927.256033] RAX: 009a660a158b487e RBX: 880233955a00 RCX: 
c01902a30f48c088
  [19927.256033] RDX: c01902a30f48c089 RSI: 8106b846 RDI: 
4000
  [19927.256033] RBP: 88023fd83a88 R08: 880233955a00 R09: 
c01902a30f48c088
  [19927.256033] R10: 009a660a158b487e R11: 8801cf5bfc00 R12: 
009a660a158b487e
  [19927.256033] R13: 8106b846 R14:  R15: 
880237001700
  [19927.256033] FS:  7fbf85e38740() GS:88023fd8() 
knlGS:
  [19927.256033] CS:  0010 DS:  ES:  CR0: 80050033
  [19927.256033] CR2: 7ffcaa2ca468 CR3: ba76 CR4: 
003406e0
  [19927.256033] Stack:
  [19927.256033]   880233d4f008  
880233cabc80
  [19927.256033]  c9e48004 0001 88023fd83ac0 
8175ff24
  [19927.256033]  0f48c088 88023fd83b50 811ef3fb 
880233d4f008
  [19927.256033] Call Trace:
  [19927.256033]  
  [19927.256033]  [] ? sch_direct_xmit+0x74/0x220
  [19927.256033]  [] __slab_free+0xcb/0x2c0
  [19927.256033]  [] ? __dev_queue_xmit+0x286/0x590
  [19927.256033]  [] kmem_cache_free+0x1d4/0x1e0
  [19927.256033]  [] kfree_skbmem+0x59/0x60
  [19927.256033]  [] consume_skb+0x34/0x90
  [19927.256033]  [] arp_process+0x80/0x750
  [19927.256033]  [] arp_rcv+0x133/0x1c0
  [19927.256033]  [] ? packet_rcv+0x44/0x440
  [19927.256033]  [] __netif_receive_skb_core+0x704/0xa60
  [19927.256033]  [] ? __build_skb+0x2a/0xe0
  [19927.256033]  [] __netif_receive_skb+0x18/0x60
  [19927.256033]  [] netif_receive_skb_internal+0x32/0xa0
  [19927.256033]  [] napi_gro_receive+0xc3/0xf0
  [19927.256033]  [] virtnet_receive+0x4a6/0x8f0
  [19927.256033]  [] virtnet_poll+0x1d/0x80
  [19927.256033]  [] net_rx_action+0x21e/0x360
  [19927.256033]  [] ? skb_recv_done+0x43/0x50
  [19927.256033]  [] __do_softirq+0x101/0x290
  [19927.256033]  [] irq_exit+0xa3/0xb0
  [19927.256033]  [] do_IRQ+0x54/0xd0
  [19927.256033]  [] common_interrupt+0x82/0x82
  [19927.256033]  
  [19927.256033]  [] ? native_safe_halt+0x6/0x10
  [19927.256033]  [] kvm_wait+0x52/0x60
  [19927.256033]  [] 
__pv_queued_spin_lock_slowpath+0x1d6/0x210
  [19927.256033]  [] _raw_spin_lock+0x21/0x30
  [19927.256033]  [] handle_mm_fault+0x60b/0x1820
  [19927.256033]  [] ? hrtimer_try_to_cancel+0x29/0x130
  [19927.256033]  [] ? do_nanosleep+0x96/0xf0
  [19927.256033]  [] ? hrtimer_nanosleep+0xdc/0x210
  [19927.256033]  [] __do_page_fault+0x197/0x400
  [19927.256033]  [] trace_do_page_fault+0x37/0xe0
  [19927.256033]  [] do_async_page_fault+0x19/0x70
  [19927.256033]  [] async_page_fault+0x28/0x30
  [19927.256033] Code: 0f 1f 80 00 00 00 00 55 49 89 d2 48 89 e5 53 48 83 e4 f0 
48 83 ec 40 f7 c7 00 00 00 40

[Kernel-packages] [Bug 1744173] Re: artful: rfi-flush: Switch to new linear fallback flush

2018-01-19 Thread Brian Murray

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

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

Title:
  artful: rfi-flush: Switch to new linear fallback flush

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

Bug description:
  Change flush from congruence-first with dependencies to linear with
  no dependencies, which increases flush performance by 8x on P8, and
  3x on P9 (as measured with null syscall loop, which will have the
  flush area in the L2).

  The flush also becomes simpler and more adaptable to different cache
  geometries.

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

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

[Kernel-packages] [Bug 1744169] [NEW] KVM + Virtio kernel panic

2018-01-19 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

I received the following kernel panic on a KVM VM which is acting as an
OpenStack compute node. I'm unable to consistently reproduce this, but I
do consistently get various kernel panics (this is only one of them). Is
anyone able to shed any light on what might be happening here?

Ubuntu Server 16.04 cloud image.
Kernel Version: 4.4.0-98-generic


[19927.255474] general protection fault:  [#1] SMP
[19927.256033] Modules linked in: vhost_net vhost macvtap macvlan xt_REDIRECT 
nf_nat_redirect xt_mark ip6table_mangle iptable_nat nf_nat_ipv4 nf_nat 
xt_connmark iptable_mangle ip6table_raw nf_conntrack_ipv6 xt_CT xt_mac 
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_comment xt_physdev xt_set 
xt_conntrack ip_set_hash_net ip_set nfnetlink iptable_raw veth ebtable_filter 
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables 
br_netfilter bridge stp llc vport_gre ip_gre ip_tunnel gre vport_vxlan vxlan 
ip6_udp_tunnel udp_tunnel openvswitch nf_defrag_ipv6 nf_conntrack ppdev kvm_amd 
kvm input_leds serio_raw joydev irqbypass parport_pc parport ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
[19927.256033] CPU: 3 PID: 2801 Comm: vna_agent Not tainted 4.4.0-98-generic 
#121-Ubuntu
[19927.256033] Hardware name: RDO OpenStack Compute, BIOS 1.9.1-5.el7_3.3 
04/01/2014
[19927.256033] task: 88023551c600 ti: 8800bb9ac000 task.ti: 
8800bb9ac000
[19927.256033] RIP: 0010:[]  [] 
cmpxchg_double_slab.isra.54+0x24/0xe0
[19927.256033] RSP: :88023fd83a40  EFLAGS: 00010206
[19927.256033] RAX: 009a660a158b487e RBX: 880233955a00 RCX: c01902a30f48c088
[19927.256033] RDX: c01902a30f48c089 RSI: 8106b846 RDI: 4000
[19927.256033] RBP: 88023fd83a88 R08: 880233955a00 R09: c01902a30f48c088
[19927.256033] R10: 009a660a158b487e R11: 8801cf5bfc00 R12: 009a660a158b487e
[19927.256033] R13: 8106b846 R14:  R15: 880237001700
[19927.256033] FS:  7fbf85e38740() GS:88023fd8() 
knlGS:
[19927.256033] CS:  0010 DS:  ES:  CR0: 80050033
[19927.256033] CR2: 7ffcaa2ca468 CR3: ba76 CR4: 003406e0
[19927.256033] Stack:
[19927.256033]   880233d4f008  
880233cabc80
[19927.256033]  c9e48004 0001 88023fd83ac0 
8175ff24
[19927.256033]  0f48c088 88023fd83b50 811ef3fb 
880233d4f008
[19927.256033] Call Trace:
[19927.256033]  
[19927.256033]  [] ? sch_direct_xmit+0x74/0x220
[19927.256033]  [] __slab_free+0xcb/0x2c0
[19927.256033]  [] ? __dev_queue_xmit+0x286/0x590
[19927.256033]  [] kmem_cache_free+0x1d4/0x1e0
[19927.256033]  [] kfree_skbmem+0x59/0x60
[19927.256033]  [] consume_skb+0x34/0x90
[19927.256033]  [] arp_process+0x80/0x750
[19927.256033]  [] arp_rcv+0x133/0x1c0
[19927.256033]  [] ? packet_rcv+0x44/0x440
[19927.256033]  [] __netif_receive_skb_core+0x704/0xa60
[19927.256033]  [] ? __build_skb+0x2a/0xe0
[19927.256033]  [] __netif_receive_skb+0x18/0x60
[19927.256033]  [] netif_receive_skb_internal+0x32/0xa0
[19927.256033]  [] napi_gro_receive+0xc3/0xf0
[19927.256033]  [] virtnet_receive+0x4a6/0x8f0
[19927.256033]  [] virtnet_poll+0x1d/0x80
[19927.256033]  [] net_rx_action+0x21e/0x360
[19927.256033]  [] ? skb_recv_done+0x43/0x50
[19927.256033]  [] __do_softirq+0x101/0x290
[19927.256033]  [] irq_exit+0xa3/0xb0
[19927.256033]  [] do_IRQ+0x54/0xd0
[19927.256033]  [] common_interrupt+0x82/0x82
[19927.256033]  
[19927.256033]  [] ? native_safe_halt+0x6/0x10
[19927.256033]  [] kvm_wait+0x52/0x60
[19927.256033]  [] __pv_queued_spin_lock_slowpath+0x1d6/0x210
[19927.256033]  [] _raw_spin_lock+0x21/0x30
[19927.256033]  [] handle_mm_fault+0x60b/0x1820
[19927.256033]  [] ? hrtimer_try_to_cancel+0x29/0x130
[19927.256033]  [] ? do_nanosleep+0x96/0xf0
[19927.256033]  [] ? hrtimer_nanosleep+0xdc/0x210
[19927.256033]  [] __do_page_fault+0x197/0x400
[19927.256033]  [] trace_do_page_fault+0x37/0xe0
[19927.256033]  [] do_async_page_fault+0x19/0x70
[19927.256033]  [] async_page_fault+0x28/0x30
[19927.256033] Code: 0f 1f 80 00 00 00 00 55 49 89 d2 48 89 e5 53 48 83 e4 f0 
48 83 ec 40 f7 c7 00 00 00 40 74 2c 48 89 ca 4c 89 d0 4c 89 c3 4c 89 c9  48 
0f c7 4e 10 0f 94 c0 41 89 c0 b8 01 00 00 00 45 84 c0 75
[19927.256033] RIP  [] cmpxchg_double_slab.isra.54+0x24/0xe0
[19927.256033]  RSP 
[19927.296033] general protection fault:  [#2] [19927.405901] ---[ end 
trace f7ced269874d3811  ]---
[19927.405903] Kernel panic - not syncing: Fatal exception in interrupt
[19927.296033] SMP
[19927.296033] Modules linked in:

[Kernel-packages] [Bug 1744294] Re: linux: 4.13.0-31.34 -proposed tracker

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

** Tags added: block-proposed-artful

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1744295,1742725,1744298,1743418,1742723,1742726
  derivatives: 1743419
  kernel-stable-phase-changed:Friday, 19. January 2018 17:01 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.13.0-31.34 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1744295,1742725,1744298,1743418,1742723,1742726
  derivatives: 1743419
  kernel-stable-phase-changed:Friday, 19. January 2018 17:01 UTC
  kernel-stable-phase:Uploaded

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

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

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

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

This change was made by a bot.

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

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

Title:
  package linux-generic 4.4.0.109.114 failed to install/upgrade:
  Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  /boot was full but bug remain as /boot was eptied from old kernels

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.109.114
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dd 2810 F pulseaudio
  Date: Mon Jan 15 00:25:15 2018
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  HibernationDevice: RESUME=UUID=aa814f2d-baf1-4b27-a546-bcdfe202dba3
  InstallationDate: Installed on 2017-07-05 (198 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ZOTAC ZBOX-CI527/CI547
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-109-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash pci=noaer vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux-meta
  Title: package linux-generic 4.4.0.109.114 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B331P205
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-CI527/CI547
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB331P205:bd03/15/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.name: ZBOX-CI527/CI547
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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

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

2018-01-19 Thread Emiko Bellocq

#540
I forgot to mention.
Since you have to use Windows for this dualboot setup, it might be easier to use
EaseUS Partition Master Free to create a new partition(s) and EasyBCD to select
a boot partition.
I have been using this method for some years to dualboot before I switched to
Linux + VM Windows configuration.

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

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

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

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

---

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

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

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

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

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

---

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

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

---

Affected Machines:

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

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

---

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

---

Original Description:

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

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

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

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

Thank you!!

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

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

[Kernel-packages] [Bug 1744398] Re: package linux-generic 4.4.0.109.114 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

** Package changed: linux-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/1744398

Title:
  package linux-generic 4.4.0.109.114 failed to install/upgrade:
  Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status in linux package in Ubuntu:
  New

Bug description:
  /boot was full but bug remain as /boot was eptied from old kernels

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.109.114
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dd 2810 F pulseaudio
  Date: Mon Jan 15 00:25:15 2018
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  HibernationDevice: RESUME=UUID=aa814f2d-baf1-4b27-a546-bcdfe202dba3
  InstallationDate: Installed on 2017-07-05 (198 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ZOTAC ZBOX-CI527/CI547
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-109-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash pci=noaer vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux-meta
  Title: package linux-generic 4.4.0.109.114 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B331P205
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-CI527/CI547
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB331P205:bd03/15/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.name: ZBOX-CI527/CI547
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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

[Kernel-packages] [Bug 1744398] [NEW] package linux-generic 4.4.0.109.114 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

2018-01-19 Thread walters

Public bug reported:

/boot was full but bug remain as /boot was eptied from old kernels

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-generic 4.4.0.109.114
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dd 2810 F pulseaudio
Date: Mon Jan 15 00:25:15 2018
ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
HibernationDevice: RESUME=UUID=aa814f2d-baf1-4b27-a546-bcdfe202dba3
InstallationDate: Installed on 2017-07-05 (198 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: ZOTAC ZBOX-CI527/CI547
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-109-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash pci=noaer vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux-meta
Title: package linux-generic 4.4.0.109.114 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: B331P205
dmi.board.asset.tag: NA
dmi.board.name: ZBOX-CI527/CI547
dmi.board.vendor: ZOTAC
dmi.board.version: XX
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 9
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB331P205:bd03/15/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring:
dmi.product.name: ZBOX-CI527/CI547
dmi.product.version: XX
dmi.sys.vendor: ZOTAC

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-generic 4.4.0.109.114 failed to install/upgrade:
  Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status in linux package in Ubuntu:
  New

Bug description:
  /boot was full but bug remain as /boot was eptied from old kernels

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.109.114
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dd 2810 F pulseaudio
  Date: Mon Jan 15 00:25:15 2018
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  HibernationDevice: RESUME=UUID=aa814f2d-baf1-4b27-a546-bcdfe202dba3
  InstallationDate: Installed on 2017-07-05 (198 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ZOTAC ZBOX-CI527/CI547
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-109-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash pci=noaer vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux-meta
  Title: package linux-generic 4.4.0.109.114 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B331P205
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-CI527/CI547
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB331P205:bd03/15/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.name: ZBOX-CI527/CI547
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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

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

2018-01-19 Thread Emiko Bellocq

#540
> Do you think if i install Ubuntu using that guide and after i update the
> kernel i colud fix my bios?

I think all you have to do is installling the "latest" 17.10 with the big-fixed
kernel which is now available for download.
https://www.ubuntu.com/download/desktop

This dualboot setting should not affect your current Windows installation.
But if you have any important data on Windows, I recommend you to make a back
up - just in case.

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

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

---

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

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

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

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

---

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

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

---

Affected Machines:

---

Original Description:

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

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

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

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

Thank you!!

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

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

[Kernel-packages] [Bug 1729674]

2018-01-19 Thread Gerben

Applied to 4.14.14. Offload:

tcp-segmentation-offload: on
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: on
rx-vlan-offload: on
tx-vlan-offload: on

dd | sha1sum loop:

742462292c76189f63fc3e7af1acc9dec56c0a8d  -
742462292c76189f63fc3e7af1acc9dec56c0a8d  -
742462292c76189f63fc3e7af1acc9dec56c0a8d  -
742462292c76189f63fc3e7af1acc9dec56c0a8d  -
742462292c76189f63fc3e7af1acc9dec56c0a8d  -
742462292c76189f63fc3e7af1acc9dec56c0a8d  -

Ran for 10 minutes, so looks like that patch works (doing around
90mbit/s of traffic).

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

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux package in Fedora:
  Confirmed

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions

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

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

I have just submitted the SRU proposal to kernel team mailing list. I'll
wait for the SRU to be made and this public bug to be marked as Fix
Committed before verifying the fix again for the final release.

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  Opinion
Status in linux source package in Trusty:
  In Progress
Status in open-iscsi source package in Trusty:
  Opinion
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  Opinion
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  Opinion
Status in linux source package in Bionic:
  In Progress
Status in open-iscsi source package in Bionic:
  Opinion

Bug description:
  [Impact]

   * open-iscsi users might face hangs during OS shutdown.
   * hangs can be caused by manual iscsi configuration/setup.
   * hangs can also be caused by bad systemd unit ordering.
   * if transport layer interface vanishes before lun is
 disconnected, then the hang will happen.
   * check comment #89 for the fix decision.
   
  [Test Case]

   * a simple way of reproducing the kernel hang is to disable
 the open-iscsi logouts. this simulates a situation when
 a service has shutdown the network interface, used by
 the transport layer, before proper iscsi logout was done.

 $ log into all iscsi luns

 $ systemctl edit --full open-iscsi.service
 ...
 #ExecStop=/lib/open-iscsi/logout-all.sh
 ...

 $ sudo reboot # this will make server to hang forever
   # on shutdown

  [Regression Potential]

   * the regression is low because the change acts on the iscsi
 transport layer code ONLY when the server is in shutdown 
 state.

   * any error in logic would only appear during shutdown and
 would not cause any harm to data.

  [Other Info]
   
   * ORIGINAL BUG DESCRIPTION

  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

** Changed in: open-iscsi (Ubuntu Trusty)
   Status: New => Opinion

** Changed in: linux (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Rafael David Tinoco (inaddy)

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

** Changed in: open-iscsi (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: open-iscsi (Ubuntu Trusty)
 Assignee: (unassigned) => Rafael David Tinoco (inaddy)

** No longer affects: open-iscsi (Ubuntu Zesty)

** No longer affects: linux (Ubuntu Zesty)

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  Opinion
Status in linux source package in Trusty:
  In Progress
Status in open-iscsi source package in Trusty:
  Opinion
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  Opinion
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  Opinion
Status in linux source package in Bionic:
  In Progress
Status in open-iscsi source package in Bionic:
  Opinion

Bug description:
  [Impact]

   * open-iscsi users might face hangs during OS shutdown.
   * hangs can be caused by manual iscsi configuration/setup.
   * hangs can also be caused by bad systemd unit ordering.
   * if transport layer interface vanishes before lun is
 disconnected, then the hang will happen.
   * check comment #89 for the fix decision.
   
  [Test Case]

   * a simple way of reproducing the kernel hang is to disable
 the open-iscsi logouts. this simulates a situation when
 a service has shutdown the network interface, used by
 the transport layer, before proper iscsi logout was done.

 $ log into all iscsi luns

 $ systemctl edit --full open-iscsi.service
 ...
 #ExecStop=/lib/open-iscsi/logout-all.sh
 ...

 $ sudo reboot # this will make server to hang forever
   # on shutdown

  [Regression Potential]

   * the regression is low because the change acts on the iscsi
 transport layer code ONLY when the server is in shutdown 
 state.

   * any error in logic would only appear during shutdown and
 would not cause any harm to data.

  [Other Info]
   
   * ORIGINAL BUG DESCRIPTION

  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage

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

2018-01-19 Thread Jørgen Best

If I knew how I might be able to bisect. I found some info on the issue
(see links), I think I can compile a kernel if I knew the options that
the kernel I used was compiled with. I'm not really a programmer so if I
have to read through (too much) code I will fail. Is there a link for
Ubuntu standard kernel compiling?

I understand from Dirk Bachmann that some where between 4.13.0.21 en 25
thinks got broken. I understand that I need the first kernel that broke
and the one before and somehow have to compare them with git. At least I
should be able to find out at what update things got broken.

How can I successfully run the script "git bisect run" step by step if I
have to hibernate the system and each time I do this the system will
freeze at resume? I assume the analysis will be aborted each time.

If someone has a link to some more info (for a not really programmer),
I'll give it a try.

Links:
https://www.kernel.org/doc/html/latest/admin-guide/bug-bisect.html
https://lwn.net/Articles/317154/

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

This change was made by a bot.

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

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

Title:
  tcp_fastretrans_alert kernel warnings, possible system hardlock

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have experienced a full system lockup, not even SysRq+REISUB could
  reboot the system. In the kernel logs I noticed multiple
  tcp_fastretrans_alert warnings and the upstream bug
  (https://bugzilla.kernel.org/show_bug.cgi?id=195835,
  https://bugzilla.kernel.org/show_bug.cgi?id=60779) seems to indicate
  this may be the reason.

  In the attached kernel log, the hang happened immediately before the
  last reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  lastique   3183 F pulseaudio
   /dev/snd/controlC1:  lastique   3183 F pulseaudio
   /dev/snd/controlC2:  lastique   3183 F pulseaudio
   /dev/snd/controlC0:  lastique   3183 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 19 22:26:36 2018
  InstallationDate: Installed on 2015-05-01 (993 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-03 (76 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

2018-01-19 Thread Pawel Por

I'm using laptop Samsung N130 and also have this issue with kernel
4.13.0-26-generic. Downgrading to kernel 4.10.0-42-generic solves the
issue but this kernel is Meltdown vulnerable. I've reported my issue
#1742756

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1744379] [NEW] tcp_fastretrans_alert kernel warnings, possible system hardlock

2018-01-19 Thread Lastique

Public bug reported:

I have experienced a full system lockup, not even SysRq+REISUB could
reboot the system. In the kernel logs I noticed multiple
tcp_fastretrans_alert warnings and the upstream bug
(https://bugzilla.kernel.org/show_bug.cgi?id=195835,
https://bugzilla.kernel.org/show_bug.cgi?id=60779) seems to indicate
this may be the reason.

In the attached kernel log, the hang happened immediately before the
last reboot.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-25-generic 4.13.0-25.29
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  lastique   3183 F pulseaudio
 /dev/snd/controlC1:  lastique   3183 F pulseaudio
 /dev/snd/controlC2:  lastique   3183 F pulseaudio
 /dev/snd/controlC0:  lastique   3183 F pulseaudio
CurrentDesktop: KDE
Date: Fri Jan 19 22:26:36 2018
InstallationDate: Installed on 2015-05-01 (993 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: System manufacturer System Product Name
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-25-generic N/A
 linux-backports-modules-4.13.0-25-generic  N/A
 linux-firmware 1.169.1
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-11-03 (76 days ago)
dmi.bios.date: 11/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug artful

** Attachment added: "Kernel log"
   https://bugs.launchpad.net/bugs/1744379/+attachment/5039732/+files/kern.log

** Description changed:

  I have experienced a full system lockup, not even SysRq+REISUB could
  reboot the system. In the kernel logs I noticed multiple
  tcp_fastretrans_alert warnings and the upstream bug
- (https://bugzilla.kernel.org/show_bug.cgi?id=60779) seems to indicate
+ (https://bugzilla.kernel.org/show_bug.cgi?id=195835) seems to indicate
  this may be the reason.
  
  In the attached kernel log, the hang happened immediately before the
  last reboot.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC3:  lastique   3183 F pulseaudio
-  /dev/snd/controlC1:  lastique   3183 F pulseaudio
-  /dev/snd/controlC2:  lastique   3183 F pulseaudio
-  /dev/snd/controlC0:  lastique   3183 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC3:  lastique   3183 F pulseaudio
+  /dev/snd/controlC1:  lastique   3183 F pulseaudio
+  /dev/snd/controlC2:  lastique   3183 F pulseaudio
+  /dev/snd/controlC0:  lastique   3183 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 19 22:26:36 2018
  InstallationDate: Installed on 2015-05-01 (993 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
-  linux-restricted-modules-4.13.0-25-generic N/A
-  linux-backports-modules-4.13.0-25-generic  N/A
-  linux-firmware 1.169.1
+  linux-restricted-modules-4.13.0-25-generic N/A
+  linux-backports-modules-4.13.0-25-generic  N/A
+  linux-firmware 1.169.1
  RfKill:
-  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on

[Kernel-packages] [Bug 1744308] Re: linux: 3.13.0-141.190 -proposed tracker

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

** Tags added: block-proposed-trusty

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1744309
  derivatives:
  kernel-stable-phase-changed:Friday, 19. January 2018 13:32 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 3.13.0-141.190 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1744309
  derivatives:
  kernel-stable-phase-changed:Friday, 19. January 2018 13:32 UTC
  kernel-stable-phase:Uploaded

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

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

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

[Kernel-packages] [Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260

2018-01-19 Thread Pete

I believe I am having the same issue on Ubuntu 17.10. Using Lenovo Yoga
11e, w/ Intel 7265 wireless.

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

Title:
  Connecting to wifi 5GHz network causes iwlwifi firmware/driver error.
  Intel Wireless 7260

Status in Ubuntu:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Only happens when connecting to 5GHz network, 2.5 GHz work fine.
  Network controller: Intel Corporation Wireless 7260 (rev 6b)

  iwlwifi :02:00.0: loaded firmware version 17.459231.0 op_mode
  iwlmvm

  
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4289] device 
(wlan0): Activation: starting connection 'NewHibernia5' 
(104460fe-9e5b-4a8c-8735-cfe48dec488e)
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4290] audit: 
op="connection-activate" uuid="104460fe-9e5b-4a8c-8735-cfe48dec488e" 
name="NewHibernia5" pid=7054 uid=1000 result="success"
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4291] device 
(wlan0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4293] 
manager: NetworkManager state is now CONNECTING
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4339] device 
(wlan0): set-hw-addr: set-cloned MAC address to E8:2A:EA:D4:16:6F (permanent)
  апр 14 10:32:34 liasus kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not 
ready
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4381] device 
(wlan0): state change: prepare -> config (reason 'none') [40 50 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4383] device 
(wlan0): Activation: (wifi) access point 'NewHibernia5' has security, but 
secrets are required.
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4384] device 
(wlan0): state change: config -> need-auth (reason 'none') [50 60 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4433] device 
(wlan0): state change: need-auth -> prepare (reason 'none') [60 40 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4438] device 
(wlan0): state change: prepare -> config (reason 'none') [40 50 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4450] device 
(wlan0): Activation: (wifi) connection 'NewHibernia5' has security, and secrets 
exist.  No new secrets needed.
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4451] 
Config: added 'ssid' value 'NewHibernia5'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4451] 
Config: added 'scan_ssid' value '1'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'key_mgmt' value 'WPA-PSK'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'auth_alg' value 'OPEN'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'psk' value ''
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4654] 
sup-iface[0x55900cef86c0,wlan0]: config: set interface ap_scan to 1
  апр 14 10:32:34 liasus wpa_supplicant[1923]: wlan0: SME: Trying to 
authenticate with e4:8d:8c:61:7d:04 (SSID='NewHibernia5' freq=5280 MHz)
  апр 14 10:32:34 liasus kernel: wlan0: authenticate with e4:8d:8c:61:7d:04
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: Microcode SW error 
detected.  Restarting 0x200.
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR values:
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: (2nd byte of 
CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_HW_IF_CONFIG_REG: 0X40489204
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_INT_COALESCING: 0X8000ff40
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 
CSR_INT: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_INT_MASK: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_FH_INT_STATUS: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 
CSR_GPIO_IN: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_RESET: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_GP_CNTRL: 0X080403cd
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_HW_REV: 0X0144
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_EEPROM_REG: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_EEPROM_GP: 0X8000
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_OTP_GP_REG: 0X803a
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 
CSR_GIO_REG: 0X001f0042
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_GP_UCODE_REG: 0X
  апр 14

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

2018-01-19 Thread Dan Streetman

** Also affects: open-iscsi (Ubuntu Bionic)
   Importance: Medium
 Assignee: Rafael David Tinoco (inaddy)
   Status: Opinion

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
 Assignee: Rafael David Tinoco (inaddy)
   Status: In Progress

** Also affects: open-iscsi (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  Opinion
Status in linux source package in Trusty:
  New
Status in open-iscsi source package in Trusty:
  New
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  Opinion
Status in linux source package in Zesty:
  In Progress
Status in open-iscsi source package in Zesty:
  Opinion
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  Opinion
Status in linux source package in Bionic:
  In Progress
Status in open-iscsi source package in Bionic:
  Opinion

Bug description:
  [Impact]

   * open-iscsi users might face hangs during OS shutdown.
   * hangs can be caused by manual iscsi configuration/setup.
   * hangs can also be caused by bad systemd unit ordering.
   * if transport layer interface vanishes before lun is
 disconnected, then the hang will happen.
   * check comment #89 for the fix decision.
   
  [Test Case]

   * a simple way of reproducing the kernel hang is to disable
 the open-iscsi logouts. this simulates a situation when
 a service has shutdown the network interface, used by
 the transport layer, before proper iscsi logout was done.

 $ log into all iscsi luns

 $ systemctl edit --full open-iscsi.service
 ...
 #ExecStop=/lib/open-iscsi/logout-all.sh
 ...

 $ sudo reboot # this will make server to hang forever
   # on shutdown

  [Regression Potential]

   * the regression is low because the change acts on the iscsi
 transport layer code ONLY when the server is in shutdown 
 state.

   * any error in logic would only appear during shutdown and
 would not cause any harm to data.

  [Other Info]
   
   * ORIGINAL BUG DESCRIPTION

  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1367366] Re: [DELL XPS 15 L502X] internal sd card reader problem

2018-01-19 Thread Christopher M. Penalver

asgard2, in order to allow additional upstream mainline kernel developers to 
examine the issue, at your earliest convenience, could you please test the 
latest mainline kernel available from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind 
the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the report 
description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest mainline kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** Description changed:

- Hi,
- 
- my internal SD-card reader is not working at the DELL XPS 15 L502X.
+ The internal SD-card reader is not working in a DELL XPS 15 L502X.
  
  messages at the system log:
  kernel: [  332.414191] mmc0: error -110 whilst initialising SD card
  kernel: [  332.763919] mmc0: error -110 whilst initialising SD card
  
- 
  After several tries, the card is recognized.
- 
- The bug seems solved for some time:
- https://bugs.launchpad.net/linux/+bug/995743
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-36-generic 3.13.0-36.63
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  chuck-game   2122 F lxpanel
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  chuck-game   2122 F lxpanel
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
  CurrentDesktop: LXDE
  Date: Tue Sep  9 18:24:58 2014
  HibernationDevice: RESUME=UUID=031c1bfb-a99f-45ff-b7fc-eeaa254f9a2a
  InstallationDate: Installed on 2013-08-10 (394 days ago)
  InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=50751449-1f90-4151-bc30-329f3b22e2cf ro quiet 
rcutree.rcu_idle_gp_delay=1
  RelatedPackageVersions:
-  linux-restricted-modules-3.13.0-36-generic N/A
-  linux-backports-modules-3.13.0-36-generic  N/A
-  linux-firmware 1.127.5
+  linux-restricted-modules-3.13.0-36-generic N/A
+  linux-backports-modules-3.13.0-36-generic  N/A
+  linux-firmware 1.127.5
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (144 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing

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

** Tags added: regression-potential

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in

[Kernel-packages] [Bug 995743] Re: 197b:2394 [Dell XPS 17 L502X] Internal SD card reader is not working

2018-01-19 Thread Christopher M. Penalver

asgard2 (kamp000x), this issue was addressed for the original reporter 3
years ago. Hence, it has nothing to do with your problem.

If you want your issue addressed, file a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

Title:
  197b:2394 [Dell XPS 17 L502X] Internal SD card reader is not working

Status in linux package in Ubuntu:
  Invalid

Bug description:
  If I start up the computer with no SD card in the reader, it will not
  recognise SD cards inserted.

  WORKAROUND: If you start up the computer with an SD card inserted, all
  is good.

  WORKAROUND: The following rescan will find the SD card.

  sudo su -l
  echo 1 > /sys/bus/pci/rescan

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-24-generic 3.2.0-24.37
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC665 Analog [ALC665 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lee   20624 F pulseaudio
  CRDA:
   country AU:
    (2402 - 2482 @ 40), (N/A, 20)
    (5170 - 5250 @ 40), (3, 23)
    (5250 - 5330 @ 40), (3, 23), DFS
    (5735 - 5835 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf3c0 irq 55'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:10ec0665,10280571,0013 
HDA:80862805,80860101,0010'
     Controls  : 31
     Simple ctrls  : 13
  Date: Mon May  7 13:52:09 2012
  HibernationDevice: RESUME=UUID=131e7674-2f9b-4de3-b917-8d79a5a64e28
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Dell Inc. Dell System XPS L702X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=157174fa-f17e-471d-9008-353e4499b5f8 ro
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic  N/A
   linux-firmware1.79
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: Upgraded to precise on 2012-04-29 (7 days ago)
  dmi.bios.date: 01/10/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 0XN71K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: FAB1
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd01/10/2012:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0XN71K:rvrFAB1:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L702X
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1713553] Re: Intel i40e PF reset due to incorrect MDD detection

2018-01-19 Thread Dan Streetman

@stefan-n1, please move discussion over to bug 1723127, no more comments
should be added to this bug.

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

Title:
  Intel i40e PF reset due to incorrect MDD detection

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

Bug description:
  [Impact]

  Using an Intel i40e network device, under heavy traffic load with
  TSO enabled, the device will spontaneously reset itself and issue errors
  similar to the following:

  Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:53 hostname kernel: [4253915.476283] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:54 hostname kernel: [4253917.411264] i40e :05:00.1: TX 
driver issue detected, PF reset issued

   This causes a full reset of the PF, which causes an interruption
  in traffic flow.

  This was partially fixed by Xenial commit
  12f8cc59d5886b86372f45290166deca57a60d7a, however there is one
  additional upstream commit required to fully fix the issue:

  commit 841493a3f64395b60554afbcaa17f4350f90e764
  Author: Alexander Duyck 
  Date:   Tue Sep 6 18:05:04 2016 -0700

  i40e: Limit TX descriptor count in cases where frag size is
  greater than 16K

   This fix was never backported into the Xenial 4.4 kernel series, but
  is already present in the Xenial HWE (and Zesty) 4.10 kernel.

  [Testcase]

   In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled. Under heavy load, the card will
  reset itself as described.

  [Regression Potential]

  As with any change to a network card driver, this may cause
  regressions with network I/O through i40e card(s).  However, this
  specific change only increases the likelyhood that any specific large
  TSO tx will need to be linearized, which will avoid the PF reset.
  Linearizing a TSO tx that did not need to be linearized will not cause
  any failures, it may only decrease performance slightly.  However this
  patch should only cause linearization when required to avoid the MDD
  detection and PF reset.

  [Other Info]

  The previous bug for this issue is bug 1700834.

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

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

[Kernel-packages] [Bug 1713553] Re: Intel i40e PF reset due to incorrect MDD detection

2018-01-19 Thread Stefan Kooman

H there. I can confirm this problem still exists in newest kernels and
with the latest intel drivers as of today:

Jan 19 16:05:19 osd9 kernel: [511271.581413] i40e :02:00.1: TX driver issue 
detected, PF reset issued
Jan 19 16:09:08 osd9 kernel: [511500.919380] i40e :02:00.0: TX driver issue 
detected, PF reset issued


driver: i40e-2.4.3 (and xenial / 4.13 shipped driver: 2.1.14-k)
kernel: 4.13.0-25-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 12:16:39 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux. Kernel loaded with nopti noibrs noibpb 
(Meltdown / Spetre mitigation disabled). 

We can trigger the issue with high load (benchmarking Ceph cluster with
fio: 4 clients, 8 threads, iodepth 256, 100% random write, 64K block
size).

Only when we use relatively large block size (64K) do we hit this
problem. With 4K blocks we do not hit this issue. We haven't tested
large random reads (that test is still to be done).

When using openvswitch port-channel (as we do) with jumbo frames ...
this port-channel will not come back online after the reset. rmmod i40e
/ modprobe i40e does the trick though.

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

Title:
  Intel i40e PF reset due to incorrect MDD detection

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

Bug description:
  [Impact]

  Using an Intel i40e network device, under heavy traffic load with
  TSO enabled, the device will spontaneously reset itself and issue errors
  similar to the following:

  Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:53 hostname kernel: [4253915.476283] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:54 hostname kernel: [4253917.411264] i40e :05:00.1: TX 
driver issue detected, PF reset issued

   This causes a full reset of the PF, which causes an interruption
  in traffic flow.

  This was partially fixed by Xenial commit
  12f8cc59d5886b86372f45290166deca57a60d7a, however there is one
  additional upstream commit required to fully fix the issue:

  commit 841493a3f64395b60554afbcaa17f4350f90e764
  Author: Alexander Duyck 
  Date:   Tue Sep 6 18:05:04 2016 -0700

  i40e: Limit TX descriptor count in cases where frag size is
  greater than 16K

   This fix was never backported into the Xenial 4.4 kernel series, but
  is already present in the Xenial HWE (and Zesty) 4.10 kernel.

  [Testcase]

   In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled. Under heavy load, the card will
  reset itself as described.

  [Regression Potential]

  As with any change to a network card driver, this may cause
  regressions with network I/O through i40e card(s).  However, this
  specific change only increases the likelyhood that any specific large
  TSO tx will need to be linearized, which will avoid the PF reset.
  Linearizing a TSO tx that did not need to be linearized will not cause
  any failures, it may only decrease performance slightly.  However this
  patch should only cause linearization when required to avoid the MDD
  detection and PF reset.

  [Other Info]

  The previous bug for this issue is bug 1700834.

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

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

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

2018-01-19 Thread Daniele Bianchin

#540

Do you think if i install Ubuntu using that guide and after i update the
kernel i colud fix my bios?

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

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

---

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

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

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

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

---

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

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

---

Affected Machines:

---

Original Description:

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

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

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

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

Thank you!!

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

[Kernel-packages] [Bug 1744309] Re: linux-lts-trusty: 3.13.0-141.190~precise1 -proposed tracker

** Description changed:

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

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

Title:
  linux-lts-trusty: 3.13.0-141.190~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

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

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

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

[Kernel-packages] [Bug 1744294] Re: linux: 4.13.0-31.34 -proposed tracker

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1744295,1742725,1744298,1743418,1742723,1742726
  derivatives: 1743419
+ kernel-stable-phase-changed:Friday, 19. January 2018 17:01 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1744295,1742725,1744298,1743418,1742723,1742726
  derivatives: 1743419
  kernel-stable-phase-changed:Friday, 19. January 2018 17:01 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.13.0-31.34 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1744295,1742725,1744298,1743418,1742723,1742726
  derivatives: 1743419
  kernel-stable-phase-changed:Friday, 19. January 2018 17:01 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1743872] Re: "0BDA:A811" - Not work 802.11ac WLAN Adapter

Hello,

* "0BDA:A811" - I'm working with 802.11ac WLAN Adapter
https://bugs.launchpad.net/bugs/1743872

Regards,
--
Cristian

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

Title:
  "0BDA:A811" - Not work 802.11ac WLAN Adapter

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Not work:
  
https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-30-generic 4.13.0-30.33
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1752 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 17:08:45 2018
  InstallationDate: Installed on 2017-10-13 (96 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-30-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-30-generic N/A
   linux-backports-modules-4.13.0-30-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1744356] [NEW] "0BDA:A811" - I'm working with 802.11ac WLAN Adapter

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

Public bug reported:

Hello,

Open bug in:
* "0BDA:A811" - Not work 802.11ac WLAN Adapter 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743872


== My Guide ==

Compile Realtek rtl8812AU/8821AU USB WiFi driver on Debian Jessie
https://www.erol.name/compile-realtek-rtl8812au8821au-usb-wifi-driver-debian-jessie/


== Disable WiFi Intel ==
/etc/modprobe.d/blacklist.conf
blacklist iwlwifi

[...]

$sudo modprobe -r iwlwifi

Regards,
--
Cristian

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-30-generic 4.13.0-30.33
ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
Uname: Linux 4.13.0-30-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   caravena   1560 F...m pulseaudio
 /dev/snd/controlC0:  caravena   1560 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 19 13:43:15 2018
InstallationDate: Installed on 2017-10-13 (98 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-30-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-30-generic N/A
 linux-backports-modules-4.13.0-30-generic  N/A
 linux-firmware 1.170
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug bionic package-from-proposed

** This bug has been marked a duplicate of bug 1743872
   "0BDA:A811" - Not work 802.11ac WLAN Adapter

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

Title:
  "0BDA:A811" - I'm working with  802.11ac WLAN Adapter

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  Open bug in:
  * "0BDA:A811" - Not work 802.11ac WLAN Adapter 
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743872


  == My Guide ==

  Compile Realtek rtl8812AU/8821AU USB WiFi driver on Debian Jessie
  
https://www.erol.name/compile-realtek-rtl8812au8821au-usb-wifi-driver-debian-jessie/

  
  == Disable WiFi Intel ==
  /etc/modprobe.d/blacklist.conf
  blacklist iwlwifi

  [...]

  $sudo modprobe -r iwlwifi

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-30-generic 4.13.0-30.33
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1560 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1560 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 13:43:15 2018
  InstallationDate: Installed on 2017-10-13 (98 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-30-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-30-generic N/A
   linux-backports-modules-4.13.0-30-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias:

[Kernel-packages] [Bug 1743872] Re: "0BDA:A811" - Not work 802.11ac WLAN Adapter

Hello,

This guide served for me:
https://www.erol.name/compile-realtek-rtl8812au8821au-usb-wifi-driver-debian-jessie/

Regards,
--
Cristian

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

Title:
  "0BDA:A811" - Not work 802.11ac WLAN Adapter

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Not work:
  
https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-30-generic 4.13.0-30.33
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1752 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 17:08:45 2018
  InstallationDate: Installed on 2017-10-13 (96 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-30-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-30-generic N/A
   linux-backports-modules-4.13.0-30-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1742696] Re: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash

Artful SRU request submitted:

https://lists.ubuntu.com/archives/kernel-team/2018-January/089426.html

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

Title:
  Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix
  of Intel SPI bug on certain serial flash

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

Bug description:
  == SRU Justification ==
  New bug forked out of Bug #1734147 "corrupted BIOS due to Intel SPI bug in 
kernel Edit"

  When trying to apply the proposed fix in Bug #1734147 to a Lenovo Yoga
  with Serial Flash s25fl064k, the actual fix works, however reverting
  back to original available Kernel <4.14.x again locks the BIOS for
  write.

  How to identify chip: Using the Fix Kernel from Bug #1734147 the kernel log 
will show intel-spi entries.
  In lower part serial is shown as below:

  intel-spi intel-spi: s25fl064k (8192 Kbytes)

  Additional Information:
  Lenovo Yoga running Linux Mint 18.3 (based on Xenial 16.04)
  Bug #1734147 occured when trying Ubuntu 17.10

  Explanation by Mika Westerberg (Bug #1734147, Comment #524)
  "commit d9018976cdb6 is missing with this particular BIOS/system because 
every time you boot the system, the BIOS resets to default when it finds BCR 
register is changed. This is different issue than the CMP=1 issue most of the 
users have reported. This one also is not permanent so everything is fine as 
long as you don't touch that BCR register. In this case you either need to 
always boot to a kernel where that fix (d9018976cdb6) is included or blacklist 
lpc_ich.ko. Ubuntu v4.14.x kernels have that fix included so you might want to 
take one of them or build your own."

  == Fixes ==
  d9018976cdb6 ("mfd: lpc_ich: Do not touch SPI-NOR write protection bit on 
Haswell/Broadwell")
  9d63f17661e2 ("spi-nor: intel-spi: Fix broken software sequencing codes")

  == Regression Potential ==
  Low, these patches fix an existing critical regression.


  New bug requested to discuss this separate from main Bug #1734147
  Anthony Wong (Bug #1734147, Comment #525)
  "Looks like we need to cherry-pick it to 4.13 after all.
  Christian, do you mind opening a new bug for your issue? We should continue 
the discussion and fix over there."

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

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

[Kernel-packages] [Bug 1742696] Re: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash

** Description changed:

- New bug forked out of Bug #1734147 "corrupted BIOS due to Intel SPI bug
- in kernel Edit"
+ == SRU Justification ==
+ New bug forked out of Bug #1734147 "corrupted BIOS due to Intel SPI bug in 
kernel Edit"
  
  When trying to apply the proposed fix in Bug #1734147 to a Lenovo Yoga
  with Serial Flash s25fl064k, the actual fix works, however reverting
  back to original available Kernel <4.14.x again locks the BIOS for
  write.
  
  How to identify chip: Using the Fix Kernel from Bug #1734147 the kernel log 
will show intel-spi entries.
  In lower part serial is shown as below:
  
  intel-spi intel-spi: s25fl064k (8192 Kbytes)
  
  Additional Information:
  Lenovo Yoga running Linux Mint 18.3 (based on Xenial 16.04)
  Bug #1734147 occured when trying Ubuntu 17.10
  
- 
  Explanation by Mika Westerberg (Bug #1734147, Comment #524)
  "commit d9018976cdb6 is missing with this particular BIOS/system because 
every time you boot the system, the BIOS resets to default when it finds BCR 
register is changed. This is different issue than the CMP=1 issue most of the 
users have reported. This one also is not permanent so everything is fine as 
long as you don't touch that BCR register. In this case you either need to 
always boot to a kernel where that fix (d9018976cdb6) is included or blacklist 
lpc_ich.ko. Ubuntu v4.14.x kernels have that fix included so you might want to 
take one of them or build your own."
+ 
+ == Fixes ==
+ d9018976cdb6 ("mfd: lpc_ich: Do not touch SPI-NOR write protection bit on 
Haswell/Broadwell")
+ 9d63f17661e2 ("spi-nor: intel-spi: Fix broken software sequencing codes")
+ 
+ == Regression Potential ==
+ Low, these patches fix an existing critical regression.
+ 
  
  New bug requested to discuss this separate from main Bug #1734147
  Anthony Wong (Bug #1734147, Comment #525)
  "Looks like we need to cherry-pick it to 4.13 after all.
  Christian, do you mind opening a new bug for your issue? We should continue 
the discussion and fix over there."

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

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

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

Title:
  Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix
  of Intel SPI bug on certain serial flash

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

Bug description:
  == SRU Justification ==
  New bug forked out of Bug #1734147 "corrupted BIOS due to Intel SPI bug in 
kernel Edit"

  When trying to apply the proposed fix in Bug #1734147 to a Lenovo Yoga
  with Serial Flash s25fl064k, the actual fix works, however reverting
  back to original available Kernel <4.14.x again locks the BIOS for
  write.

  How to identify chip: Using the Fix Kernel from Bug #1734147 the kernel log 
will show intel-spi entries.
  In lower part serial is shown as below:

  intel-spi intel-spi: s25fl064k (8192 Kbytes)

  Additional Information:
  Lenovo Yoga running Linux Mint 18.3 (based on Xenial 16.04)
  Bug #1734147 occured when trying Ubuntu 17.10

  Explanation by Mika Westerberg (Bug #1734147, Comment #524)
  "commit d9018976cdb6 is missing with this particular BIOS/system because 
every time you boot the system, the BIOS resets to default when it finds BCR 
register is changed. This is different issue than the CMP=1 issue most of the 
users have reported. This one also is not permanent so everything is fine as 
long as you don't touch that BCR register. In this case you either need to 
always boot to a kernel where that fix (d9018976cdb6) is included or blacklist 
lpc_ich.ko. Ubuntu v4.14.x kernels have that fix included so you might want to 
take one of them or build your own."

  == Fixes ==
  d9018976cdb6 ("mfd: lpc_ich: Do not touch SPI-NOR write protection bit on 
Haswell/Broadwell")
  9d63f17661e2 ("spi-nor: intel-spi: Fix broken software sequencing codes")

  == Regression Potential ==
  Low, these patches fix an existing critical regression.


  New bug requested to discuss this separate from main Bug #1734147
  Anthony Wong (Bug #1734147, Comment #525)
  "Looks like we need to cherry-pick it to 4.13 after all.
  Christian, do you mind opening a new bug for your issue? We should continue 
the discussion and fix over there."

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

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

[Kernel-packages] [Bug 1743269] Re: P-state not working in kernel 4.13

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

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

Title:
  P-state not working in kernel 4.13

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

Bug description:
  == SRU Justification ==
  Commits b29c6ef7bb12 and 7d5905dc14a8 fix a regression in Artful.  They
  were both added to mainline in v4.15-rc1 and fix the following two commits:
  b29c6ef7bb12 Fixes: 4815d3c56d1e (cpufreq: x86: Make scaling_cur_freq behave 
more as expected)
  7d5905dc14a8 Fixes: 890da9cf0983 (Revert "x86: do not use cpufreq_quick_get() 
for /proc/cpuinfo "cpu MHz"")  
  According to the bug report, P-state is not working in Artful, but it was 
working 
  in Zesty.  This bug is happening on a Lenovo Thinkpad X230 with an Intel Core 
i5-3210M CPU.
  The bug reporter is using CPU scaling to improve battery life.

  == Fixes ==
  b29c6ef7bb12 ("x86 / CPU: Avoid unnecessary IPIs in arch_freq_get_on_cpu()")
  7d5905dc14a8 ("x86 / CPU: Always show current CPU frequency in /proc/cpuinfo")

  == Regression Potential ==
  Low.  The two commit fix a current regression and have had additiona upstream 
reviews
  from being send to stable.

  
  ## Original Bug Description ##
  I have a Lenovo Thinkpad X230 with an Intel Core i5-3210M CPU. I'm using 
Xubuntu 17.10 (Description:  Ubuntu 17.10, Release:  17.10). I use tlp 
1.0-1~artful in order to improve battery performance, particularly enabling the 
Intel P-state performance scaling. In Xubuntu 17.04 it worked flawlessly, but 
when I upgraded to 17.10 the processor doesn't scale anymore. I ran all the 
updates and it's not working. I also did a clean install using another hard 
drive and the problem persist.

  I searched the tlp forums and similar problems pointed to a kernel
  bug, so I'm filing this report.

  I tested different mainline kernels in order to see what kernel
  version is causing the problem:

  Up to mainline kernel 4.12.14 generic, P-state scaling is OK
  Kernel 4.13 generic up to kernel 4.14.12 generic, P-state scaling is not 
working
  Kernel 4.14.13 generic up to 4.15 rc7 generic, P-state scaling is OK

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eduar  1686 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 14 18:46:27 2018
  HibernationDevice: RESUME=UUID=ec172c41-ddb8-4d67-8249-390aa1bb6331
  InstallationDate: Installed on 2017-02-07 (341 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 232032U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=a5c459a3-f6c9-40cd-a648-e7b8b28a2ee6 ro radeon.dpm=1 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-13 (1 days ago)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 232032U
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn232032U:pvrThinkPadX230:rvnLENOVO:rn232032U:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 232032U
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1743746] Re: 4.13: unable to increase MTU configuration for GRE devices

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

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

Title:
  4.13: unable to increase MTU configuration for GRE devices

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

Bug description:
  [Impact]
  GRE overlay networks can't carry traffic with MTU > 1500

  [Test Case]
  sudo add-apt-repository cloud-archive:pike
  sudo apt update
  sudo apt install openvswitch-switch
  sudo ovs-vsctl add-br br-tun
  sudo ovs-vsctl add-port br-tun gre0 -- set interface gre0 type=gre 
options:remote_ip=10.100.1.1

  gre_sys device will be configured with MTU 1472.

  sudo ip link set gre_sys mtu 65000

  will fail with EINVAL.

  [Regression Potential]

  [Bug Report]

  Under Linux 4.13 its not possible to configure GRE tunnel devices with
  a MTU larger than 1500; this impacts on Open vSwitch (which creates
  tunnel devices for GRE overlay networking) and the ip tools.

  The kernel will error with:

    gre_sys: Invalid MTU 65000 requested, hw max 1500

  The side effect of this is that if overlay networks are configured
  with high MTUs, the gre devices fragment the packets and networking is
  generally slow/broken.

  This is resolved as part of the upcoming 4.15 kernel under:

  
https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146

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

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

[Kernel-packages] [Bug 1742684] Re: Display res

2018-01-19 Thread Gerry

kernel-bug-exists-upstream

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

Title:
  Display res

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  GPU GeForce 6150SE nForce 430 using Nvidia 304.135 wont go above 1024 display 
resolution. Normally  1920 after upgrading to kernel 4.13.0-26.29
  Mint 18.3 Sylvia
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  acer   1237 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=15e46a87-7fe7-420a-ad37-812be19f62c2
  InstallationDate: Installed on 2017-12-12 (29 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  IwConfig:
   enp0s7no wireless extensions.
   
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7309
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=bcb6f656-ad31-4a57-9f51-138eb65690f6 ro quiet splash
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   
  Tags:  sylvia sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 12/23/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V9.9
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7309
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV9.9:bd12/23/2009:svnMSI:pnMS-7309:pvr1.0:rvnMSI:rnMS-7309:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7309
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1742721] Re: linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic fail to boot

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

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

Title:
  linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic
  fail to boot

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

Bug description:
  == SRU Justification ==
  The following mainline commit introduced a regression in v4.11-rc1:
  c075b6f2d357ea9 ("staging: sm750fb: Replace POKE32 and PEEK32 by inline 
functions")

  This regression caused the bug reporters system to crash and exhibited no 
display 
  output.

  A "Reverse" bisect was performed and it was found that this regression is
  fixed by commit 16808dcf605e6, which was added to mainline in v4.15-rc1.

  
  == Fix ==
  commit 16808dcf605e6302319a8c3266789b76d4c0983b
  Author: Huacai Chen 
  Date:   Mon Nov 6 08:43:03 2017 +0800

  staging: sm750fb: Fix parameter mistake in poke32

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

  
  ## Original Bug Description#
  I've updated the machine to the linux-hwe kernels, and experienced an almost 
instant crash when booting.  Nothing is shown on the VGA output, so no stack 
traces are available.

  I've tried booting a few kernels with the following results:

  - linux-image-4.8.0-56-generic + linux-image-extra-4.8.0-56-generic: boots up 
fine
  - linux-image-4.13.0-26-generic + linux-image-extra-4.13.0-26-generic:  fails 
to boot
  - linux-image-4.13.0-21-generic: boots up, but since no r8169, no networking
  - linux-image-4.13.0-21-generic + linux-image-extra-4.13.0-21-generic:  fails 
to boot
  - linux-image-4.10.0-42-generic + linux-image-extra-4.10.0-42-generic:  boots 
up fine

  After that I've tried some mainline kernels from
  http://kernel.ubuntu.com/~kernel-ppa/mainline to check if the problem
  is the upstream or ubuntu patches:

  - linux-image-4.14.13-041413-generic_4.14.13-041413.201801101001_amd64.deb: 
boots up fine
  - linux-image-4.13.13-041313-generic_4.13.13-041313.201711150531_amd64.deb: 
fails to boot
  - linux-image-4.13.16-041316-generic_4.13.16-041316.201711240901_amd64.deb: 
boots up fine
  - linux-image-4.13.14-041314-generic_4.13.14-041314.201711180632_amd64.deb: 
fails to boot
  - linux-image-4.13.15-041315-generic_4.13.15-041315.201711211030_amd64.deb: 
boots up fine

  So, it seems, the problem is fixed either in patches between 4.13.14
  and 4.13.15 upstream, or ubuntu configs/patches applied to mainline
  kernels.

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

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

[Kernel-packages] [Bug 1741655] Re: Regression: KVM no longer supports Intel CPUs without Virtual NMI

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

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

Title:
  Regression: KVM no longer supports Intel CPUs without Virtual NMI

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

Bug description:
  == SRU Justification ==
  The following mainline commit introduced a regression in v4.12-rc1:
  2c82878b0cb3 ("KVM: VMX: require virtual NMI support")

  This regression caused the kvm-intel module fail to load with the following 
error:
  "modprobe: ERROR: could not insert 'kvm_intel': Input/output error"

  This error would happen because suppor for CPUs without virtual NMI was 
removed
  by commit 2c82878b0cb3.

  Mainline commit 8a1b43922d0d fixes this regression and was added to
  mainline in v4.15-rc1.

  
  == Fix ==
  commit 8a1b43922d0d1279e7936ba85c4c2a870403c95f
  Author: Paolo Bonzini 
  Date:   Mon Nov 6 13:31:12 2017 +0100

  kvm: vmx: Reinstate support for CPUs without virtual NMI

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


  ## Original Bug Description ##
  Since upgrading from zesty to artful, I'm not longer able to use KVM on my 
server:
  # modprobe kvm-intel
  modprobe: ERROR: could not insert 'kvm_intel': Input/output error

  Searching tells me this is caused by requiring Virtual NMI support[1]

  Running the script provided on the mailing list[1] to check virtualization 
features confirms my CPU (Xeon E5345) doesn't support Virtual NMIs:
  # python features.py | grep NMI
    NMI exiting  yes
    Virtual NMIs no
    NMI-window exiting   no

  Virtual NMI support was required in v4.12[1] and later reverted in
  v4.14.3[2] as some models (including Xeons) don't support it, even if
  others with the same core do.

  [1] https://bugzilla.redhat.com/show_bug.cgi?id=1490803
  [2] https://lkml.org/lkml/2017/8/7/231
  [3] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/kvm/vmx.c?h=linux-4.13.y=2c82878b0cb38fd516fd612c67852a6bbf282003
  [4] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/kvm/vmx.c?h=linux-4.14.y=a77360e989f3dc06e4f177a0837d533d13a20d91

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

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

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

This change was made by a bot.

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

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

Title:
  USB devices not recognized after suspend to RAM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a fresh reboot, USB devices / hard disks are recognized
  correctly.

  After the first suspend to RAM, this recognition does not work any
  more.

  USB Flash drives are recognized as xhci_hdc:
  ...
  Jan 19 16:29:39 mbpr13b kernel: [ 4312.095869] usb 2-1: new SuperSpeed USB 
device number 20 using xhci_hcd
  Jan 19 16:29:44 mbpr13b kernel: [ 4317.199585] usb 2-1: device descriptor 
read/8, error -110
  Jan 19 16:29:44 mbpr13b kernel: [ 4317.307436] usb 2-1: new SuperSpeed USB 
device number 20 using xhci_hcd
  Jan 19 16:29:49 mbpr13b kernel: [ 4322.575395] usb 2-1: device descriptor 
read/8, error -110
  Jan 19 16:29:49 mbpr13b kernel: [ 4322.891260] usb 2-1: new SuperSpeed USB 
device number 21 using xhci_hcd
  Jan 19 16:29:55 mbpr13b kernel: [ 4327.951076] usb 2-1: device descriptor 
read/8, error -110
  Jan 19 16:29:55 mbpr13b kernel: [ 4328.058970] usb 2-1: new SuperSpeed USB 
device number 21 using xhci_hcd
  ...
  but do not mount

  Hard disks freeze the system

  Android Phones don't get recognized as xhci_hdc instead of an external 
storage device:
  ...
  Jan 19 16:34:17 mbpr13b kernel: [ 4589.93] usb 1-1: new high-speed USB 
device number 4 using xhci_hcd
  Jan 19 16:34:22 mbpr13b kernel: [ 4595.066102] usb 1-1: device descriptor 
read/64, error -110
  Jan 19 16:34:37 mbpr13b kernel: [ 4610.681476] usb 1-1: device descriptor 
read/64, error -110
  Jan 19 16:34:37 mbpr13b kernel: [ 4610.909265] usb 1-1: new high-speed USB 
device number 5 using xhci_hcd
  Jan 19 16:34:43 mbpr13b kernel: [ 4616.057120] usb 1-1: device descriptor 
read/64, error -110

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-30-generic 4.13.0-30.33
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wolf   1317 F pulseaudio
   /dev/snd/controlC0:  wolf   1317 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 16:30:16 2018
  HibernationDevice: RESUME=UUID=e0d91223-651f-43b1-bb25-12794e7155d4
  InstallationDate: Installed on 2017-10-20 (91 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 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-30-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-30-generic N/A
   linux-backports-modules-4.13.0-30-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: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1743746] Re: 4.13: unable to increase MTU configuration for GRE devices

Submitted Artful and Bionic SRU requests:
https://lists.ubuntu.com/archives/kernel-team/2018-January/089420.html

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

Title:
  4.13: unable to increase MTU configuration for GRE devices

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

Bug description:
  [Impact]
  GRE overlay networks can't carry traffic with MTU > 1500

  [Test Case]
  sudo add-apt-repository cloud-archive:pike
  sudo apt update
  sudo apt install openvswitch-switch
  sudo ovs-vsctl add-br br-tun
  sudo ovs-vsctl add-port br-tun gre0 -- set interface gre0 type=gre 
options:remote_ip=10.100.1.1

  gre_sys device will be configured with MTU 1472.

  sudo ip link set gre_sys mtu 65000

  will fail with EINVAL.

  [Regression Potential]

  [Bug Report]

  Under Linux 4.13 its not possible to configure GRE tunnel devices with
  a MTU larger than 1500; this impacts on Open vSwitch (which creates
  tunnel devices for GRE overlay networking) and the ip tools.

  The kernel will error with:

    gre_sys: Invalid MTU 65000 requested, hw max 1500

  The side effect of this is that if overlay networks are configured
  with high MTUs, the gre devices fragment the packets and networking is
  generally slow/broken.

  This is resolved as part of the upcoming 4.15 kernel under:

  
https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146

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

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

[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel due to mainline commit 24247aeeabe

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

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

Title:
  System hang with Linux kernel due to mainline commit 24247aeeabe

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

Bug description:
  == SRU Justification ==
  The following mainline commit introduced a regression in v4.14-rc1:
  24247aeeabe9 ("x86/intel_rdt/cqm: Improve limbo list processing")

  This commit made it's way into Artful via Launchpad bug 1591609 as Artful 
commit
  ac2fc5adab0f4b.

  This bug was causing regression tests to hang about one in four
  times when running cpu_offlining tests.

  This patch to fix this regression was just submitted to mainline, so it is 
also
  needed in Bionic.

  == Fix ==
  commit d47924417319e3b6a728c0b690f183e75bc2a702
  Author: Thomas Gleixner 
  Date:   Tue Jan 16 19:59:59 2018 +0100

  x86/intel_rdt/cqm: Prevent use after free

  == Regression Potential ==
  Low.  This patch fixes a current regression that is a use after free.


  ### Original Bug Description ###
  In doing Ubuntu 17.10 regression testing, we've encountered one computer 
(boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when 
running our cpu_offlining test. This test attempts to take all the CPU cores 
offline except one, then brings them back online again. This test ran 
successfully on boldore with previous releases, but with 17.10, the system 
sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found 
no problems; but when I upgraded the 16.04.3 installation to 
linux-image-4.13.0-16-generic, the problem appeared again, so I'm confident 
this is a problem with the kernel. I'm attaching two files, 
dmesg-output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output 
that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 
kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg 
-w" in a second SSH login; the files are cut-and-pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1743746] Re: 4.13: unable to increase MTU configuration for GRE devices

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

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

Title:
  4.13: unable to increase MTU configuration for GRE devices

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

Bug description:
  [Impact]
  GRE overlay networks can't carry traffic with MTU > 1500

  [Test Case]
  sudo add-apt-repository cloud-archive:pike
  sudo apt update
  sudo apt install openvswitch-switch
  sudo ovs-vsctl add-br br-tun
  sudo ovs-vsctl add-port br-tun gre0 -- set interface gre0 type=gre 
options:remote_ip=10.100.1.1

  gre_sys device will be configured with MTU 1472.

  sudo ip link set gre_sys mtu 65000

  will fail with EINVAL.

  [Regression Potential]

  [Bug Report]

  Under Linux 4.13 its not possible to configure GRE tunnel devices with
  a MTU larger than 1500; this impacts on Open vSwitch (which creates
  tunnel devices for GRE overlay networking) and the ip tools.

  The kernel will error with:

    gre_sys: Invalid MTU 65000 requested, hw max 1500

  The side effect of this is that if overlay networks are configured
  with high MTUs, the gre devices fragment the packets and networking is
  generally slow/broken.

  This is resolved as part of the upcoming 4.15 kernel under:

  
https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146

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

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

[Kernel-packages] [Bug 1744077] Re: $(LOCAL_ENV_CC) and $(LOCAL_ENV_DISTCC_HOSTS) should be properly quoted

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

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

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

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

Title:
  $(LOCAL_ENV_CC) and $(LOCAL_ENV_DISTCC_HOSTS) should be properly
  quoted

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  New
Status in linux source package in Artful:
  New

Bug description:
  Kernel will fail to build if there's a space in either $(LOCAL_ENV_CC)
  or $(LOCAL_ENV_DISTCC_HOSTS), for example if someone trying to use
  LOCAL_ENV_CC="ccache gcc".

  This is caused by the line in debian/rules.d/0-common-vars.mk which both of 
them are passed without quote:
  kmake += CC=$(LOCAL_ENV_CC) DISTCC_HOSTS=$(LOCAL_ENV_DISTCC_HOSTS)

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

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

[Kernel-packages] [Bug 1743269] Re: P-state not working in kernel 4.13

Submitted SRU request for Artful and Bionic:
https://lists.ubuntu.com/archives/kernel-team/2018-January/089416.html

** Description changed:

- I have a Lenovo Thinkpad X230 with an Intel Core i5-3210M CPU. I'm using
- Xubuntu 17.10 (Description:Ubuntu 17.10, Release:  17.10). I use tlp
- 1.0-1~artful in order to improve battery performance, particularly
- enabling the Intel P-state performance scaling. In Xubuntu 17.04 it
- worked flawlessly, but when I upgraded to 17.10 the processor doesn't
- scale anymore. I ran all the updates and it's not working. I also did a
- clean install using another hard drive and the problem persist.
+ == SRU Justification ==
+ Commits b29c6ef7bb12 and 7d5905dc14a8 fix a regression in Artful.  They
+ were both added to mainline in v4.15-rc1 and fix the following two commits:
+ b29c6ef7bb12 Fixes: 4815d3c56d1e (cpufreq: x86: Make scaling_cur_freq behave 
more as expected)
+ 7d5905dc14a8 Fixes: 890da9cf0983 (Revert "x86: do not use cpufreq_quick_get() 
for /proc/cpuinfo "cpu MHz"")  
+ According to the bug report, P-state is not working in Artful, but it was 
working 
+ in Zesty.  This bug is happening on a Lenovo Thinkpad X230 with an Intel Core 
i5-3210M CPU.
+ The bug reporter is using CPU scaling to improve battery life.
+ 
+ == Fixes ==
+ b29c6ef7bb12 ("x86 / CPU: Avoid unnecessary IPIs in arch_freq_get_on_cpu()")
+ 7d5905dc14a8 ("x86 / CPU: Always show current CPU frequency in /proc/cpuinfo")
+ 
+ == Regression Potential ==
+ Low.  The two commit fix a current regression and have had additiona upstream 
reviews
+ from being send to stable.
+ 
+ 
+ ## Original Bug Description ##
+ I have a Lenovo Thinkpad X230 with an Intel Core i5-3210M CPU. I'm using 
Xubuntu 17.10 (Description:  Ubuntu 17.10, Release:  17.10). I use tlp 
1.0-1~artful in order to improve battery performance, particularly enabling the 
Intel P-state performance scaling. In Xubuntu 17.04 it worked flawlessly, but 
when I upgraded to 17.10 the processor doesn't scale anymore. I ran all the 
updates and it's not working. I also did a clean install using another hard 
drive and the problem persist.
  
  I searched the tlp forums and similar problems pointed to a kernel bug,
  so I'm filing this report.
  
  I tested different mainline kernels in order to see what kernel version
  is causing the problem:
  
  Up to mainline kernel 4.12.14 generic, P-state scaling is OK
  Kernel 4.13 generic up to kernel 4.14.12 generic, P-state scaling is not 
working
  Kernel 4.14.13 generic up to 4.15 rc7 generic, P-state scaling is OK
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  eduar  1686 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  eduar  1686 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 14 18:46:27 2018
  HibernationDevice: RESUME=UUID=ec172c41-ddb8-4d67-8249-390aa1bb6331
  InstallationDate: Installed on 2017-02-07 (341 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 232032U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=a5c459a3-f6c9-40cd-a648-e7b8b28a2ee6 ro radeon.dpm=1 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.13.0-25-generic N/A
-  linux-backports-modules-4.13.0-25-generic  N/A
-  linux-firmware 1.169.1
+  linux-restricted-modules-4.13.0-25-generic N/A
+  linux-backports-modules-4.13.0-25-generic  N/A
+  linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-13 (1 days ago)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 232032U
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn232032U:pvrThinkPadX230:rvnLENOVO:rn232032U:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 232032U
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

Title:
  P-state not working in kernel 4.13

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

Bug description:
  == SRU Justification ==
  Commits b29c6ef7bb12

[Kernel-packages] [Bug 1744337] Re: USB devices not recognized after suspend to RAM

2018-01-19 Thread Wolf Rogner

lsusb does not report devices

MicroPython board is not recognized either

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

Title:
  USB devices not recognized after suspend to RAM

Status in linux package in Ubuntu:
  New

Bug description:
  After a fresh reboot, USB devices / hard disks are recognized
  correctly.

  After the first suspend to RAM, this recognition does not work any
  more.

  USB Flash drives are recognized as xhci_hdc:
  ...
  Jan 19 16:29:39 mbpr13b kernel: [ 4312.095869] usb 2-1: new SuperSpeed USB 
device number 20 using xhci_hcd
  Jan 19 16:29:44 mbpr13b kernel: [ 4317.199585] usb 2-1: device descriptor 
read/8, error -110
  Jan 19 16:29:44 mbpr13b kernel: [ 4317.307436] usb 2-1: new SuperSpeed USB 
device number 20 using xhci_hcd
  Jan 19 16:29:49 mbpr13b kernel: [ 4322.575395] usb 2-1: device descriptor 
read/8, error -110
  Jan 19 16:29:49 mbpr13b kernel: [ 4322.891260] usb 2-1: new SuperSpeed USB 
device number 21 using xhci_hcd
  Jan 19 16:29:55 mbpr13b kernel: [ 4327.951076] usb 2-1: device descriptor 
read/8, error -110
  Jan 19 16:29:55 mbpr13b kernel: [ 4328.058970] usb 2-1: new SuperSpeed USB 
device number 21 using xhci_hcd
  ...
  but do not mount

  Hard disks freeze the system

  Android Phones don't get recognized as xhci_hdc instead of an external 
storage device:
  ...
  Jan 19 16:34:17 mbpr13b kernel: [ 4589.93] usb 1-1: new high-speed USB 
device number 4 using xhci_hcd
  Jan 19 16:34:22 mbpr13b kernel: [ 4595.066102] usb 1-1: device descriptor 
read/64, error -110
  Jan 19 16:34:37 mbpr13b kernel: [ 4610.681476] usb 1-1: device descriptor 
read/64, error -110
  Jan 19 16:34:37 mbpr13b kernel: [ 4610.909265] usb 1-1: new high-speed USB 
device number 5 using xhci_hcd
  Jan 19 16:34:43 mbpr13b kernel: [ 4616.057120] usb 1-1: device descriptor 
read/64, error -110

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-30-generic 4.13.0-30.33
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wolf   1317 F pulseaudio
   /dev/snd/controlC0:  wolf   1317 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 16:30:16 2018
  HibernationDevice: RESUME=UUID=e0d91223-651f-43b1-bb25-12794e7155d4
  InstallationDate: Installed on 2017-10-20 (91 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 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-30-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-30-generic N/A
   linux-backports-modules-4.13.0-30-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: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task

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

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  So I just upgrade from zesty zapus to artful aardvark. At boot, right
  after I enter my drive encryption password, it kernel panics with the
  above message.

  It doesn't even get far enough along in the boot process for syslog to
  log this panic, so the only info I have is a photo of the panic.

  In short, I can't boot using the latest artful aardvark kernel, and I
  have to boot with the latest zesty zapus kernel.

  :~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  linux-image-4.13.0-16-generic

  I expect this isn't normal and I should be able to boot with the new
  kernel, which I can't.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lost   2071 F pulseaudio
   /dev/snd/controlC2:  lost   2071 F pulseaudio
   /dev/snd/controlC0:  lost   2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 23 12:52:20 2017
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (355 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1742759] Re: boot failure on AMD Raven + WesternXT

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

Title:
  boot failure on AMD Raven + WesternXT

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  This issue has been fixed with with patch:
  https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-drm-
  next=e639173a30efab97dabcf2229362aacd8f46a894

  drm/amdgpu: add atpx quirk handling (v2)
  Add quirks for handling PX/HG systems.  In this case, add
  a quirk for a weston dGPU that only seems to properly power
  down using ATPX power control rather than HG (_PR3).

  v2: append a new weston XT

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

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

[Kernel-packages] [Bug 1742721] Re: linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic fail to boot

SRU request submitted for Artful and Bionic:
https://lists.ubuntu.com/archives/kernel-team/2018-January/089407.html

** Description changed:

- I've updated the machine to the linux-hwe kernels, and experienced an
- almost instant crash when booting.  Nothing is shown on the VGA output,
- so no stack traces are available.
+ == SRU Justification ==
+ The following mainline commit introduced a regression in v4.11-rc1:
+ c075b6f2d357ea9 ("staging: sm750fb: Replace POKE32 and PEEK32 by inline 
functions")
+ 
+ This regression caused the bug reporters system to crash and exhibited no 
display 
+ output.
+ 
+ A "Reverse" bisect was performed and it was found that this regression is
+ fixed by commit 16808dcf605e6, which was added to mainline in v4.15-rc1.
+ 
+ 
+ == Fix ==
+ commit 16808dcf605e6302319a8c3266789b76d4c0983b
+ Author: Huacai Chen 
+ Date:   Mon Nov 6 08:43:03 2017 +0800
+ 
+ staging: sm750fb: Fix parameter mistake in poke32
+ 
+ == Regression Potential ==
+ Low.  This patch fixes a current regression.  It was cc'd to upstream stable
+ so had additional upstream review.
+ 
+ 
+ ## Original Bug Description#
+ I've updated the machine to the linux-hwe kernels, and experienced an almost 
instant crash when booting.  Nothing is shown on the VGA output, so no stack 
traces are available.
  
  I've tried booting a few kernels with the following results:
  
  - linux-image-4.8.0-56-generic + linux-image-extra-4.8.0-56-generic: boots up 
fine
  - linux-image-4.13.0-26-generic + linux-image-extra-4.13.0-26-generic:  fails 
to boot
  - linux-image-4.13.0-21-generic: boots up, but since no r8169, no networking
  - linux-image-4.13.0-21-generic + linux-image-extra-4.13.0-21-generic:  fails 
to boot
  - linux-image-4.10.0-42-generic + linux-image-extra-4.10.0-42-generic:  boots 
up fine
  
  After that I've tried some mainline kernels from
  http://kernel.ubuntu.com/~kernel-ppa/mainline to check if the problem is
  the upstream or ubuntu patches:
  
  - linux-image-4.14.13-041413-generic_4.14.13-041413.201801101001_amd64.deb: 
boots up fine
  - linux-image-4.13.13-041313-generic_4.13.13-041313.201711150531_amd64.deb: 
fails to boot
  - linux-image-4.13.16-041316-generic_4.13.16-041316.201711240901_amd64.deb: 
boots up fine
  - linux-image-4.13.14-041314-generic_4.13.14-041314.201711180632_amd64.deb: 
fails to boot
  - linux-image-4.13.15-041315-generic_4.13.15-041315.201711211030_amd64.deb: 
boots up fine
  
  So, it seems, the problem is fixed either in patches between 4.13.14 and
  4.13.15 upstream, or ubuntu configs/patches applied to mainline kernels.

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

Title:
  linux-image-4.13.0-26-generic / linux-image-extra-4.13.0-26-generic
  fail to boot

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

Bug description:
  == SRU Justification ==
  The following mainline commit introduced a regression in v4.11-rc1:
  c075b6f2d357ea9 ("staging: sm750fb: Replace POKE32 and PEEK32 by inline 
functions")

  This regression caused the bug reporters system to crash and exhibited no 
display 
  output.

  A "Reverse" bisect was performed and it was found that this regression is
  fixed by commit 16808dcf605e6, which was added to mainline in v4.15-rc1.

  
  == Fix ==
  commit 16808dcf605e6302319a8c3266789b76d4c0983b
  Author: Huacai Chen 
  Date:   Mon Nov 6 08:43:03 2017 +0800

  staging: sm750fb: Fix parameter mistake in poke32

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

  
  ## Original Bug Description#
  I've updated the machine to the linux-hwe kernels, and experienced an almost 
instant crash when booting.  Nothing is shown on the VGA output, so no stack 
traces are available.

  I've tried booting a few kernels with the following results:

  - linux-image-4.8.0-56-generic + linux-image-extra-4.8.0-56-generic: boots up 
fine
  - linux-image-4.13.0-26-generic + linux-image-extra-4.13.0-26-generic:  fails 
to boot
  - linux-image-4.13.0-21-generic: boots up, but since no r8169, no networking
  - linux-image-4.13.0-21-generic + linux-image-extra-4.13.0-21-generic:  fails 
to boot
  - linux-image-4.10.0-42-generic + linux-image-extra-4.10.0-42-generic:  boots 
up fine

  After that I've tried some mainline kernels from
  http://kernel.ubuntu.com/~kernel-ppa/mainline to check if the problem
  is the upstream or ubuntu patches:

  - linux-image-4.14.13-041413-generic_4.14.13-041413.201801101001_amd64.deb: 
boots up fine
  - linux-image-4.13.13-041313-generic_4.13.13-041313.201711150531_amd64.deb: 
fails to boot
  - linux-image-4.13.16-041316-generic_4.13.16-041316.201711240901_amd64.deb: 
boots up fine
  -

[Kernel-packages] [Bug 1744330] Re: Bionic update to v4.14.14 stable release

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

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

Title:
  Bionic update to v4.14.14 stable release

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.14.14 stable release shall be
  applied:

  dm bufio: fix shrinker scans when (nr_to_scan < retain_target)
  KVM: Fix stack-out-of-bounds read in write_mmio
  can: vxcan: improve handling of missing peer name attribute
  can: gs_usb: fix return value of the "set_bittiming" callback
  IB/srpt: Disable RDMA access by the initiator
  IB/srpt: Fix ACL lookup during login
  MIPS: Validate PR_SET_FP_MODE prctl(2) requests against the ABI of the task
  MIPS: Factor out NT_PRFPREG regset access helpers
  MIPS: Guard against any partial write attempt with PTRACE_SETREGSET
  MIPS: Consistently handle buffer counter with PTRACE_SETREGSET
  MIPS: Fix an FCSR access API regression with NT_PRFPREG and MSA
  MIPS: Also verify sizeof `elf_fpreg_t' with PTRACE_SETREGSET
  MIPS: Disallow outsized PTRACE_SETREGSET NT_PRFPREG regset accesses
  cgroup: fix css_task_iter crash on CSS_TASK_ITER_PROC
  kvm: vmx: Scrub hardware GPRs at VM-exit
  platform/x86: wmi: Call acpi_wmi_init() later
  iw_cxgb4: only call the cq comp_handler when the cq is armed
  iw_cxgb4: atomically flush the qp
  iw_cxgb4: only clear the ARMED bit if a notification is needed
  iw_cxgb4: reflect the original WR opcode in drain cqes
  iw_cxgb4: when flushing, complete all wrs in a chain
  x86/acpi: Handle SCI interrupts above legacy space gracefully
  ALSA: pcm: Remove incorrect snd_BUG_ON() usages
  ALSA: pcm: Workaround for weird PulseAudio behavior on rewind error
  ALSA: pcm: Add missing error checks in OSS emulation plugin builder
  ALSA: pcm: Abort properly at pending signal in OSS read/write loops
  ALSA: pcm: Allow aborting mutex lock at OSS read/write loops
  ALSA: aloop: Release cable upon open error path
  ALSA: aloop: Fix inconsistent format due to incomplete rule
  ALSA: aloop: Fix racy hw constraints adjustment
  x86/acpi: Reduce code duplication in mp_override_legacy_irq()
  8021q: fix a memory leak for VLAN 0 device
  ip6_tunnel: disable dst caching if tunnel is dual-stack
  net: core: fix module type in sock_diag_bind
  phylink: ensure we report link down when LOS asserted
  RDS: Heap OOB write in rds_message_alloc_sgs()
  RDS: null pointer dereference in rds_atomic_free_op
  net: fec: restore dev_id in the cases of probe error
  net: fec: defer probe if regulator is not ready
  net: fec: free/restore resource in related probe error pathes
  sctp: do not retransmit upon FragNeeded if PMTU discovery is disabled
  sctp: fix the handling of ICMP Frag Needed for too small MTUs
  sh_eth: fix TSU resource handling
  net: stmmac: enable EEE in MII, GMII or RGMII only
  sh_eth: fix SH7757 GEther initialization
  ipv6: fix possible mem leaks in ipv6_make_skb()
  ethtool: do not print warning for applications using legacy API
  mlxsw: spectrum_router: Fix NULL pointer deref
  net/sched: Fix update of lastuse in act modules implementing stats_update
  ipv6: sr: fix TLVs not being copied using setsockopt
  mlxsw: spectrum: Relax sanity checks during enslavement
  sfp: fix sfp-bus oops when removing socket/upstream
  membarrier: Disable preemption when calling smp_call_function_many()
  crypto: algapi - fix NULL dereference in crypto_remove_spawns()
  mmc: renesas_sdhi: Add MODULE_LICENSE
  rbd: reacquire lock should update lock owner client id
  rbd: set max_segments to USHRT_MAX
  iwlwifi: pcie: fix DMA memory mapping / unmapping
  x86/microcode/intel: Extend BDW late-loading with a revision check
  KVM: x86: Add memory barrier on vmcs field lookup
  KVM: PPC: Book3S PR: Fix WIMG handling under pHyp
  KVM: PPC: Book3S HV: Drop prepare_done from struct kvm_resize_hpt
  KVM: PPC: Book3S HV: Fix use after free in case of multiple resize requests
  KVM: PPC: Book3S HV: Always flush TLB in kvmppc_alloc_reset_hpt()
  drm/vmwgfx: Don't cache framebuffer maps
  drm/vmwgfx: Potential off by one in vmw_view_add()
  drm/i915/gvt: Clear the shadow page table entry after post-sync
  drm/i915: Whitelist SLICE_COMMON_ECO_CHICKEN1 on Geminilake.
  drm/i915: Move init_clock_gating() back to where it was
  drm/i915: Fix

[Kernel-packages] [Bug 1744330] [NEW] Bionic update to v4.14.14 stable release

Public bug reported:

SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.14.14 stable release shall be
applied:

dm bufio: fix shrinker scans when (nr_to_scan < retain_target)
KVM: Fix stack-out-of-bounds read in write_mmio
can: vxcan: improve handling of missing peer name attribute
can: gs_usb: fix return value of the "set_bittiming" callback
IB/srpt: Disable RDMA access by the initiator
IB/srpt: Fix ACL lookup during login
MIPS: Validate PR_SET_FP_MODE prctl(2) requests against the ABI of the task
MIPS: Factor out NT_PRFPREG regset access helpers
MIPS: Guard against any partial write attempt with PTRACE_SETREGSET
MIPS: Consistently handle buffer counter with PTRACE_SETREGSET
MIPS: Fix an FCSR access API regression with NT_PRFPREG and MSA
MIPS: Also verify sizeof `elf_fpreg_t' with PTRACE_SETREGSET
MIPS: Disallow outsized PTRACE_SETREGSET NT_PRFPREG regset accesses
cgroup: fix css_task_iter crash on CSS_TASK_ITER_PROC
kvm: vmx: Scrub hardware GPRs at VM-exit
platform/x86: wmi: Call acpi_wmi_init() later
iw_cxgb4: only call the cq comp_handler when the cq is armed
iw_cxgb4: atomically flush the qp
iw_cxgb4: only clear the ARMED bit if a notification is needed
iw_cxgb4: reflect the original WR opcode in drain cqes
iw_cxgb4: when flushing, complete all wrs in a chain
x86/acpi: Handle SCI interrupts above legacy space gracefully
ALSA: pcm: Remove incorrect snd_BUG_ON() usages
ALSA: pcm: Workaround for weird PulseAudio behavior on rewind error
ALSA: pcm: Add missing error checks in OSS emulation plugin builder
ALSA: pcm: Abort properly at pending signal in OSS read/write loops
ALSA: pcm: Allow aborting mutex lock at OSS read/write loops
ALSA: aloop: Release cable upon open error path
ALSA: aloop: Fix inconsistent format due to incomplete rule
ALSA: aloop: Fix racy hw constraints adjustment
x86/acpi: Reduce code duplication in mp_override_legacy_irq()
8021q: fix a memory leak for VLAN 0 device
ip6_tunnel: disable dst caching if tunnel is dual-stack
net: core: fix module type in sock_diag_bind
phylink: ensure we report link down when LOS asserted
RDS: Heap OOB write in rds_message_alloc_sgs()
RDS: null pointer dereference in rds_atomic_free_op
net: fec: restore dev_id in the cases of probe error
net: fec: defer probe if regulator is not ready
net: fec: free/restore resource in related probe error pathes
sctp: do not retransmit upon FragNeeded if PMTU discovery is disabled
sctp: fix the handling of ICMP Frag Needed for too small MTUs
sh_eth: fix TSU resource handling
net: stmmac: enable EEE in MII, GMII or RGMII only
sh_eth: fix SH7757 GEther initialization
ipv6: fix possible mem leaks in ipv6_make_skb()
ethtool: do not print warning for applications using legacy API
mlxsw: spectrum_router: Fix NULL pointer deref
net/sched: Fix update of lastuse in act modules implementing stats_update
ipv6: sr: fix TLVs not being copied using setsockopt
mlxsw: spectrum: Relax sanity checks during enslavement
sfp: fix sfp-bus oops when removing socket/upstream
membarrier: Disable preemption when calling smp_call_function_many()
crypto: algapi - fix NULL dereference in crypto_remove_spawns()
mmc: renesas_sdhi: Add MODULE_LICENSE
rbd: reacquire lock should update lock owner client id
rbd: set max_segments to USHRT_MAX
iwlwifi: pcie: fix DMA memory mapping / unmapping
x86/microcode/intel: Extend BDW late-loading with a revision check
KVM: x86: Add memory barrier on vmcs field lookup
KVM: PPC: Book3S PR: Fix WIMG handling under pHyp
KVM: PPC: Book3S HV: Drop prepare_done from struct kvm_resize_hpt
KVM: PPC: Book3S HV: Fix use after free in case of multiple resize requests
KVM: PPC: Book3S HV: Always flush TLB in kvmppc_alloc_reset_hpt()
drm/vmwgfx: Don't cache framebuffer maps
drm/vmwgfx: Potential off by one in vmw_view_add()
drm/i915/gvt: Clear the shadow page table entry after post-sync
drm/i915: Whitelist SLICE_COMMON_ECO_CHICKEN1 on Geminilake.
drm/i915: Move init_clock_gating() back to where it was
drm/i915: Fix init_clock_gating for resume
bpf: prevent out-of-bounds speculation
bpf, array: fix overflow in max_entries and undefined behavior in index_mask
bpf: arsh is not supported in 32 bit alu thus reject it
USB: serial: cp210x: add IDs for LifeScan OneTouch Verio IQ
USB: serial: cp210x: add new device ID ELV ALC 8xxx
usb: misc: usb3503: make sure reset is low for at least 100us
USB: fix usbmon BUG trigger
USB: UDC core: fix double-free in usb_add_gadget_udc_release
usbip: remove kernel addresses from usb device

[Kernel-packages] [Bug 1741655] Re: Regression: KVM no longer supports Intel CPUs without Virtual NMI

SRU request submitted for Artful and Bionic:
https://lists.ubuntu.com/archives/kernel-team/2018-January/089404.html

** Description changed:

+ == SRU Justification ==
+ The following mainline commit introduced a regression in v4.12-rc1:
+ 2c82878b0cb3 ("KVM: VMX: require virtual NMI support")
+ 
+ This regression caused the kvm-intel module fail to load with the following 
error:
+ "modprobe: ERROR: could not insert 'kvm_intel': Input/output error"
+ 
+ This error would happen because suppor for CPUs without virtual NMI was 
removed
+ by commit 2c82878b0cb3.
+ 
+ Mainline commit 8a1b43922d0d fixes this regression and was added to
+ mainline in v4.15-rc1.
+ 
+ 
+ == Fix ==
+ commit 8a1b43922d0d1279e7936ba85c4c2a870403c95f
+ Author: Paolo Bonzini 
+ Date:   Mon Nov 6 13:31:12 2017 +0100
+ 
+ kvm: vmx: Reinstate support for CPUs without virtual NMI
+ 
+ == Regression Potential ==
+ Low.  This patch fixes a current regression.  It was cc'd to upstream stable
+ so had additional upstream review.
+ 
+ 
+ ## Original Bug Description ##
  Since upgrading from zesty to artful, I'm not longer able to use KVM on my 
server:
  # modprobe kvm-intel
  modprobe: ERROR: could not insert 'kvm_intel': Input/output error
  
  Searching tells me this is caused by requiring Virtual NMI support[1]
  
  Running the script provided on the mailing list[1] to check virtualization 
features confirms my CPU (Xeon E5345) doesn't support Virtual NMIs:
  # python features.py | grep NMI
-   NMI exiting  yes
-   Virtual NMIs no
-   NMI-window exiting   no
+   NMI exiting  yes
+   Virtual NMIs no
+   NMI-window exiting   no
  
  Virtual NMI support was required in v4.12[1] and later reverted in
  v4.14.3[2] as some models (including Xeons) don't support it, even if
  others with the same core do.
  
- 
  [1] https://bugzilla.redhat.com/show_bug.cgi?id=1490803
  [2] https://lkml.org/lkml/2017/8/7/231
  [3] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/kvm/vmx.c?h=linux-4.13.y=2c82878b0cb38fd516fd612c67852a6bbf282003
  [4] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/kvm/vmx.c?h=linux-4.14.y=a77360e989f3dc06e4f177a0837d533d13a20d91

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

Title:
  Regression: KVM no longer supports Intel CPUs without Virtual NMI

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

Bug description:
  == SRU Justification ==
  The following mainline commit introduced a regression in v4.12-rc1:
  2c82878b0cb3 ("KVM: VMX: require virtual NMI support")

  This regression caused the kvm-intel module fail to load with the following 
error:
  "modprobe: ERROR: could not insert 'kvm_intel': Input/output error"

  This error would happen because suppor for CPUs without virtual NMI was 
removed
  by commit 2c82878b0cb3.

  Mainline commit 8a1b43922d0d fixes this regression and was added to
  mainline in v4.15-rc1.

  
  == Fix ==
  commit 8a1b43922d0d1279e7936ba85c4c2a870403c95f
  Author: Paolo Bonzini 
  Date:   Mon Nov 6 13:31:12 2017 +0100

  kvm: vmx: Reinstate support for CPUs without virtual NMI

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


  ## Original Bug Description ##
  Since upgrading from zesty to artful, I'm not longer able to use KVM on my 
server:
  # modprobe kvm-intel
  modprobe: ERROR: could not insert 'kvm_intel': Input/output error

  Searching tells me this is caused by requiring Virtual NMI support[1]

  Running the script provided on the mailing list[1] to check virtualization 
features confirms my CPU (Xeon E5345) doesn't support Virtual NMIs:
  # python features.py | grep NMI
    NMI exiting  yes
    Virtual NMIs no
    NMI-window exiting   no

  Virtual NMI support was required in v4.12[1] and later reverted in
  v4.14.3[2] as some models (including Xeons) don't support it, even if
  others with the same core do.

  [1] https://bugzilla.redhat.com/show_bug.cgi?id=1490803
  [2] https://lkml.org/lkml/2017/8/7/231
  [3] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/kvm/vmx.c?h=linux-4.13.y=2c82878b0cb38fd516fd612c67852a6bbf282003
  [4] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/kvm/vmx.c?h=linux-4.14.y=a77360e989f3dc06e4f177a0837d533d13a20d91

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1744173] Re: artful: rfi-flush: Switch to new linear fallback flush

2018-01-19 Thread Frank Heimes

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

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

Title:
  artful: rfi-flush: Switch to new linear fallback flush

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

Bug description:
  Change flush from congruence-first with dependencies to linear with
  no dependencies, which increases flush performance by 8x on P8, and
  3x on P9 (as measured with null syscall loop, which will have the
  flush area in the L2).

  The flush also becomes simpler and more adaptable to different cache
  geometries.

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

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

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

2018-01-19 Thread bugproxy

--- Comment From bren...@br.ibm.com 2018-01-19 09:33 EDT---
Canonical, please target this one for Xenial GA (4.4) also, please.
This also affects Xenial and I am attaching the backport of the fix for 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/1744173

Title:
  artful: rfi-flush: Switch to new linear fallback flush

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

Bug description:
  Change flush from congruence-first with dependencies to linear with
  no dependencies, which increases flush performance by 8x on P8, and
  3x on P9 (as measured with null syscall loop, which will have the
  flush area in the L2).

  The flush also becomes simpler and more adaptable to different cache
  geometries.

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

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

[Kernel-packages] [Bug 1743766] Re: reboot/IKVM problems on Ubuntu 14.04

2018-01-19 Thread Roman Rykhlitskyy

So test results:
3.13.0-136 kernel has same bug.
Tried 4.4.0-109 kernel and it works fine without bugs.

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

Title:
  reboot/IKVM problems on Ubuntu 14.04

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed

Bug description:
  On the 3.13.0-52-generic #86-Ubuntu kernel server worked perfectly fine.
  To mitigate meltdown vulnerability updated kernel to 3.13.0-139-generic 
#188-Ubuntu.

  Approximately one hour after system boots I get this bug. I can`t access 
server via IKVM(ssh works fine).
  Also I got problem with server reboot. On "reboot" or "init 6" commands 
server halts. Only option is to reset server via IPMI. After server reseted and 
system boots, IKVM and reboot works as intended for approximately one hour. 
Then bug is repeated.

  linux-image-3.13.0-139-generic:
Installed: 3.13.0-139.188
Candidate: 3.13.0-139.188

  Distributor ID: Ubuntu
  Description:Ubuntu 14.04 LTS
  Release:14.04
  Codename:   trusty

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

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

[Kernel-packages] [Bug 1744173] Xenial GA wave2 patches

2018-01-19 Thread bugproxy

--- Comment (attachment only) From bren...@br.ibm.com 2018-01-19 09:34 
EDT---


** Attachment added: "Xenial GA wave2 patches"
   
https://bugs.launchpad.net/bugs/1744173/+attachment/5039556/+files/xenial_ga_wave2.tgz

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

Title:
  artful: rfi-flush: Switch to new linear fallback flush

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

Bug description:
  Change flush from congruence-first with dependencies to linear with
  no dependencies, which increases flush performance by 8x on P8, and
  3x on P9 (as measured with null syscall loop, which will have the
  flush area in the L2).

  The flush also becomes simpler and more adaptable to different cache
  geometries.

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

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

[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel due to mainline commit 24247aeeabe

SRU request submitted for Artful and Bionic.

https://lists.ubuntu.com/archives/kernel-team/2018-January/089403.html

** Description changed:

- In doing Ubuntu 17.10 regression testing, we've encountered one computer
- (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times
- when running our cpu_offlining test. This test attempts to take all the
- CPU cores offline except one, then brings them back online again. This
- test ran successfully on boldore with previous releases, but with 17.10,
- the system sometimes (about one in four runs) hangs. Reverting to Ubuntu
- 16.04.3, I found no problems; but when I upgraded the 16.04.3
- installation to linux-image-4.13.0-16-generic, the problem appeared
- again, so I'm confident this is a problem with the kernel. I'm attaching
- two files, dmesg-output-4.10.txt and dmesg-output-4.13.txt, which show
- the dmesg output that appears when running the cpu_offlining test with
- 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the
- 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are
- cut-and-pasted from that.)
+ == SRU Justification ==
+ The following mainline commit introduced a regression in v4.14-rc1:
+ 24247aeeabe9 ("x86/intel_rdt/cqm: Improve limbo list processing")
+ 
+ This commit made it's way into Artful via Launchpad bug 1591609 as Artful 
commit
+ ac2fc5adab0f4b.
+ 
+ This bug was causing regression tests to hang about one in four
+ times when running cpu_offlining tests.
+ 
+ This patch to fix this regression was just submitted to mainline, so it is 
also
+ needed in Bionic.
+ 
+ == Fix ==
+ commit d47924417319e3b6a728c0b690f183e75bc2a702
+ Author: Thomas Gleixner 
+ Date:   Tue Jan 16 19:59:59 2018 +0100
+ 
+ x86/intel_rdt/cqm: Prevent use after free
+ 
+ == Regression Potential ==
+ Low.  This patch fixes a current regression that is a use after free.
+ 
+ 
+ ### Original Bug Description ###
+ In doing Ubuntu 17.10 regression testing, we've encountered one computer 
(boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when 
running our cpu_offlining test. This test attempts to take all the CPU cores 
offline except one, then brings them back online again. This test ran 
successfully on boldore with previous releases, but with 17.10, the system 
sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found 
no problems; but when I upgraded the 16.04.3 installation to 
linux-image-4.13.0-16-generic, the problem appeared again, so I'm confident 
this is a problem with the kernel. I'm attaching two files, 
dmesg-output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output 
that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 
kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg 
-w" in a second SSH login; the files are cut-and-pasted from that.)
  
  I initiated this bug report from an Ubuntu 16.04.3 installation running
  a 4.10 kernel; but as I said, this applies to the 4.13 kernel.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  System hang with Linux kernel due to mainline commit 24247aeeabe

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

Bug description:
  == SRU Justification ==
  The following mainline commit introduced a regression in v4.14-rc1:
  24247aeeabe9 ("x86/intel_rdt/cqm: Improve limbo list processing")

  This commit made it's way into Artful via Launchpad bug 1591609 as Artful 
commit
  ac2fc5adab0f4b.

  This bug was causing regression tests to hang about one in four
  times when running cpu_offlining tests.

  This patch to fix this regression was just submitted to mainline, so it is 
also
  needed in Bionic.

  == Fix ==
  commit d47924417319e3b6a728c0b690f183e75bc2a702
  Author: Thomas Gleixner 
  Date:   Tue Jan 16 19:59:59 2018 +0100

  x86/intel_rdt/cqm: Prevent use after free

  == Regression Potential ==
  Low.  This patch fixes a current regression that is a use after free.


  ### Original Bug Description ###
  In doing Ubuntu 17.10 regression testing, we've

[Kernel-packages] [Bug 1741655] Re: Regression: KVM no longer supports Intel CPUs without Virtual NMI

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

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

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

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

Title:
  Regression: KVM no longer supports Intel CPUs without Virtual NMI

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

Bug description:
  Since upgrading from zesty to artful, I'm not longer able to use KVM on my 
server:
  # modprobe kvm-intel
  modprobe: ERROR: could not insert 'kvm_intel': Input/output error

  Searching tells me this is caused by requiring Virtual NMI support[1]

  Running the script provided on the mailing list[1] to check virtualization 
features confirms my CPU (Xeon E5345) doesn't support Virtual NMIs:
  # python features.py | grep NMI
NMI exiting  yes
Virtual NMIs no
NMI-window exiting   no

  Virtual NMI support was required in v4.12[1] and later reverted in
  v4.14.3[2] as some models (including Xeons) don't support it, even if
  others with the same core do.

  
  [1] https://bugzilla.redhat.com/show_bug.cgi?id=1490803
  [2] https://lkml.org/lkml/2017/8/7/231
  [3] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/kvm/vmx.c?h=linux-4.13.y=2c82878b0cb38fd516fd612c67852a6bbf282003
  [4] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/kvm/vmx.c?h=linux-4.14.y=a77360e989f3dc06e4f177a0837d533d13a20d91

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

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

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

2018-01-19 Thread Emiko Bellocq

> #539
> Will this bug ever be solved using windows (or without a kernel update) or my
> bios will stay broken forever?

I do not think so.

According to this instruction, there is a way to install Ubuntu from internal
disk partition without using CD nor USB.
https://help.ubuntu.com/community/Grub2/ISOBoot

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

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

---

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

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

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

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

---

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

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

---

Affected Machines:

---

Original Description:

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

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

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

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

Thank you!!

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

[Kernel-packages] [Bug 1744173] Re: artful: rfi-flush: Switch to new linear fallback flush

2018-01-19 Thread Dimitri John Ledkov

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

Title:
  artful: rfi-flush: Switch to new linear fallback flush

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

Bug description:
  Change flush from congruence-first with dependencies to linear with
  no dependencies, which increases flush performance by 8x on P8, and
  3x on P9 (as measured with null syscall loop, which will have the
  flush area in the L2).

  The flush also becomes simpler and more adaptable to different cache
  geometries.

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

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

[Kernel-packages] [Bug 1744309] Re: linux-lts-trusty: 3.13.0-141.190~precise1 -proposed tracker

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

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

Title:
  linux-lts-trusty: 3.13.0-141.190~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

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

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

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

[Kernel-packages] [Bug 1744173] [NEW] artful: rfi-flush: Switch to new linear fallback flush

2018-01-19 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Change flush from congruence-first with dependencies to linear with
no dependencies, which increases flush performance by 8x on P8, and
3x on P9 (as measured with null syscall loop, which will have the
flush area in the L2).

The flush also becomes simpler and more adaptable to different cache
geometries.

** Affects: ubuntu-power-systems
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bot-comment bugnameltc-163715 severity-medium 
targetmilestone-inin1710 triage-g
-- 
artful: rfi-flush: Switch to new linear fallback flush
https://bugs.launchpad.net/bugs/1744173
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

2018-01-19 Thread André Brait Carneiro Fabotti

@Seth You might have missed it (there's lots of text here, so it's more
than ok :-) ) but I already had said in one comment here that it affects
Artful as well (and Bionic, of course, but that is still in
development).

Pretty much it affects any distro using a kernel newer than or equal to
4.12. I've posted a report from Debian here and I've found mentions of
this bug in Arch as well.

The original question on askubuntu that led me to report the bug
(although I had experienced it in Xenial) was from a user running
Artful.

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

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

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

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

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

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

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

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

  Which led me to this bug in upstream:

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

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

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

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

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

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

  -

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

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

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

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

  [How to fix it]

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

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

  -

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

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

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

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

[Kernel-packages] [Bug 1744308] Re: linux: 3.13.0-141.190 -proposed tracker

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1744309
  derivatives:
+ kernel-stable-phase-changed:Friday, 19. January 2018 13:32 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1744309
  derivatives:
  kernel-stable-phase-changed:Friday, 19. January 2018 13:32 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 3.13.0-141.190 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1744309
  derivatives:
  kernel-stable-phase-changed:Friday, 19. January 2018 13:32 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1744309] Re: linux-lts-trusty: 3.13.0-141.190~precise1 -proposed tracker

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

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

** Description changed:

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

** Description changed:

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

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

Title:
  linux-lts-trusty: 3.13.0-141.190~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

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

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

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

[Kernel-packages] [Bug 1743872] Re: "0bda:a811" - Not work 802.11ac WLAN Adapter

** Summary changed:

- Not work 802.11ac WLAN Adapter
+ "0bda:a811" - Not work 802.11ac WLAN Adapter

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

Title:
  "0bda:a811" - Not work 802.11ac WLAN Adapter

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Not work:
  
https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-30-generic 4.13.0-30.33
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1752 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 17:08:45 2018
  InstallationDate: Installed on 2017-10-13 (96 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-30-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-30-generic N/A
   linux-backports-modules-4.13.0-30-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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

Added artful nomination based on duplicate bug 1744187.

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

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

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

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

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

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

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

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

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

  Which led me to this bug in upstream:

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

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

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

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

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

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

  -

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

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

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

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

  [How to fix it]

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

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

  -

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

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

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

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

[Kernel-packages] [Bug 1744187] Re: [168c:003e] WiFi disconnect after using for a while (QCA6174A XR)

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

Let's use the same bug that was used for xenial, bug 1743279. Marking
this as a duplicate.

** This bug has been marked a duplicate of bug 1743279
   QCA6174 stops working on newer kernels after second group rekeying

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

Title:
  [168c:003e] WiFi disconnect after using for a while (QCA6174A XR)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  SRU Justification
  [Impact]
  Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e]
  WiFi disconnects after using for a while. (Less than 30 minutes)
  Use Wireless hotkey can recovery WiFi network.
  The WiFi icon still shows connected when issue happens.

  [Test Case]
  96a7402 ath10k: QCA6174 hw3.0: update firmware-6.bin to 
WLAN.RM.4.4.1-00051-QCARMSWP-1
  Above commit fixes frequently disconnecting regression issue.

  [Regression Potential]
  Low, this commit is already in xenial, but not be included in artful, so 
should be safe to have it in artful, too.

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2018-01-19 Thread Dan Streetman

I've updated the patch and submitted upstream:
https://marc.info/?l=linux-netdev=151631015108584=2

The PPA also contains the latest ubuntu kernels patched for the issue, if 
anyone has time to test:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1711407

> How do we know when we hit the bug with your patched kernel?

I didn't include any output in the latest kernels to indicate this issue
had been detected and fixed.  If anyone is able to reproduce it with one
of the test kernels, I can provide a debug kernel to gather more details
of why it's still failing, though.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 995743] Re: 197b:2394 [Dell XPS 17 L502X] Internal SD card reader is not working

2018-01-19 Thread asgard2

The workaround is not working here too.

The report from 2014 is here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1367366

@penalvch
why no longer affects linux?

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

Title:
  197b:2394 [Dell XPS 17 L502X] Internal SD card reader is not working

Status in linux package in Ubuntu:
  Invalid

Bug description:
  If I start up the computer with no SD card in the reader, it will not
  recognise SD cards inserted.

  WORKAROUND: If you start up the computer with an SD card inserted, all
  is good.

  WORKAROUND: The following rescan will find the SD card.

  sudo su -l
  echo 1 > /sys/bus/pci/rescan

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-24-generic 3.2.0-24.37
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC665 Analog [ALC665 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lee   20624 F pulseaudio
  CRDA:
   country AU:
    (2402 - 2482 @ 40), (N/A, 20)
    (5170 - 5250 @ 40), (3, 23)
    (5250 - 5330 @ 40), (3, 23), DFS
    (5735 - 5835 @ 40), (3, 30)
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf3c0 irq 55'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:10ec0665,10280571,0013 
HDA:80862805,80860101,0010'
     Controls  : 31
     Simple ctrls  : 13
  Date: Mon May  7 13:52:09 2012
  HibernationDevice: RESUME=UUID=131e7674-2f9b-4de3-b917-8d79a5a64e28
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Dell Inc. Dell System XPS L702X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=157174fa-f17e-471d-9008-353e4499b5f8 ro
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic  N/A
   linux-firmware1.79
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: Upgraded to precise on 2012-04-29 (7 days ago)
  dmi.bios.date: 01/10/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 0XN71K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: FAB1
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd01/10/2012:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0XN71K:rvrFAB1:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L702X
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1367366] Re: [DELL XPS 15 L502X] internal sd card reader problem

2018-01-19 Thread asgard2

still no SD-Card with 16.04 LTS + linux-image-4.13.0-26

same error:
mmc0: error -110 whilst initialising SD card

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

Title:
  [DELL XPS 15 L502X] internal sd card reader problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  my internal SD-card reader is not working at the DELL XPS 15 L502X.

  messages at the system log:
  kernel: [  332.414191] mmc0: error -110 whilst initialising SD card
  kernel: [  332.763919] mmc0: error -110 whilst initialising SD card

  
  After several tries, the card is recognized.

  The bug seems solved for some time:
  https://bugs.launchpad.net/linux/+bug/995743

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-36-generic 3.13.0-36.63
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chuck-game   2122 F lxpanel
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
  CurrentDesktop: LXDE
  Date: Tue Sep  9 18:24:58 2014
  HibernationDevice: RESUME=UUID=031c1bfb-a99f-45ff-b7fc-eeaa254f9a2a
  InstallationDate: Installed on 2013-08-10 (394 days ago)
  InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=50751449-1f90-4151-bc30-329f3b22e2cf ro quiet 
rcutree.rcu_idle_gp_delay=1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-36-generic N/A
   linux-backports-modules-3.13.0-36-generic  N/A
   linux-firmware 1.127.5
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (144 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

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

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

apport-collect 1744122

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

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

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

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

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

Title:
  Ubuntu 16.04.3 LTS with kerne 4.4.0-109-generic, segfaults vsyscalls

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The following ubuntu xenial version segfaults any program trying to
  read its own vsyscall memory segment. The affected ubuntu version:

  Vagrant box: ubuntu/xenial64 (v20180112.0.0)
  Kernel: 4.4.0-109-generic

  Executing the following program segfaults:

  // gcc -g -O0 
  int main() {
// You use gdb to pause the program and 
// check through /proc//maps that this 
// memory addrs is mapped to [vsyscall]
return *(int*)(0xff60);
  }

  The following two versions work fine:

  Vagrant box: ubuntu/bionic64 (v20180115.1.0)
  Kernel: 4.13.0-25-generic

  Vagrant box: ubuntu/xenial64 (v20171028.0.0)
  Kernel: 4.4.0-97-generic

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

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

[Kernel-packages] [Bug 1743872] Re: Not work 802.11ac WLAN Adapter

2018-01-19 Thread TJ

There's an outside tree that I've had a lot of success with from:

https://github.com/abperiasamy/rtl8812AU_8821AU_linux.git

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

Title:
  Not work 802.11ac WLAN Adapter

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Not work:
  
https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-30-generic 4.13.0-30.33
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1752 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 17:08:45 2018
  InstallationDate: Installed on 2017-10-13 (96 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-30-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-30-generic N/A
   linux-backports-modules-4.13.0-30-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

** Description changed:

+ [Impact]
+ 
+  * open-iscsi users might face hangs during OS shutdown.
+  * hangs can be caused by manual iscsi configuration/setup.
+  * hangs can also be caused by bad systemd unit ordering.
+  * if transport layer interface vanishes before lun is
+disconnected, then the hang will happen.
+  * check comment #89 for the fix decision.
+  
+ [Test Case]
+ 
+  * a simple way of reproducing the kernel hang is to disable
+the open-iscsi logouts. this simulates a situation when
+a service has shutdown the network interface, used by
+the transport layer, before proper iscsi logout was done.
+ 
+$ log into all iscsi luns
+   
+$ systemctl edit --full open-iscsi.service
+...
+#ExecStop=/lib/open-iscsi/logout-all.sh
+...
+   
+$ sudo reboot # this will make server to hang forever
+  # on shutdown
+ 
+ [Regression Potential]
+ 
+  * the regression is low because the change acts on the iscsi
+transport layer code ONLY when the server is in shutdown 
+state.
+ 
+  * any error in logic would only appear during shutdown and
+would not cause any harm to data.
+ 
+ [Other Info]
+  
+  * ORIGINAL BUG DESCRIPTION
+ 
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).
  
  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being managed
  by device mapper.
  
  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.
  
  I see a message that says:
  
    "Reached target Shutdown"
  
  followed by
  
    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"
  
  and then I see 8 lines that say:
  
    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.
  
  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.
  
  Note I also have similar setups that are not doing iscsi and they don't
  have this problem.
  
  Here is a screenshot of what I see on the shell when I try to reboot:
  
  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)
  
  This is being tracked in NetApp bug tracker CQ number 860251.
  
  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:
  
  iscsiadm -m node -U all
  
  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  Opinion
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  Opinion
Status in linux source package in Zesty:
  In Progress
Status in open-iscsi source package in Zesty:
  Opinion
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  Opinion

Bug description:
  [Impact]

   * open-iscsi users might face hangs during OS shutdown.
   * hangs can be caused by manual iscsi configuration/setup.
   * hangs can also be caused by bad systemd unit ordering.
   * if transport layer interface vanishes before lun is
 disconnected, then the hang will happen.
   * check comment #89 for the fix decision.
   
  [Test Case]

   * a simple way of reproducing the kernel hang is to disable
 the open-iscsi logouts. this simulates a situation when
 a service has shutdown the network interface, used by
 the transport layer, before proper iscsi logout was done.

 $ log into all iscsi luns

[Kernel-packages] [Bug 1744199] Re: ubuntu_32_on_64 test crash Trusty 3.13.0-140 amd64 system

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

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

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

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

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

Title:
  ubuntu_32_on_64 test crash Trusty 3.13.0-140 amd64 system

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  THIS IS A POTENTIAL REGRESSION

  Steps:
  1. Deploy a Trusty amd64 node (node pepe in this case)
  2. sudo apt-get install git python-minimal -y
  3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 
-b master-next
  4. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
  5. rm -fr autotest/client/tests
  6. ln -sf ~/autotest-client-tests autotest/client/tests
  7. Monitor the syslog with tail -f /var/log/syslog
  8. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_32_on_64/control.ubuntu

  Result:
  * The system will hang without any output in syslog. I can't see any error 
message from ipmi output as well.

  This test can pass with 3.13.0-139

  Output:
  ubuntu@pepe:~$ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_32_on_64/control.ubuntu
  03:53:08 INFO | Writing results to 
/home/ubuntu/autotest/client/results/default
  03:53:08 DEBUG| Initializing the state engine
  03:53:08 DEBUG| Persistent state client.steps now set to []
  03:53:08 DEBUG| Persistent option harness now set to None
  03:53:08 DEBUG| Persistent option harness_args now set to None
  03:53:08 DEBUG| Selected harness: standalone
  03:53:08 INFO | START timestamp=1516333988localtime=Jan 
19 03:53:08   
  03:53:08 DEBUG| Persistent state client._record_indent now set to 1
  03:53:08 INFO |   START   ubuntu_32_on_64 ubuntu_32_on_64 
timestamp=1516333988localtime=Jan 19 03:53:08   
  03:53:08 DEBUG| Persistent state client._record_indent now set to 2
  03:53:08 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_32_on_64', 'ubuntu_32_on_64')
  03:53:08 WARNI| Could not find GDB installed. Crash handling will operate 
with limited functionality
  03:53:08 DEBUG| Running 'apt-get install --yes --force-yes build-essential 
gcc-multilib'
  03:53:08 DEBUG| [stdout] Reading package lists...
  03:53:08 DEBUG| [stdout] Building dependency tree...
  03:53:08 DEBUG| [stdout] Reading state information...
  03:53:09 DEBUG| [stdout] build-essential is already the newest version.
  03:53:09 DEBUG| [stdout] gcc-multilib is already the newest version.
  03:53:09 DEBUG| [stdout] 0 upgraded, 0 newly installed, 0 to remove and 0 not 
upgraded.
  03:53:09 DEBUG| Running 'which gcc'
  03:53:09 DEBUG| [stdout] /usr/bin/gcc
  03:53:09 DEBUG| Running 
'/home/ubuntu/autotest/client/tmp/ubuntu_32_on_64/src/forkexec  date'

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-140-generic 3.13.0-140.189
  ProcVersionSignature: User Name 3.13.0-140.189-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-140-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 19 03:43 seq
   crw-rw 1 root audio 116, 33 Jan 19 03:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Jan 19 03:44:08 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R310
  PciMultimedia:

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

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-140-generic 
root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-140-generic N/A
   linux-backports-modules-3.13.0-140-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2011

[Kernel-packages] [Bug 1744300] Re: bt_iter() crash due to NULL pointer

2018-01-19 Thread Guilherme G. Piccoli

** No longer affects: linux (Ubuntu Bionic)

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

** Changed in: linux (Ubuntu Artful)
   Status: New => In Progress

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

Title:
  bt_iter() crash due to NULL pointer

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

Bug description:
  SRU Justification:

  
  [Impact]
  The following crash was observed in Ubuntu 16.04 running linux-gcp kernel 
version 4.13 (specifically 4.13.0-1006.9):

  [ 10.972644] BUG: unable to handle kernel NULL pointer dereference at 
0030 
  [ 10.980708] IP: bt_iter+0x31/0x50 
  [ 10.984310] PGD 0 
  [ 10.984310] P4D 0 
  [ 10.986439] 
  [ 10.990190] Oops:  [#1] SMP PTI 
  [ 11.016282] Workqueue: kblockd blk_mq_timeout_work 
  [ 11.021196] task: 8e7c2e70 task.stack: b8d4c67a8000 
  [ 11.027234] RIP: 0010:bt_iter+0x31/0x50 
  [ 11.031187] RSP: 0018:b8d4c67abda0 EFLAGS: 00010206 
  [ 11.037730] RAX: b8d4c67abdd0 RBX: 0180 RCX: 
 
  [ 11.045172] RDX: 8e7c34c8d280 RSI:  RDI: 
8e7c32dd8000 
  [ 11.053321] RBP: b8d4c67abe20 R08:  R09: 
2100 
  [ 11.060582] R10: 0130 R11: fffee5bf R12: 
8e7c3572c790 
  [ 11.068094] R13: 8e7c3572c780 R14: 0008 R15: 
8e7c35e7c180 
  [ 11.075522] FS: () GS:8e7c3a4c() 
knlGS: 
  [ 11.083721] CS: 0010 DS:  ES:  CR0: 80050033 
  [ 11.089593] CR2: 0030 CR3: 9e20a003 CR4: 
001606e0 
  [ 11.096871] Call Trace: 
  [ 11.099468] ? blk_mq_queue_tag_busy_iter+0xe2/0x1f0 
  [ 11.104558] ? blk_mq_rq_timed_out+0x70/0x70 
  [ 11.109130] ? blk_mq_rq_timed_out+0x70/0x70 
  [ 11.114933] blk_mq_timeout_work+0xbb/0x170 
  [ 11.119408] process_one_work+0x156/0x410 
  [ 11.123641] worker_thread+0x4b/0x460 
  [ 11.127827] kthread+0x109/0x140 
  [ 11.131186] ? process_one_work+0x410/0x410 
  [ 11.135499] ? kthread_create_on_node+0x70/0x70 
  [ 11.140408] ret_from_fork+0x1f/0x30 
  [ 11.144110] Code: 89 d0 48 8b 3a 0f b6 48 18 48 8b 97 30 01 00 00 84 c9 75 
03 03 72 04 48 8b 92 80 00 00 00 89 f6 48 8b 34 f2 48 8b 97 c0 00 00 00 <48> 39 
56 30 74 06 b8 01 00 00 00 c3 55 48 8b 50 10 48 89 e5 ff 
  [ 11.167573] RIP: bt_iter+0x31/0x50 RSP: b8d4c67abda0 
  [ 11.173028] CR2: 0030 
  [ 11.176515] ---[ end trace 2f8e5b1cf4139fec ]--- 
  [ 11.182589] Kernel panic - not syncing: Fatal exception 

  Basically, we have a NULL pointer dereference while in bt_iter()
  function - this is caused because after the merge of blk-mq scheduler
  capability on Linux kernel , tags->rqs[] array has been dinamically
  assigned and there's a small window of time in which the bit is set
  but tags->rqs[] array wasn't allocated yet. This was reported to
  happen in about 5% of test runs (more details on test section).

  
  [Fix]
  The fix is small and simple, and it's upstream already. Basically, it adds a 
NULL pointer check on bt_iter() and bt_tags_iter() functions.

  The fix is: 7f5562d5ecc4 ("blk-mq-tag: check for NULL rq when iterating 
tags"), by Jens Axboe.
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7f5562d5ecc4)

  
  [Testcase] 
  Since the problem manifests in a small non-deterministic time window, there's 
no easy test to reproduce this. In our case, it was observed while testing a 
large number of CPU's and attached disks (>200 disks, >150 cores), trying to 
exercise all CPUs and disks (the disks with quick dd commands). In this test 
scenario, as already mentioned, issue occured in about 5% of the runs.

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

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

[Kernel-packages] [Bug 1742722] Re: linux: 4.13.0-29.32 -proposed tracker

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

** This bug is no longer a duplicate of bug 1743412
   linux: 4.13.0-30.33 -proposed tracker
** This bug has been marked a duplicate of bug 1744294
   linux:  -proposed tracker

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

Title:
  linux: 4.13.0-29.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1742723,1742725,1742726,1742727,1742728,1742928
  derivatives: 1742730
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1743412] Re: linux: 4.13.0-30.33 -proposed tracker

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

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

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

Title:
  linux: 4.13.0-30.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1743413,1743414,1743415,1743416,1743417,1743418
  derivatives: 1743419
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1744244] Re: linux: 4.4.0-112.135 -proposed tracker

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1743363,1743364
  derivatives: 1743365,1743367,1743368,1743369,1743370,1743371
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Friday, 19. January 2018 12:01 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1743363,1743364
  derivatives: 1743365,1743367,1743368,1743369,1743370,1743371
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Friday, 19. January 2018 12:01 UTC
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.4.0-112.135 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1743363,1743364
  derivatives: 1743365,1743367,1743368,1743369,1743370,1743371
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Friday, 19. January 2018 12:01 UTC

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1742602] Re: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26

2018-01-19 Thread William Horner

Thanks for all this good testing Tim and Joseph.
If I can help to keep things moving while Tim is travelling, let me know, 
although might need a little guidance initially... if there are some good 
instructions you can point me to on how to get the test kernel in and to 
boot... 
Tim: to your observation I see the issue (assuming it is the same one) with a 
VM with no dual monitor.  But I do see the issue fix itself and reappear based 
on the screen resolution.  Perhaps does that observation shed any further light 
on it or fit with your external monitor results?

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

Title:
  Blank screen when starting X after upgrading from 4.10 to 4.13.0-26

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

Bug description:
  I'm following the HWE kernels in Ubuntu 16.04, so my kernel was
  upgraded today from 4.10.0-42 to 4.13.0-26. After rebooting, the
  splash screen and disk encryption passphrase prompt showed correctly,
  but when X started, the screen went blank. Logs showed everything
  running as normal despite the blank screen. Rebooting with the
  "nomodeset" kernel parameter fixed the issue but is not suitable as a
  permanent workaround since it disables my external monitor. Rebooting
  back into 4.10 also fixed the issue.

  I am using a ThinkPad X240 laptop, current HWE X.org packages. I tried
  both intel and fbdev X drivers, both gave a blank screen.

  lsb_release: Ubuntu 16.04.3 LTS

  dpkg-query -W:

  linux-signed-image-generic-hwe-16.04  4.13.0.26.46
  xserver-xorg-hwe-16.041:7.7+16ubuntu3~16.04.1
  xserver-xorg-video-intel-hwe-16.042:2.99.917+git20170309-0ubuntu1~16.04.1
  xserver-xorg-video-fbdev-hwe-16.041:0.4.4-1build6~16.04.1

  In Xorg.0.log with fbdev, I saw:

  [23.646] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument

  repeated 239 times.

  Typical kernel messages attached (from kern.log, reformatted to look
  like dmesg).

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

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

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

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

apport-collect 1744300

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

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

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

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

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

Title:
  bt_iter() crash due to NULL pointer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SRU Justification:

  
  [Impact]
  The following crash was observed in Ubuntu 16.04 running linux-gcp kernel 
version 4.13 (specifically 4.13.0-1006.9):

  [ 10.972644] BUG: unable to handle kernel NULL pointer dereference at 
0030 
  [ 10.980708] IP: bt_iter+0x31/0x50 
  [ 10.984310] PGD 0 
  [ 10.984310] P4D 0 
  [ 10.986439] 
  [ 10.990190] Oops:  [#1] SMP PTI 
  [ 11.016282] Workqueue: kblockd blk_mq_timeout_work 
  [ 11.021196] task: 8e7c2e70 task.stack: b8d4c67a8000 
  [ 11.027234] RIP: 0010:bt_iter+0x31/0x50 
  [ 11.031187] RSP: 0018:b8d4c67abda0 EFLAGS: 00010206 
  [ 11.037730] RAX: b8d4c67abdd0 RBX: 0180 RCX: 
 
  [ 11.045172] RDX: 8e7c34c8d280 RSI:  RDI: 
8e7c32dd8000 
  [ 11.053321] RBP: b8d4c67abe20 R08:  R09: 
2100 
  [ 11.060582] R10: 0130 R11: fffee5bf R12: 
8e7c3572c790 
  [ 11.068094] R13: 8e7c3572c780 R14: 0008 R15: 
8e7c35e7c180 
  [ 11.075522] FS: () GS:8e7c3a4c() 
knlGS: 
  [ 11.083721] CS: 0010 DS:  ES:  CR0: 80050033 
  [ 11.089593] CR2: 0030 CR3: 9e20a003 CR4: 
001606e0 
  [ 11.096871] Call Trace: 
  [ 11.099468] ? blk_mq_queue_tag_busy_iter+0xe2/0x1f0 
  [ 11.104558] ? blk_mq_rq_timed_out+0x70/0x70 
  [ 11.109130] ? blk_mq_rq_timed_out+0x70/0x70 
  [ 11.114933] blk_mq_timeout_work+0xbb/0x170 
  [ 11.119408] process_one_work+0x156/0x410 
  [ 11.123641] worker_thread+0x4b/0x460 
  [ 11.127827] kthread+0x109/0x140 
  [ 11.131186] ? process_one_work+0x410/0x410 
  [ 11.135499] ? kthread_create_on_node+0x70/0x70 
  [ 11.140408] ret_from_fork+0x1f/0x30 
  [ 11.144110] Code: 89 d0 48 8b 3a 0f b6 48 18 48 8b 97 30 01 00 00 84 c9 75 
03 03 72 04 48 8b 92 80 00 00 00 89 f6 48 8b 34 f2 48 8b 97 c0 00 00 00 <48> 39 
56 30 74 06 b8 01 00 00 00 c3 55 48 8b 50 10 48 89 e5 ff 
  [ 11.167573] RIP: bt_iter+0x31/0x50 RSP: b8d4c67abda0 
  [ 11.173028] CR2: 0030 
  [ 11.176515] ---[ end trace 2f8e5b1cf4139fec ]--- 
  [ 11.182589] Kernel panic - not syncing: Fatal exception 

  Basically, we have a NULL pointer dereference while in bt_iter()
  function - this is caused because after the merge of blk-mq scheduler
  capability on Linux kernel , tags->rqs[] array has been dinamically
  assigned and there's a small window of time in which the bit is set
  but tags->rqs[] array wasn't allocated yet. This was reported to
  happen in about 5% of test runs (more details on test section).

  
  [Fix]
  The fix is small and simple, and it's upstream already. Basically, it adds a 
NULL pointer check on bt_iter() and bt_tags_iter() functions.

  The fix is: 7f5562d5ecc4 ("blk-mq-tag: check for NULL rq when iterating 
tags"), by Jens Axboe.
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7f5562d5ecc4)

  
  [Testcase] 
  Since the problem manifests in a small non-deterministic time window, there's 
no easy test to reproduce this. In our case, it was observed while testing a 
large number of CPU's and attached disks (>200 disks, >150 cores), trying to 
exercise all CPUs and disks (the disks with quick dd commands). In this test 
scenario, as already mentioned, issue occured in about 5% of the runs.

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

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

[Kernel-packages] [Bug 1744294] Re: linux: -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: 1744295,1744297,1744298,1744299,1744301,1744302
+ derivatives: 1744303

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1744295,1744297,1744298,1744299,1744301,1744302
- derivatives: 1744303
+ derivatives: 1743419

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- backports: 1744295,1744297,1744298,1744299,1744301,1744302
+ backports: 1744295,1744297,1744298,1743418,1744301,1744302
  derivatives: 1743419

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- backports: 1744295,1744297,1744298,1743418,1744301,1744302
+ backports: 1744295,1744297,1744298,1743418,1742723,1744302
  derivatives: 1743419

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- backports: 1744295,1744297,1744298,1743418,1742723,1744302
+ backports: 1744295,1742725,1744298,1743418,1742723,1744302
  derivatives: 1743419

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- backports: 1744295,1742725,1744298,1743418,1742723,1744302
+ backports: 1744295,1742725,1744298,1743418,1742723,1742726
  derivatives: 1743419

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1744295,1742725,1744298,1743418,1742723,1742726
  derivatives: 1743419

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

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

[Kernel-packages] [Bug 1744300] Re: bt_iter() crash due to NULL pointer

2018-01-19 Thread Guilherme G. Piccoli

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

** No longer affects: linux-gcp (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/1744300

Title:
  bt_iter() crash due to NULL pointer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SRU Justification:

  
  [Impact]
  The following crash was observed in Ubuntu 16.04 running linux-gcp kernel 
version 4.13 (specifically 4.13.0-1006.9):

  [ 10.972644] BUG: unable to handle kernel NULL pointer dereference at 
0030 
  [ 10.980708] IP: bt_iter+0x31/0x50 
  [ 10.984310] PGD 0 
  [ 10.984310] P4D 0 
  [ 10.986439] 
  [ 10.990190] Oops:  [#1] SMP PTI 
  [ 11.016282] Workqueue: kblockd blk_mq_timeout_work 
  [ 11.021196] task: 8e7c2e70 task.stack: b8d4c67a8000 
  [ 11.027234] RIP: 0010:bt_iter+0x31/0x50 
  [ 11.031187] RSP: 0018:b8d4c67abda0 EFLAGS: 00010206 
  [ 11.037730] RAX: b8d4c67abdd0 RBX: 0180 RCX: 
 
  [ 11.045172] RDX: 8e7c34c8d280 RSI:  RDI: 
8e7c32dd8000 
  [ 11.053321] RBP: b8d4c67abe20 R08:  R09: 
2100 
  [ 11.060582] R10: 0130 R11: fffee5bf R12: 
8e7c3572c790 
  [ 11.068094] R13: 8e7c3572c780 R14: 0008 R15: 
8e7c35e7c180 
  [ 11.075522] FS: () GS:8e7c3a4c() 
knlGS: 
  [ 11.083721] CS: 0010 DS:  ES:  CR0: 80050033 
  [ 11.089593] CR2: 0030 CR3: 9e20a003 CR4: 
001606e0 
  [ 11.096871] Call Trace: 
  [ 11.099468] ? blk_mq_queue_tag_busy_iter+0xe2/0x1f0 
  [ 11.104558] ? blk_mq_rq_timed_out+0x70/0x70 
  [ 11.109130] ? blk_mq_rq_timed_out+0x70/0x70 
  [ 11.114933] blk_mq_timeout_work+0xbb/0x170 
  [ 11.119408] process_one_work+0x156/0x410 
  [ 11.123641] worker_thread+0x4b/0x460 
  [ 11.127827] kthread+0x109/0x140 
  [ 11.131186] ? process_one_work+0x410/0x410 
  [ 11.135499] ? kthread_create_on_node+0x70/0x70 
  [ 11.140408] ret_from_fork+0x1f/0x30 
  [ 11.144110] Code: 89 d0 48 8b 3a 0f b6 48 18 48 8b 97 30 01 00 00 84 c9 75 
03 03 72 04 48 8b 92 80 00 00 00 89 f6 48 8b 34 f2 48 8b 97 c0 00 00 00 <48> 39 
56 30 74 06 b8 01 00 00 00 c3 55 48 8b 50 10 48 89 e5 ff 
  [ 11.167573] RIP: bt_iter+0x31/0x50 RSP: b8d4c67abda0 
  [ 11.173028] CR2: 0030 
  [ 11.176515] ---[ end trace 2f8e5b1cf4139fec ]--- 
  [ 11.182589] Kernel panic - not syncing: Fatal exception 

  Basically, we have a NULL pointer dereference while in bt_iter()
  function - this is caused because after the merge of blk-mq scheduler
  capability on Linux kernel , tags->rqs[] array has been dinamically
  assigned and there's a small window of time in which the bit is set
  but tags->rqs[] array wasn't allocated yet. This was reported to
  happen in about 5% of test runs (more details on test section).

  
  [Fix]
  The fix is small and simple, and it's upstream already. Basically, it adds a 
NULL pointer check on bt_iter() and bt_tags_iter() functions.

  The fix is: 7f5562d5ecc4 ("blk-mq-tag: check for NULL rq when iterating 
tags"), by Jens Axboe.
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7f5562d5ecc4)

  
  [Testcase] 
  Since the problem manifests in a small non-deterministic time window, there's 
no easy test to reproduce this. In our case, it was observed while testing a 
large number of CPU's and attached disks (>200 disks, >150 cores), trying to 
exercise all CPUs and disks (the disks with quick dd commands). In this test 
scenario, as already mentioned, issue occured in about 5% of the runs.

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

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

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

2018-01-19 Thread Jon Evans

** Attachment added: "Slo-mo video of failing boot (3s)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675/+attachment/5039509/+files/Failed%204.13.0-26-generic%20boot.mp4

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

[Kernel-packages] [Bug 1744284] Re: linux: -proposed tracker

** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Invalid

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Invalid

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

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

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

[Kernel-packages] [Bug 1743872] Re: Not work 802.11ac WLAN Adapter

Hello Kai-Heng.

Can you create the .deb package with the correction? for me to download
and install it.

So tell you if it works.

Regards,
-
Cristian

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

Title:
  Not work 802.11ac WLAN Adapter

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Not work:
  
https://www.ebay.com/itm/600Mbps-Dual-Band-2-4G-5G-Hz-Wireless-Lan-USB-PC-WiFi-Adapter-802-11AC/352152445782

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-30-generic 4.13.0-30.33
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1752 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 17:08:45 2018
  InstallationDate: Installed on 2017-10-13 (96 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-30-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-30-generic N/A
   linux-backports-modules-4.13.0-30-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

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

2018-01-19 Thread Jon Evans

It still fails for me with acpi=off.

A bit of background, this PC has been running fine for the past 12
months or so, with regular updates including kernel updates. It's only
started failing since 4.13.0-26-generic.

** Attachment added: "grub command line"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675/+attachment/5039508/+files/IMG_0804.JPG

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

[Kernel-packages] [Bug 1744296] [NEW] After ifdown on underlay interface ifup fails with 'already configured'

2018-01-19 Thread Witold Krecicki

Public bug reported:

With following setup:
<...>
2: ens192:  mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether 00:50:56:86:31:a8 brd ff:ff:ff:ff:ff:ff
inet 10.245.40.80/18 brd 10.245.63.255 scope global ens192
   valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fe86:31a8/64 scope link 
   valid_lft forever preferred_lft forever
<...>
4: fan-254:  mtu 1450 qdisc noqueue state UP 
group default qlen 1000
link/ether 8a:f3:53:e5:11:37 brd ff:ff:ff:ff:ff:ff
inet 254.161.64.1/8 scope global fan-254
   valid_lft forever preferred_lft forever
inet6 fe80::88f3:53ff:fee5:1137/64 scope link 
   valid_lft forever preferred_lft forever
5: ftun0:  mtu 1450 qdisc noqueue master 
fan-254 state UNKNOWN group default qlen 1000
link/ether 8a:f3:53:e5:11:37 brd ff:ff:ff:ff:ff:ff
inet6 fe80::88f3:53ff:fee5:1137/64 scope link 
   valid_lft forever preferred_lft forever


Doing ifdown ens192; ifup ens192 results in an error:
# ifdown ens192; echo $?; ifup ens192; echo $?
Killed old client process
<... isc-dhcp stuff ...>
0
<... isc-dhcp stuff ...>
/usr/sbin/fanctl: fan-254: already configured
/usr/sbin/fanctl: /etc/network/fan:40 10.245.0.0/18 254.0.0.0/8  -- failed err=1
run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1
Failed to bring up ens192.
1

** Affects: ubuntu-fan (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  After ifdown on underlay interface ifup fails with 'already
  configured'

Status in ubuntu-fan package in Ubuntu:
  New

Bug description:
  With following setup:
  <...>
  2: ens192:  mtu 1500 qdisc mq state UP group 
default qlen 1000
  link/ether 00:50:56:86:31:a8 brd ff:ff:ff:ff:ff:ff
  inet 10.245.40.80/18 brd 10.245.63.255 scope global ens192
 valid_lft forever preferred_lft forever
  inet6 fe80::250:56ff:fe86:31a8/64 scope link 
 valid_lft forever preferred_lft forever
  <...>
  4: fan-254:  mtu 1450 qdisc noqueue state UP 
group default qlen 1000
  link/ether 8a:f3:53:e5:11:37 brd ff:ff:ff:ff:ff:ff
  inet 254.161.64.1/8 scope global fan-254
 valid_lft forever preferred_lft forever
  inet6 fe80::88f3:53ff:fee5:1137/64 scope link 
 valid_lft forever preferred_lft forever
  5: ftun0:  mtu 1450 qdisc noqueue master 
fan-254 state UNKNOWN group default qlen 1000
  link/ether 8a:f3:53:e5:11:37 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::88f3:53ff:fee5:1137/64 scope link 
 valid_lft forever preferred_lft forever

  
  Doing ifdown ens192; ifup ens192 results in an error:
  # ifdown ens192; echo $?; ifup ens192; echo $?
  Killed old client process
  <... isc-dhcp stuff ...>
  0
  <... isc-dhcp stuff ...>
  /usr/sbin/fanctl: fan-254: already configured
  /usr/sbin/fanctl: /etc/network/fan:40 10.245.0.0/18 254.0.0.0/8  -- failed 
err=1
  run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1
  Failed to bring up ens192.
  1

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

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

[Kernel-packages] [Bug 1744294] [NEW] linux: -proposed tracker

Public bug reported:

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

For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

backports: 1744295,1744297,1744298,1744299,1744301,1744302
derivatives: 1743419

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Artful)
 Importance: Medium
 Status: Confirmed


** Tags: artful kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2017.11.20-9 kernel-sru-master-kernel

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

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: artful

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in:

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

** Tags added: sts

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  In Progress
Status in open-iscsi package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in open-iscsi source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in open-iscsi source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in open-iscsi source package in Artful:
  In Progress

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Kernel-packages] [Bug 1744283] [NEW] Bluetooh daemon don't work

2018-01-19 Thread Jiri Vrany

Public bug reported:

Bluetooth service complains about Not Enough Resources. My BT headset is
not connecting and if so, it is disconnected after 30s-2min. BT daemon
freezes in restart attempt.

bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Pá 2018-01-19 12:06:42 CET; 5s ago
 Docs: man:bluetoothd(8)
 Main PID: 4842 (bluetoothd)
   Status: "Running"
Tasks: 1
   Memory: 1.1M
  CPU: 14ms
   CGroup: /system.slice/bluetooth.service
   └─4842 /usr/lib/bluetooth/bluetoothd

led 19 12:06:42 sela bluetoothd[4842]: Not enough free handles to register 
service
led 19 12:06:42 sela bluetoothd[4842]: Not enough free handles to register 
service
led 19 12:06:42 sela bluetoothd[4842]: Current Time Service could not be 
registered
led 19 12:06:42 sela bluetoothd[4842]: gatt-time-server: Input/output error (5)
led 19 12:06:42 sela bluetoothd[4842]: Not enough free handles to register 
service
led 19 12:06:42 sela bluetoothd[4842]: Not enough free handles to register 
service
led 19 12:06:42 sela bluetoothd[4842]: Sap driver initialization failed.
led 19 12:06:42 sela bluetoothd[4842]: sap-server: Operation not permitted (1)
led 19 12:06:42 sela bluetoothd[4842]: Endpoint registered: sender=:1.65 
path=/MediaEndpoint/A2DPSource
led 19 12:06:42 sela bluetoothd[4842]: Endpoint registered: sender=:1.65 
path=/MediaEndpoint/A2DPSink

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bluetooth 5.37-0ubuntu5.1
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jan 19 12:08:06 2018
InstallationDate: Installed on 2017-07-26 (176 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Precision 5520
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-26-generic.efi.signed 
root=UUID=31407435-ebcb-4377-84d8-b3c4de7f74c5 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/15/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: F8:59:71:A8:6D:84  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:111825 acl:0 sco:0 events:3513 errors:0
TX bytes:609537 acl:0 sco:0 commands:2565 errors:0

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


** Tags: amd64 apport-bug xenial

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

Title:
  Bluetooh daemon don't work

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth service complains about Not Enough Resources. My BT headset
  is not connecting and if so, it is disconnected after 30s-2min. BT
  daemon freezes in restart attempt.

  bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Pá 2018-01-19 12:06:42 CET; 5s ago
   Docs: man:bluetoothd(8)
   Main PID: 4842 (bluetoothd)
 Status: "Running"
  Tasks: 1
 Memory: 1.1M
CPU: 14ms
 CGroup: /system.slice/bluetooth.service
 └─4842 /usr/lib/bluetooth/bluetoothd

  led 19 12:06:42 sela bluetoothd[4842]: Not enough free handles to register 
service
  led 19 12:06:42 sela bluetoothd[4842]: Not enough free handles to register 
service
  led 19 12:06:42 sela bluetoothd[4842]: Current Time Service could not be 
registered
  led 19 12:06:42 sela bluetoothd[4842]: gatt-time-server: Input/output error 
(5)
  led 19 12:06:42 sela bluetoothd[4842]: Not enough free handles to register 
service
  led 19 12:06:42 sela bluetoothd[4842]: Not enough free handles to register 
service
  led 19 12:06:42 sela bluetoothd[4842]: Sap driver initialization failed.
  led 19 12:06:42 sela bluetoothd[4842]: sap-server: Operation not permitted (1)
  led 19 12:06:42 sela bluetoothd[4842]: Endpoint registered: sender=:1.65 
path=/MediaEndpoint/A2DPSource
  led 19 12:06:42 sela bluetoothd[4842]: Endpoint registered: sender=:1.65 
path=/MediaEndpoint/A2DPSink

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluetooth 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64

[Kernel-packages] [Bug 1742998] Re: linux-aws: 4.4.0-1011.11 -proposed tracker

** Description changed:

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

** Tags removed: kernel-sru-backport-of-1743362
** Tags added: kernel-sru-backport-of-1744244

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

Title:
  linux-aws: 4.4.0-1011.11 -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1743001] Re: linux-aws: 4.4.0-1049.58 -proposed tracker