[Kernel-packages] [Bug 1999229] Re: mlx5 VF LAG flapping

[Dmitrii Shcherbakov]

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

Title:
  mlx5 VF LAG flapping

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  # sudo lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  Codename: jammy

  # mlxfwmanager 
  Querying Mellanox devices firmware ...

  Device #1:
  --

Device Type:  ConnectX6DX
Part Number:  MCX623106AN-CDA_Ax
Description:  ConnectX-6 Dx EN adapter card; 100GbE; Dual-port QSFP56; 
PCIe 4.0/3.0 x16;
PSID: MT_000359
PCI Device Name:  :41:00.0
Base GUID:08c0eb03006fb26e
Base MAC: 08c0eb6fb26e
Versions: CurrentAvailable 
   FW 22.34.4000 N/A   
   PXE3.6.0700   N/A   
   UEFI   14.27.0015 N/A   

  # uname -a
  Linux ps6-ra1-n2 5.19.0-24-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri 
Nov 18 14:28:08 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  Kernel from linux-generic-hwe-22.04-edge package in jammy-proposed,
  see https://wiki.ubuntu.com/Testing/EnableProposed for documentation
  how to enable and use -proposed.

  Problem:
  Severe packet loss to high speed NIC due to what appears as VF LAG flapping:
  [Fri Dec  9 07:27:19 2022] mlx5_core :41:00.0: mlx5_cmd_out_err:778:(pid 
3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad 
resource(0x5), syndrome (0xf2ff71), err(-22)
  [Fri Dec  9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to create 
termination table rule, err -EINVAL
  [Fri Dec  9 07:27:19 2022] mlx5_core :41:00.0: E-Switch: Failed to get 
termination table, err -EINVAL
  [Fri Dec  9 07:27:19 2022] mlx5_core :41:00.1: mlx5_cmd_out_err:778:(pid 
3383): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad 
resource(0x5), syndrome (0xf2ff71), err(-22)
  [Fri Dec  9 07:27:19 2022] mlx5_core :41:00.1: E-Switch: Failed to create 
termination table rule, err -EINVAL
  [Fri Dec  9 07:27:19 2022] mlx5_core :41:00.1: E-Switch: Failed to get 
termination table, err -EINVAL
  [Fri Dec  9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 1, 2
  [Fri Dec  9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 2
  [Fri Dec  9 07:27:20 2022] mlx5_core :41:00.0: lag map active ports: 1, 2
  [Fri Dec  9 07:27:21 2022] mlx5_core :41:00.0: lag map active ports: 2
  [Fri Dec  9 07:27:21 2022] mlx5_core :41:00.0: lag map active ports: 1, 2
  [Fri Dec  9 07:27:22 2022] mlx5_core :41:00.0: lag map active ports: 2
  [Fri Dec  9 07:27:23 2022] mlx5_core :41:00.0: lag map active ports: 1, 2
  [Fri Dec  9 07:27:23 2022] mlx5_core :41:00.0: lag map active ports: 2

  This does not happen when using the Jammy 5.15 kernel, everything else
  in the environment being equal.

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


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

[Kernel-packages] [Bug 1995580] [NEW] load of value 8 is not a valid value for type '_Bool'

[Dmitrii Shcherbakov]

Public bug reported:

Getting a call trace below with the 5.17.0-1003-oem OEM kernel.

HW: Lenovo 21D4000HUS

WNIC: 04:00.0 Network controller: Qualcomm QCNFA765 Wireless Network
Adapter (rev 01)


~$ uname -r
5.17.0-1003-oem

ноя 03 10:22:47 dz16 kernel: wlp4s0: send auth to aa:46:8d:38:07:9d (try 1/3)
ноя 03 10:22:47 dz16 kernel: 

ноя 03 10:22:47 dz16 kernel: UBSAN: invalid-load in 
/build/linux-oem-5.17-vTcPy2/linux-oem-5.17-5.17.0/net/mac80211/status.c:1164:21
ноя 03 10:22:47 dz16 kernel: load of value 8 is not a valid value for type 
'_Bool'
ноя 03 10:22:47 dz16 kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 
5.17.0-1003-oem #3-Ubuntu
ноя 03 10:22:47 dz16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
ноя 03 10:22:47 dz16 kernel: Call Trace:
ноя 03 10:22:47 dz16 kernel:  
ноя 03 10:22:47 dz16 kernel:  show_stack+0x52/0x58
ноя 03 10:22:47 dz16 kernel:  dump_stack_lvl+0x4c/0x63
ноя 03 10:22:47 dz16 kernel:  dump_stack+0x10/0x12
ноя 03 10:22:47 dz16 kernel:  ubsan_epilogue+0x9/0x45
ноя 03 10:22:47 dz16 kernel:  __ubsan_handle_load_invalid_value.cold+0x44/0x49
ноя 03 10:22:47 dz16 kernel:  ieee80211_tx_status_ext.cold+0x4e/0x5f [mac80211]
ноя 03 10:22:47 dz16 kernel:  ieee80211_tx_status+0x7d/0xa0 [mac80211]
ноя 03 10:22:47 dz16 kernel:  ieee80211_tasklet_handler+0xa2/0xd0 [mac80211]
ноя 03 10:22:47 dz16 kernel:  tasklet_action_common.constprop.0+0xc0/0xf0
ноя 03 10:22:47 dz16 kernel:  tasklet_action+0x22/0x30
ноя 03 10:22:47 dz16 kernel:  __do_softirq+0xd9/0x315
ноя 03 10:22:47 dz16 kernel:  __irq_exit_rcu+0x87/0xb0
ноя 03 10:22:47 dz16 kernel:  irq_exit_rcu+0xe/0x10
ноя 03 10:22:47 dz16 kernel:  common_interrupt+0x8a/0xa0
ноя 03 10:22:47 dz16 kernel:  
ноя 03 10:22:47 dz16 kernel:  
ноя 03 10:22:47 dz16 kernel:  asm_common_interrupt+0x1e/0x40
ноя 03 10:22:47 dz16 kernel: RIP: 0010:cpuidle_enter_state+0xec/0x630
ноя 03 10:22:47 dz16 kernel: Code: ff e8 a8 ee 6a ff 80 7d d0 00 74 17 9c 58 0f 
1f 44 00 00 f6 c4 02 0f 85 3c 03 00 00 31 ff e8 3b c4 72 ff fb 66 0f 1f 44 00 
00 <45> 85 f6 0f 88 73 01 00 00 4d 63 ee 49 8>
ноя 03 10:22:47 dz16 kernel: RSP: 0018:a571001ffe28 EFLAGS: 0246
ноя 03 10:22:47 dz16 kernel: RAX: 94e422071340 RBX: 94dddb0e8400 RCX: 
0005a1d2ec47
ноя 03 10:22:47 dz16 kernel: RDX: 0005a20ff50b RSI: 0005a1d2ec47 RDI: 

ноя 03 10:22:47 dz16 kernel: RBP: a571001ffe78 R08: 0005a1d2f24e R09: 
000aae60
ноя 03 10:22:47 dz16 kernel: R10: 0004 R11: 071c71c71c71c71c R12: 
a60f6020
ноя 03 10:22:47 dz16 kernel: R13: 0003 R14: 0003 R15: 
0005a1d2f24e
ноя 03 10:22:47 dz16 kernel:  ? cpuidle_enter_state+0xc8/0x630
ноя 03 10:22:47 dz16 kernel:  cpuidle_enter+0x2e/0x40
ноя 03 10:22:47 dz16 kernel:  cpuidle_idle_call+0x13e/0x1d0
ноя 03 10:22:47 dz16 kernel:  do_idle+0x83/0xf0
ноя 03 10:22:47 dz16 kernel:  cpu_startup_entry+0x20/0x30
ноя 03 10:22:47 dz16 kernel:  start_secondary+0x12a/0x180
ноя 03 10:22:47 dz16 kernel:  secondary_startup_64_no_verify+0xd5/0xdb
ноя 03 10:22:47 dz16 kernel:  
ноя 03 10:22:47 dz16 kernel: 


** Affects: linux-oem-5.17 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  load of value 8 is not a valid value for type '_Bool'

Status in linux-oem-5.17 package in Ubuntu:
  New

Bug description:
  Getting a call trace below with the 5.17.0-1003-oem OEM kernel.

  HW: Lenovo 21D4000HUS

  WNIC: 04:00.0 Network controller: Qualcomm QCNFA765 Wireless Network
  Adapter (rev 01)

  
  ~$ uname -r
  5.17.0-1003-oem

  ноя 03 10:22:47 dz16 kernel: wlp4s0: send auth to aa:46:8d:38:07:9d (try 1/3)
  ноя 03 10:22:47 dz16 kernel: 

  ноя 03 10:22:47 dz16 kernel: UBSAN: invalid-load in 
/build/linux-oem-5.17-vTcPy2/linux-oem-5.17-5.17.0/net/mac80211/status.c:1164:21
  ноя 03 10:22:47 dz16 kernel: load of value 8 is not a valid value for type 
'_Bool'
  ноя 03 10:22:47 dz16 kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 
5.17.0-1003-oem #3-Ubuntu
  ноя 03 10:22:47 dz16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, 
BIOS N3GET42W (1.22 ) 09/06/2022
  ноя 03 10:22:47 dz16 kernel: Call Trace:
  ноя 03 10:22:47 dz16 kernel:  
  ноя 03 10:22:47 dz16 kernel:  show_stack+0x52/0x58
  ноя 03 10:22:47 dz16 kernel:  dump_stack_lvl+0x4c/0x63
  ноя 03 10:22:47 dz16 kernel:  dump_stack+0x10/0x12
  ноя 03 10:22:47 dz16 kernel:  ubsan_epilogue+0x9/0x45
  ноя 03 10:22:47 dz16 kernel:  __ubsan_handle_load_invalid_value.cold+0x44/0x49
  ноя 03 10:22:47 dz16 kernel:  ieee80211_tx_status_ext.cold+0x4e/0x5f 
[mac80211]
  ноя 03 10:22:47 

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

[Dmitrii Shcherbakov]

apport information

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

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

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
   

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

[Dmitrii Shcherbakov]

apport information

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

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

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
   

[Kernel-packages] [Bug 1995207] acpidump.txt

[Dmitrii Shcherbakov]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1995207/+attachment/5628253/+files/acpidump.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/1995207

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   

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

[Dmitrii Shcherbakov]

apport information

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

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
  

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

[Dmitrii Shcherbakov]

apport information

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

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
   

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

[Dmitrii Shcherbakov]

apport information

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

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
   

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

[Dmitrii Shcherbakov]

apport information

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

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

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
   

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

[Dmitrii Shcherbakov]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1995207/+attachment/5628246/+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/1995207

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
  

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

[Dmitrii Shcherbakov]

apport information

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

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

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
   

[Kernel-packages] [Bug 1995207] Lsusb-v.txt

[Dmitrii Shcherbakov]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1995207/+attachment/5628244/+files/Lsusb-v.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/1995207

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
   

[Kernel-packages] [Bug 1995207] Lsusb-t.txt

[Dmitrii Shcherbakov]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1995207/+attachment/5628243/+files/Lsusb-t.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/1995207

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
   

[Kernel-packages] [Bug 1995207] Lspci-vt.txt

[Dmitrii Shcherbakov]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1995207/+attachment/5628241/+files/Lspci-vt.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/1995207

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
   

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

[Dmitrii Shcherbakov]

apport information

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

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

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
   

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

[Dmitrii Shcherbakov]

apport information

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

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

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
  

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

[Dmitrii Shcherbakov]

apport information

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

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

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
   mapped:352660 

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

[Dmitrii Shcherbakov]

apport information

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

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
   mapped:352660 

[Kernel-packages] [Bug 1995207] AudioDevicesInUse.txt

[Dmitrii Shcherbakov]

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1995207/+attachment/5628237/+files/AudioDevicesInUse.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/1995207

Title:
  [amdgpu] gnome-shell: page allocation failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome shell crashed while I was doing web browsing.

  A crash report was also submitted via apport. This is a fresh install
  of Ubuntu 22.10.

  ~$ uname -r
  5.19.0-23-generic

  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).

  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)

  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)

  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)

  $ printenv XDG_SESSION_TYPE 
  wayland

  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287

[Kernel-packages] [Bug 1995207] Re: [amdgpu] gnome-shell: page allocation failure

[Dmitrii Shcherbakov]

apport information

** Description changed:

  Gnome shell crashed while I was doing web browsing.
  
  A crash report was also submitted via apport. This is a fresh install of
  Ubuntu 22.10.
  
  ~$ uname -r
  5.19.0-23-generic
  
  HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
  Radeon RX 6500M discrete card (AMD SmartShift).
  
  $ lspci -n -s 03:00.0
  03:00.0 0380: 1002:743f (rev c3)
  
  $ lspci -n -s 67:00.0
  67:00.0 0300: 1002:1681 (rev 12)
  
  03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 
[Radeon RX 6400 / 6500 XT] (rev c3)
  67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Rembrandt [Radeon 680M] (rev 12)
  
  $ printenv XDG_SESSION_TYPE 
  wayland
  
  
  oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, 
mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), 
nodemask=(null),cpuset=/,mems_allowed=0
  oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 
5.19.0-23-generic #24-Ubuntu
  oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS 
N3GET42W (1.22 ) 09/06/2022
  oct 30 13:36:19 z16 kernel: Call Trace:
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel:  show_stack+0x4e/0x61
  oct 30 13:36:19 z16 kernel:  dump_stack_lvl+0x4a/0x6d
  oct 30 13:36:19 z16 kernel:  dump_stack+0x10/0x18
  oct 30 13:36:19 z16 kernel:  warn_alloc+0x164/0x190
  oct 30 13:36:19 z16 kernel:  __alloc_pages_slowpath.constprop.0+0x975/0x9b0
  oct 30 13:36:19 z16 kernel:  __alloc_pages+0x31d/0x350
  oct 30 13:36:19 z16 kernel:  alloc_pages+0x90/0x1c0
  oct 30 13:36:19 z16 kernel:  ttm_pool_alloc+0x395/0x580 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ttm_tt_populate+0xbc/0x1a0 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_handle_move_mem+0x21a/0x280 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_validate+0xf8/0x130 [ttm]
  oct 30 13:36:19 z16 kernel:  ttm_bo_init_reserved+0x18d/0x260 [ttm]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create+0x1d0/0x4b0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_bo_create_user+0x40/0x70 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  drm_ioctl_kernel+0xd6/0x180 [drm]
  oct 30 13:36:19 z16 kernel:  drm_ioctl+0x29d/0x4d0 [drm]
  oct 30 13:36:19 z16 kernel:  ? amdgpu_gem_force_release+0x190/0x190 [amdgpu]
  oct 30 13:36:19 z16 kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  oct 30 13:36:19 z16 kernel:  __x64_sys_ioctl+0xa0/0xe0
  oct 30 13:36:19 z16 kernel:  do_syscall_64+0x5b/0x90
  oct 30 13:36:19 z16 kernel:  ? do_user_addr_fault+0x1df/0x680
  oct 30 13:36:19 z16 kernel:  ? do_syscall_64+0x67/0x90
  oct 30 13:36:19 z16 kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
  oct 30 13:36:19 z16 kernel:  ? irqentry_exit+0x43/0x50
  oct 30 13:36:19 z16 kernel:  ? exc_page_fault+0x91/0x1b0
  oct 30 13:36:19 z16 kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
  oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 
04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 
0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
  oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 
ORIG_RAX: 0010
  oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 
7fc5dcd12d8f
  oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 
0011
  oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 
7fc5dcdf6ec0
  oct 30 13:36:19 z16 kernel: R10:  R11: 0246 R12: 
c0206440
  oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 
0013
  oct 30 13:36:19 z16 kernel:  
  oct 30 13:36:19 z16 kernel: Mem-Info:
  oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 
isolated_anon:0
   active_file:448331 inactive_file:919182 
isolated_file:0
   unevictable:214 dirty:247 writeback:2
   slab_reclaimable:41947 
slab_unreclaimable:65287
   mapped:352660 shmem:166458 pagetables:11885 
bounce:0
   kernel_misc_reclaimable:0
   free:5048298 free_pcp:2656 free_cma:0
  oct 30 13:36:19 z16 kernel: Node 0 active_anon:5432kB inactive_anon:3821164kB 
active_file:1793324kB inactive_file:3676728kB unevictable:856kB 
isolated(anon):0kB isolated(file):0kB 

[Kernel-packages] [Bug 1983468] Re: tx checksumming offload results in TCP/UDP packet drops (was Octavia amphora loadbalancer gets stuck at PENDING_CREATE status)

[Dmitrii Shcherbakov]

As far as looking at the practice of using stateless offload for
tunneled traffic:

I can see that there were tests performed on Intel HW in upstream OpenStack 
with TX & TSO features enabled (albeit with VXLAN tunnels):
https://docs.openstack.org/developer/performance-docs/test_plans/hardware_features/hardware_offloads/plan.html
https://docs.openstack.org/developer/performance-docs/test_results/hardware_features/hardware_offloads/test_results.html#hw-features-offloads

So, in general, I don't see any documented restrictions on the kernel
OVS data path in terms of having stateless offloads enabled.

There was an old bug that had similar symptoms:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1629053

But it couldn't be reproduced eventually:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1629053/comments/3
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1629053/comments/11

This paper also discusses using checksumming offload in the context of the OVS 
datapath:
https://conferences.sigcomm.org/sigcomm/2021/files/papers/3452296.3472914.pdf

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

Title:
  tx checksumming offload results in TCP/UDP packet drops (was Octavia
  amphora loadbalancer gets stuck at PENDING_CREATE status)

Status in OpenStack Octavia Charm:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In a new focal-yoga deployment, the creation of a loadbalancer gets
  stuck at PENDING_CREATE status.

  Checking the amphora we could see that it stays at BOOTING status:

  $ openstack loadbalancer amphora show ef48089d-ba40-46db-92e8-e369f764f017 
--format yaml
  id: ef48089d-ba40-46db-92e8-e369f764f017
  loadbalancer_id: dcd17d9e-6a27-43c5-9c3f-eb2b266d
  compute_id: 5efe11a8-93d8-4278-94c2-4efc8b015009
  lb_network_ip: fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa
  vrrp_ip: null
  ha_ip: null
  vrrp_port_id: null
  ha_port_id: null
  cert_expiration: '2022-09-01T20:27:05'
  cert_busy: false
  role: null
  status: BOOTING
  vrrp_interface: null
  vrrp_id: null
  vrrp_priority: null
  cached_zone: nova
  created_at: '2022-08-02T20:27:05'
  updated_at: '2022-08-02T20:30:13'
  image_id: 6c6cd911-197f-45d3-a6d5-4ff1789d4ee7
  compute_flavor: 638fa4c5-e81b-438f-a12b-1ef7faf81c3e

  
  /var/log/octavia/octavia-worker.log shows several warnings about connection 
failure to the amphora.

  2022-08-02 20:30:22.589 149659 WARNING
  octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect
  to instance. Retrying.: requests.exceptions.ConnectTimeout:
  HTTPSConnectionPool(host='fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa',
  port=9443): Max retries exceeded with url: // (Caused by
  ConnectTimeoutError(, 'Connection to
  fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa timed out. (connect
  timeout=10.0)'))

  
  It is possible to ping the amphora from an octavia unit:

  # ping -M do -s 1452 fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa
  PING 
fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa(fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa)
 1452 data bytes
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=1 ttl=64 
time=2.45 ms
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=2 ttl=64 
time=1.01 ms
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=3 ttl=64 
time=0.532 ms
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=4 ttl=64 
time=0.417 ms

  Also, the port tcp/22 is reacheable from the octavia unit:

  # telnet fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa 22
  Trying fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa...
  Connected to fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa.
  Escape character is '^]'.
  SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.5

  After running the config-changed hook as described at the bug
  https://bugs.launchpad.net/charm-octavia/+bug/1961088 , the creation
  of a loadbalancer ends with a ERROR provisioning_status.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-octavia/+bug/1983468/+subscriptions


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

[Kernel-packages] [Bug 1983468] Re: tx checksumming offload results in TCP/UDP packet drops (was Octavia amphora loadbalancer gets stuck at PENDING_CREATE status)

[Dmitrii Shcherbakov]

Marked this bug as invalid for charm-octavia and added Linux since this
is either a driver problem with bnxt and BCM57414 or a firmware issue.

The card in question: https://buy.hpe.com/us/en/options/adapters/host-
adapters/proliant-host-adapters/hpe-ethernet-10-25gb-2-port-
sfp28-bcm57414-adapter/p/817718-b21

This NIC is handled by the bnxt driver.
https://github.com/torvalds/linux/blob/3d7cb6b04c3f3115719235cc6866b10326de34cd/drivers/net/ethernet/broadcom/bnxt/bnxt.c#L105


The NIC data sheet advertises "TCP, UDP, and IP checksum offloads" and 
"Tunnel-aware stateless offloads":
https://docs.broadcom.com/doc/957414A4142CC-DS

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

Title:
  tx checksumming offload results in TCP/UDP packet drops (was Octavia
  amphora loadbalancer gets stuck at PENDING_CREATE status)

Status in OpenStack Octavia Charm:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In a new focal-yoga deployment, the creation of a loadbalancer gets
  stuck at PENDING_CREATE status.

  Checking the amphora we could see that it stays at BOOTING status:

  $ openstack loadbalancer amphora show ef48089d-ba40-46db-92e8-e369f764f017 
--format yaml
  id: ef48089d-ba40-46db-92e8-e369f764f017
  loadbalancer_id: dcd17d9e-6a27-43c5-9c3f-eb2b266d
  compute_id: 5efe11a8-93d8-4278-94c2-4efc8b015009
  lb_network_ip: fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa
  vrrp_ip: null
  ha_ip: null
  vrrp_port_id: null
  ha_port_id: null
  cert_expiration: '2022-09-01T20:27:05'
  cert_busy: false
  role: null
  status: BOOTING
  vrrp_interface: null
  vrrp_id: null
  vrrp_priority: null
  cached_zone: nova
  created_at: '2022-08-02T20:27:05'
  updated_at: '2022-08-02T20:30:13'
  image_id: 6c6cd911-197f-45d3-a6d5-4ff1789d4ee7
  compute_flavor: 638fa4c5-e81b-438f-a12b-1ef7faf81c3e

  
  /var/log/octavia/octavia-worker.log shows several warnings about connection 
failure to the amphora.

  2022-08-02 20:30:22.589 149659 WARNING
  octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect
  to instance. Retrying.: requests.exceptions.ConnectTimeout:
  HTTPSConnectionPool(host='fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa',
  port=9443): Max retries exceeded with url: // (Caused by
  ConnectTimeoutError(, 'Connection to
  fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa timed out. (connect
  timeout=10.0)'))

  
  It is possible to ping the amphora from an octavia unit:

  # ping -M do -s 1452 fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa
  PING 
fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa(fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa)
 1452 data bytes
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=1 ttl=64 
time=2.45 ms
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=2 ttl=64 
time=1.01 ms
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=3 ttl=64 
time=0.532 ms
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=4 ttl=64 
time=0.417 ms

  Also, the port tcp/22 is reacheable from the octavia unit:

  # telnet fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa 22
  Trying fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa...
  Connected to fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa.
  Escape character is '^]'.
  SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.5

  After running the config-changed hook as described at the bug
  https://bugs.launchpad.net/charm-octavia/+bug/1961088 , the creation
  of a loadbalancer ends with a ERROR provisioning_status.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-octavia/+bug/1983468/+subscriptions


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

[Kernel-packages] [Bug 1983468] Re: tx checksumming offload results in TCP/UDP packet drops (was Octavia amphora loadbalancer gets stuck at PENDING_CREATE status)

[Dmitrii Shcherbakov]

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

** Changed in: charm-octavia
   Status: New => 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/1983468

Title:
  tx checksumming offload results in TCP/UDP packet drops (was Octavia
  amphora loadbalancer gets stuck at PENDING_CREATE status)

Status in OpenStack Octavia Charm:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  In a new focal-yoga deployment, the creation of a loadbalancer gets
  stuck at PENDING_CREATE status.

  Checking the amphora we could see that it stays at BOOTING status:

  $ openstack loadbalancer amphora show ef48089d-ba40-46db-92e8-e369f764f017 
--format yaml
  id: ef48089d-ba40-46db-92e8-e369f764f017
  loadbalancer_id: dcd17d9e-6a27-43c5-9c3f-eb2b266d
  compute_id: 5efe11a8-93d8-4278-94c2-4efc8b015009
  lb_network_ip: fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa
  vrrp_ip: null
  ha_ip: null
  vrrp_port_id: null
  ha_port_id: null
  cert_expiration: '2022-09-01T20:27:05'
  cert_busy: false
  role: null
  status: BOOTING
  vrrp_interface: null
  vrrp_id: null
  vrrp_priority: null
  cached_zone: nova
  created_at: '2022-08-02T20:27:05'
  updated_at: '2022-08-02T20:30:13'
  image_id: 6c6cd911-197f-45d3-a6d5-4ff1789d4ee7
  compute_flavor: 638fa4c5-e81b-438f-a12b-1ef7faf81c3e

  
  /var/log/octavia/octavia-worker.log shows several warnings about connection 
failure to the amphora.

  2022-08-02 20:30:22.589 149659 WARNING
  octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect
  to instance. Retrying.: requests.exceptions.ConnectTimeout:
  HTTPSConnectionPool(host='fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa',
  port=9443): Max retries exceeded with url: // (Caused by
  ConnectTimeoutError(, 'Connection to
  fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa timed out. (connect
  timeout=10.0)'))

  
  It is possible to ping the amphora from an octavia unit:

  # ping -M do -s 1452 fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa
  PING 
fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa(fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa)
 1452 data bytes
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=1 ttl=64 
time=2.45 ms
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=2 ttl=64 
time=1.01 ms
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=3 ttl=64 
time=0.532 ms
  1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=4 ttl=64 
time=0.417 ms

  Also, the port tcp/22 is reacheable from the octavia unit:

  # telnet fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa 22
  Trying fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa...
  Connected to fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa.
  Escape character is '^]'.
  SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.5

  After running the config-changed hook as described at the bug
  https://bugs.launchpad.net/charm-octavia/+bug/1961088 , the creation
  of a loadbalancer ends with a ERROR provisioning_status.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-octavia/+bug/1983468/+subscriptions


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

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Dmitrii Shcherbakov]

Tested the proposed focal kernel - looks good as well:

$ uname -r
5.4.0-98-generic

$ apt policy linux-image-5.4.0-98-generic
linux-image-5.4.0-98-generic:
  Installed: 5.4.0-98.111
  Candidate: 5.4.0-98.111
  Version table:
 *** 5.4.0-98.111 500
500 http://ppa.launchpad.net/canonical-kernel-team/proposed/ubuntu 
focal/main amd64 Packages
100 /var/lib/dpkg/status


$ readlink /sys/class/net/enp130s0f0v0/device
../../../:82:00.3
$ sudo lspci -s :82:00.3 -v
82:00.3 Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen 
Virtual Function (rev 01)
Subsystem: Mellanox Technologies ConnectX Family mlx5Gen Virtual 
Function
Flags: bus master, fast devsel, latency 0, NUMA node 1
Memory at 3c00400 (64-bit, prefetchable) [virtual] [size=2M]
Capabilities: [60] Express Endpoint, MSI 00
Capabilities: [48] Vital Product Data
Capabilities: [9c] MSI-X: Enable+ Count=12 Masked-
Capabilities: [100] Vendor Specific Information: ID= Rev=0 Len=00c 

Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
Kernel driver in use: mlx5_core
Kernel modules: mlx5_core

$ sudo lspci -s :82:00.0 -v
82:00.0 Ethernet controller: Mellanox Technologies MT42822 BlueField-2 
integrated ConnectX-6 Dx network controller (rev 01)
Subsystem: Mellanox Technologies MT42822 BlueField-2 integrated 
ConnectX-6 Dx network controller
Flags: bus master, fast devsel, latency 0, IRQ 99, NUMA node 1
Memory at 3c00200 (64-bit, prefetchable) [size=32M]
Expansion ROM at  [disabled]
Capabilities: [60] Express Endpoint, MSI 00
Capabilities: [48] Vital Product Data
Capabilities: [9c] MSI-X: Enable+ Count=64 Masked-
Capabilities: [c0] Vendor Specific Information: Len=18 
Capabilities: [40] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
Capabilities: [180] Single Root I/O Virtualization (SR-IOV)
Capabilities: [1c0] Secondary PCI Express
Capabilities: [230] Access Control Services
Capabilities: [320] Lane Margining at the Receiver 
Capabilities: [370] Physical Layer 16.0 GT/s 
Capabilities: [420] Data Link Feature 
Kernel driver in use: mlx5_core
Kernel modules: mlx5_core

$ sudo ip link set enp130s0f0 vf 0 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2

$ sudo ip link set enp130s0f0 vf 0 vlan 0 ; echo $?
0


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

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16

  From patch description:
  When using libvirt to passthrough VF to VM it will always set the VF vlan
  to 0 even if user didn’t request it, this will cause libvirt to fail to
  boot in case the PF isn't eswitch owner.

  Example of such case is the DPU host PF which isn't eswitch manager, so
  any attempt to passthrough VF of it using libvirt will fail.

  [Fix]
  * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
   eswitch manager

  This patch can be cherry-picked into Impish and newer kernels, but it
  requires some backport work on F/H due to they're missing commit
  b55b3538 that split the legacy code out.

  The ESW_ALLOWED marco was later converted into a helper routine in
  commit b16f2bb6.

  [Test]
  Test kernels can be found here:
  F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
  H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
  I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
  J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/

  Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
  passed with positive feedback.

  [Where problems could occur]
  If this patch is erroneous, it might cause issue to this mlx5 driver
  with certain operations (setting vid 0). And other programs such as
  libvirt that depends on this return value might be affected as well.

  [Original Bug Description]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16 that was recently fixed in master with a 
one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/comm

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Dmitrii Shcherbakov]

Tried the proposed impish kernel - looks good:

$ uname -r
5.13.0-29-generic

$ apt policy linux-image-5.13.0-29-generic 
linux-image-5.13.0-29-generic:
  Installed: 5.13.0-29.32
  Candidate: 5.13.0-29.32
  Version table:
 *** 5.13.0-29.32 500
500 http://ppa.launchpad.net/canonical-kernel-team/proposed/ubuntu 
impish/main amd64 Packages
100 /var/lib/dpkg/status

$ readlink /sys/class/net/enp130s0f0v0/device
../../../:82:00.3

# VF
$ sudo lspci -s :82:00.3 -v
82:00.3 Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen 
Virtual Function (rev 01)
Subsystem: Mellanox Technologies ConnectX Family mlx5Gen Virtual 
Function
Flags: bus master, fast devsel, latency 0, NUMA node 1
Memory at 3c00400 (64-bit, prefetchable) [virtual] [size=2M]
Capabilities: [60] Express Endpoint, MSI 00
Capabilities: [48] Vital Product Data
Capabilities: [9c] MSI-X: Enable+ Count=12 Masked-
Capabilities: [100] Vendor Specific Information: ID= Rev=0 Len=00c 

Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
Kernel driver in use: mlx5_core
Kernel modules: mlx5_core

# Parent PF
$ sudo lspci -s :82:00.0 -v
82:00.0 Ethernet controller: Mellanox Technologies MT42822 BlueField-2 
integrated ConnectX-6 Dx network controller (rev 01)
Subsystem: Mellanox Technologies MT42822 BlueField-2 integrated 
ConnectX-6 Dx network controller
Flags: bus master, fast devsel, latency 0, IRQ 101, NUMA node 1
Memory at 3c00200 (64-bit, prefetchable) [size=32M]
Expansion ROM at  [disabled]
Capabilities: [60] Express Endpoint, MSI 00
Capabilities: [48] Vital Product Data
Capabilities: [9c] MSI-X: Enable+ Count=64 Masked-
Capabilities: [c0] Vendor Specific Information: Len=18 
Capabilities: [40] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
Capabilities: [180] Single Root I/O Virtualization (SR-IOV)
Capabilities: [1c0] Secondary PCI Express
Capabilities: [230] Access Control Services
Capabilities: [320] Lane Margining at the Receiver 
Capabilities: [370] Physical Layer 16.0 GT/s 
Capabilities: [420] Data Link Feature 
Kernel driver in use: mlx5_core
Kernel modules: mlx5_core


$ sudo ip link set enp130s0f0 vf 0 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2

$ sudo ip link set enp130s0f0 vf 0 vlan 0 ; echo $?
0


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

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16

  From patch description:
  When using libvirt to passthrough VF to VM it will always set the VF vlan
  to 0 even if user didn’t request it, this will cause libvirt to fail to
  boot in case the PF isn't eswitch owner.

  Example of such case is the DPU host PF which isn't eswitch manager, so
  any attempt to passthrough VF of it using libvirt will fail.

  [Fix]
  * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
   eswitch manager

  This patch can be cherry-picked into Impish and newer kernels, but it
  requires some backport work on F/H due to they're missing commit
  b55b3538 that split the legacy code out.

  The ESW_ALLOWED marco was later converted into a helper routine in
  commit b16f2bb6.

  [Test]
  Test kernels can be found here:
  F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
  H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
  I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
  J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/

  Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
  passed with positive feedback.

  [Where problems could occur]
  If this patch is erroneous, it might cause issue to this mlx5 driver
  with certain operations (setting vid 0). And other programs such as
  libvirt that depends on this return value might be affected as well.

  [Original Bug Description]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16 that was recently fixed in master with a 
one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/comm

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Dmitrii Shcherbakov]

Thanks!

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  In Progress
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16

  From patch description:
  When using libvirt to passthrough VF to VM it will always set the VF vlan
  to 0 even if user didn’t request it, this will cause libvirt to fail to
  boot in case the PF isn't eswitch owner.

  Example of such case is the DPU host PF which isn't eswitch manager, so
  any attempt to passthrough VF of it using libvirt will fail.

  [Fix]
  * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
   eswitch manager

  This patch can be cherry-picked into Impish and newer kernels, but it
  requires some backport work on F/H due to they're missing commit
  b55b3538 that split the legacy code out.

  The ESW_ALLOWED marco was later converted into a helper routine in
  commit b16f2bb6.

  [Test]
  Test kernels can be found here:
  F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
  H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
  I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
  J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/

  Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
  passed with positive feedback.

  [Where problems could occur]
  If this patch is erroneous, it might cause issue to this mlx5 driver
  with certain operations (setting vid 0). And other programs such as
  libvirt that depends on this return value might be affected as well.

  [Original Bug Description]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16 that was recently fixed in master with a 
one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Dmitrii Shcherbakov]

And, finally, the Jammy kernel:

$ uname -r
5.15.0-17-generic

$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0

$ sudo ip link set enp130s0f0 vf 2 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2


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

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

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

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed
Status in linux source package in Impish:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16 that was recently fixed in master
  with a one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Dmitrii Shcherbakov]

Impish kernel looks good:

$ uname -r
5.13.0-28-generic

$ sudo ip link set enp130s0f0 vf 2 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2

$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16 that was recently fixed in master
  with a one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Dmitrii Shcherbakov]

Hirsute kernel looks good as well:

$ uname -r
5.11.0-50-generic

$ sudo ip link set enp130s0f0 vf 2 vlan 1 ; echo $?
RTNETLINK answers: Operation not permitted
2

$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16 that was recently fixed in master
  with a one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Dmitrii Shcherbakov]

Focal:

$ uname -r
5.4.0-97-generic

$ sudo ip link set enp130s0f0 vf 2 vlan 1
RTNETLINK answers: Operation not permitted

$ sudo ip link set enp130s0f0 vf 2 vlan 0 ; echo $?
0

Looks good - vlan 0 programming doesn't result in EPERM as expected
contrary to non-zero vlans.

Will try others as well. It would be good to backport it to currently
released versions above Focal (for production, we are mostly looking for
Focal GA + HWE kernels but it keeping it fixed consistently seems like
the right approach).

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16 that was recently fixed in master
  with a one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1957753] [NEW] net/mlx5e: EPERM on vlan 0 programming

[Dmitrii Shcherbakov]

Public bug reported:

There is an issue with hypervisor host side mlx5 driver operation on
Bluefield devices in kernels <=5.16 that was recently fixed in master
with a one-liner:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

It would be good to have this fix in Focal+ kernels.

This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
bluefield since it's used at the DPU side whereas the issue in question
affects the hypervisor side.

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

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  New

Bug description:
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16 that was recently fixed in master
  with a one-liner:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1918583] Re: Switch to libgpiod and disable CONFIG_GPIO_SYSFS

[Dmitrii Shcherbakov]

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

Title:
  Switch to libgpiod and disable CONFIG_GPIO_SYSFS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu kernels are built with CONFIG_GPIO_SYSFS=y after
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153

  debian.master/config/config.common.ubuntu: CONFIG_GPIO_SYSFS=y

  However, this interface got deprecated for removal:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0910d72afc69b25703f7be9bf7d13f18937a478
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe95046e960b4b76e73dc1486955d93f47276134
  "This marks the (optional) sysfs GPIO ABI as obsolete and schedules it for 
removal in 2020."

  https://www.kernel.org/doc/Documentation/gpio/sysfs.txt
  "THIS ABI IS DEPRECATED, THE ABI DOCUMENTATION HAS BEEN MOVED TO 
Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS
  ARE SUPPOSED TO USE THE CHARACTER DEVICE ABI. THIS OLD SYSFS ABI WILL
  NOT BE DEVELOPED (NO NEW FEATURES), IT WILL JUST BE MAINTAINED."

  libgpiod and the use of a character file-based interface is a
  replacement to the sysfs interface:

  https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/

  
  Those two interfaces cannot be used interchangeably and working via libgpiod 
is not possible when the sysfs interface is used:

  sudo gpioget gpiochip0 12
  gpioget: error reading GPIO values: Device or resource busy

  sudo gpioinfo  | grep 12
line  12: "GPIO12"  "sysfs"   input  active-high [used]

  
  It would be good to switch to a newer interface since the old one does not 
get new features and there is no way to switch to libgpiod besides recompiling 
the kernel with "CONFIG_GPIO_SYSFS=n"

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

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

[Kernel-packages] [Bug 1918583] [NEW] Switch to libgpiod and disable CONFIG_GPIO_SYSFS

[Dmitrii Shcherbakov]

Public bug reported:

Ubuntu kernels are built with CONFIG_GPIO_SYSFS=y after
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153

debian.master/config/config.common.ubuntu: CONFIG_GPIO_SYSFS=y

However, this interface got deprecated for removal:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0910d72afc69b25703f7be9bf7d13f18937a478
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe95046e960b4b76e73dc1486955d93f47276134
"This marks the (optional) sysfs GPIO ABI as obsolete and schedules it for 
removal in 2020."

https://www.kernel.org/doc/Documentation/gpio/sysfs.txt
"THIS ABI IS DEPRECATED, THE ABI DOCUMENTATION HAS BEEN MOVED TO 
Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS
ARE SUPPOSED TO USE THE CHARACTER DEVICE ABI. THIS OLD SYSFS ABI WILL
NOT BE DEVELOPED (NO NEW FEATURES), IT WILL JUST BE MAINTAINED."

libgpiod and the use of a character file-based interface is a
replacement to the sysfs interface:

https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/


Those two interfaces cannot be used interchangeably and working via libgpiod is 
not possible when the sysfs interface is used:

sudo gpioget gpiochip0 12
gpioget: error reading GPIO values: Device or resource busy

sudo gpioinfo  | grep 12
line  12: "GPIO12"  "sysfs"   input  active-high [used]


It would be good to switch to a newer interface since the old one does not get 
new features and there is no way to switch to libgpiod besides recompiling the 
kernel with "CONFIG_GPIO_SYSFS=n"

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

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

Title:
  Switch to libgpiod and disable CONFIG_GPIO_SYSFS

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu kernels are built with CONFIG_GPIO_SYSFS=y after
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153

  debian.master/config/config.common.ubuntu: CONFIG_GPIO_SYSFS=y

  However, this interface got deprecated for removal:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0910d72afc69b25703f7be9bf7d13f18937a478
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe95046e960b4b76e73dc1486955d93f47276134
  "This marks the (optional) sysfs GPIO ABI as obsolete and schedules it for 
removal in 2020."

  https://www.kernel.org/doc/Documentation/gpio/sysfs.txt
  "THIS ABI IS DEPRECATED, THE ABI DOCUMENTATION HAS BEEN MOVED TO 
Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS
  ARE SUPPOSED TO USE THE CHARACTER DEVICE ABI. THIS OLD SYSFS ABI WILL
  NOT BE DEVELOPED (NO NEW FEATURES), IT WILL JUST BE MAINTAINED."

  libgpiod and the use of a character file-based interface is a
  replacement to the sysfs interface:

  https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/

  
  Those two interfaces cannot be used interchangeably and working via libgpiod 
is not possible when the sysfs interface is used:

  sudo gpioget gpiochip0 12
  gpioget: error reading GPIO values: Device or resource busy

  sudo gpioinfo  | grep 12
line  12: "GPIO12"  "sysfs"   input  active-high [used]

  
  It would be good to switch to a newer interface since the old one does not 
get new features and there is no way to switch to libgpiod besides recompiling 
the kernel with "CONFIG_GPIO_SYSFS=n"

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

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

[Kernel-packages] [Bug 1765998] Re: FS access deadlock with btrfs quotas enabled

[Dmitrii Shcherbakov]

Recently hit that on Focal due to the fact that quotas were enabled by
LXD.

This renders the system completely unresponsive if you use btrfs as a
rootfs with btrfs-transaction or btrfs-cleaner kernel threads hogging a
100% of 1 CPU core.

Booting using a live USB, disabling quotas and temporarily moving
/etc/systemd/system/snap-lxd-* files out helps (followed by `snap
disable lxd` until it gets updated with
https://github.com/lxc/lxd/pull/7032).

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

Title:
  FS access deadlock with btrfs quotas enabled

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

Bug description:
  I'm running into an issue on Ubuntu Bionic (but not Xenial) where
  shortly after boot, under heavy load from many LXD containers starting
  at once, access to the btrfs filesystem that the containers are on
  deadlocks.

  The issue is quite hard to reproduce on other systems, quite likely
  related to the size of the filesystem involved (4 devices with a total
  of 8TB, millions of files, ~20 subvolumes with tens of snapshots each)
  and the access pattern from many LXD containers at once. It definitely
  goes away when disabling btrfs quotas though. Another prerequisite to
  trigger this bug may be the container subvolumes sharing extents (from
  their parent image or due to deduplication).

  I can only reliably reproduce it on a production system that I can only do 
very limited testing on, however I have been able to gather the following 
information:
  - Many threads are stuck, trying to aquire locks on various tree roots, which 
are never released by their current holders.
  - There always seem to be (at least) two threads executing rmdir syscalls 
which are creating the circular dependency: One of them is in btrfs_cow_block 
=> ... => btrfs_qgroup_trace_extent_post => ... => find_parent_nodes and wants 
to acquire a lock that was already aquired by btrfs_search_slot of the other 
rmdir.
  - Reverting this patch seems to prevent it from happening: 
https://patchwork.kernel.org/patch/9573267/

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

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

[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[Dmitrii Shcherbakov]

** Tags added: champagne

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing

[Dmitrii Shcherbakov]

Sandor,

Not on the VRF usage side but there is a feature in MAAS 2.6 to have a
better way to work in multi-homed environments (for bionic+ machines):

https://docs.maas.io/2.6/en/intro-new
"Networking - Multiple default gateways"

It relies on "routing policy database" (RPDB) functionality
https://paste.ubuntu.com/p/xg6vFm8Hx7/ (netplan config, routing-policy sections 
are defined only for subnets that have a gateway configured in MAAS)

At the target machine you will see something like this:

# ip rule
0:  from all lookup local 
0:  from 10.232.24.0/21 to 10.232.24.0/21 lookup main 
0:  from 10.232.40.0/21 to 10.232.40.0/21 lookup main 
100:from 10.232.24.0/21 lookup 2 
100:from 10.232.40.0/21 lookup 1 
32766:  from all lookup main 
32767:  from all lookup default 

# ip route show table 1
default via 10.232.40.1 dev b-enp4s0f0-2730 proto static 

# ip route show table 2
default via 10.232.24.1 dev b-enp4s0f0-2731 proto static 

This works well for TCP when responding to traffic (even when software
listens on 0.0.0.0). For UDP a frequent server use-case is DNS servers
and bind9 binds its UDP sockets to interface addresses directly as
opposed to using 0.0.0.0 (some other DNS servers do the same, e.g.
PowerDNS - they even have a post about it
https://blog.powerdns.com/2012/10/08/on-binding-datagram-udp-sockets-to-
the-any-addresses/).

For sending, the policy rules will also kick in provided that a client
socket (TCP or UDP) is bound to a specific address (so that the source
IP is not automatically selected). This requires that the target
software supports binding client sockets to specific addresses
unfortunately.

So far using static routes to summarized prefixes has been a solution
for east-west traffic (because we control nodes managed by MAAS) and
using the approach above for client responses to arbitrary networks (via
https://jaas.ai/u/canonical-bootstack/policy-routing).

After juju starts supporting this new MAAS feature
https://bugs.launchpad.net/juju/+bug/1829150 we can stop using charm-
policy-routing.

I hope that helps while VRF functionality is not implemented.

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

Title:
  VRF support to solve routing problems associated with multi-homing

Status in juju:
  Incomplete
Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem description:

  * a host is multi-homed if it has multiple network interfaces with L3
  addresses configured (physical or virtual interfaces, natural to
  OpenStack regardless of IPv4/IPv6 and IPv6 in general);

  (see 3.3.4  Local Multihoming
  https://tools.ietf.org/html/rfc1122#page-60 and 3.3.4.2  Multihoming
  Requirements)

  * if all hosts that need to participate in L3 communication are
  located on the same L2 network there is no need for a routing device
  to be present. ARP/NDP and auto-created directly connected routes are
  enough;

  * multi-homing with hosts located on different L2 networks requires more 
intelligent routing:
    - "directly connected" routes are no longer enough to talk to all relevant 
hosts in the same network space;
    - a default gateway in the main routing table may not be the correct 
routing device that knows where to forward traffic (management network traffic 
goes to a management switch and router, other traffic goes to L3 ToR switch but 
may go via different bonds);
    - even if a default gateway knows where to forward traffic, it may not be 
the intended physical path (storage replication traffic must go through a 
specific outgoing interface, not the same interface as storage access traffic 
although both interfaces are connected to the same ToR);
    - there is no longer a single "default gateway" as applications need either 
per-logical-direction routers or to become routers themselves (if destination 
== X, forward to next-hop Y). Leaf-spine architecture is a good example of how 
multiple L2 networks force you to use spaces that have VLANs in different 
switch fabrics => one or more hops between hosts with interfaces associated 
with the same network space;
    - while network spaces implicitly require L3 reachability between each host 
that has a NIC associated with a network space, the current definition does not 
mention routing infrastructure required for that. For a single L2 this problem 
is hidden by directly connected routes, for multi-L2, no solution is provided 
or discussed;

  * existing solutions to multi-homing require routing table management
  on a given host: complex static routing rules, dynamic routing (e.g.
  running an OSPF or BGP daemon on a host);

  * using static routes is rigid and requires network planning (i.e.
  working with network engineers which may have varying degrees of
  experience, doing VLSM planning etc.);

  * using dynamic routing requires a broader 

[Kernel-packages] [Bug 1829563] Re: bcache device is accessible even if a backing device is not (writeback mode)

[Dmitrii Shcherbakov]

Setting to 'Confirmed' as the issue was fixed upstream and this is a
backport request.

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

** Summary changed:

- bcache device is accessible even if a backing device is not (writeback mode)
+ [4.15] bcache device is accessible even if a backing device is not (writeback 
mode)

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

Title:
  [4.15] bcache device is accessible even if a backing device is not
  (writeback mode)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a request for a backport of the following upstream patch from
  4.18:

  "bcache: stop bcache device when backing device is offline"
  
https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee

  Field engineering uses bcache quite extensively and it would be good
  to have this in the GA/bionic kernel.

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

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

[Kernel-packages] [Bug 1829563] [NEW] bcache device is accessible even if a backing device is not (writeback mode)

[Dmitrii Shcherbakov]

Public bug reported:

This is a request for a backport of the following upstream patch from
4.18:

"bcache: stop bcache device when backing device is offline"
https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee

Field engineering uses bcache quite extensively and it would be good to
have this in the GA/bionic kernel.

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


** Tags: cpe-onsite

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

Title:
  bcache device is accessible even if a backing device is not (writeback
  mode)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a request for a backport of the following upstream patch from
  4.18:

  "bcache: stop bcache device when backing device is offline"
  
https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee

  Field engineering uses bcache quite extensively and it would be good
  to have this in the GA/bionic kernel.

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

Tried using direct kernel boot with QEMU and couldn't reproduce it:

sha256sum 
/mnt/libvirt-images/boot-resources-20190419-115735/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/boot-initrd
69ca457a119fe309d315972ca2756a17bd9bc55bc98f2bea5542566a7f41b08f  
/mnt/libvirt-images/boot-resources-20190419-115735/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/boot-initrd


30463 qemu-system-x86_64 -enable-kvm -name guest=maas-vhost6,debug-threads=on 
-S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-224-maas-vhost6/master-key.aes
 -machine pc-q35-2.11,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu 
Haswell-noTSX-IBRS,vme=on,ss=on,vmx=on,f16c=on,rdrand=on,hypervisor=on,arat=on,tsc_adjust=on,ssbd=on,xsaveopt=on,pdpe1gb=on,abm=on
 -m 2048 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 
399eae83-f059-4ac0-9609-5bb548f5a90a -no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-224-maas-vhost6/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew 
-global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global 
ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1 -boot strict=on -kernel 
/mnt/libvirt-images/boot-resources-20190419-115735/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/boot-kernel
 -initrd 
/mnt/libvirt-images/boot-resources-20190419-115735/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/boot-initrd
 -append 
BOOT_IMAGE=http://10.10.101.2:5248/images/ubuntu/amd64/ga-18.04/bionic/daily/boot-kernel
 nomodeset ro 
root=squash:http://10.10.101.2:5248/images/ubuntu/amd64/ga-18.04/bionic/daily/squashfs
 ip=maas-vhost6:BOOTIF ip6=off overlayroot=tmpfs 
overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc 
cloud-config-url=http://10.10.101.2:5248/MAAS/metadata/latest/by-id/xeqrrw/?op=get_preseed
 apparmor=0 log_host=10.10.101.2 log_port=5247 --- console=ttyS0,115200 
initrd=http://10.10.101.2:5248/images/ubuntu/amd64/ga-18.04/bionic/daily/boot-initrd
 BOOTIF=01-52-54-00-3f-ae-46 -device 
pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2
 -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 
-device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 
-device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 
-device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 
-device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 
-device pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x6 
-device i82801b11-bridge,id=pci.8,bus=pcie.0,addr=0x1e -device 
pci-bridge,chassis_nr=9,id=pci.9,bus=pci.8,addr=0x0 -device 
ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x1d.0x7 -device 
ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x1d
 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x1d.0x1 
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x1d.0x2 
-device virtio-scsi-pci,id=scsi0,bus=pci.2,addr=0x0 -device 
virtio-scsi-pci,id=scsi1,bus=pci.4,addr=0x0 -device 
ahci,id=sata1,bus=pci.9,addr=0x1 -device ahci,id=sata2,bus=pci.9,addr=0x2 
-device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 -drive 
file=/mnt/libvirt-images/vhost6.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 
-device 
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2
 -drive 
file=/mnt/libvirt-images/maas-vhost6.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-1,serial=disk0
 -device 
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi0-0-0-1,id=scsi0-0-0-1
 -drive 
file=/mnt/libvirt-images/masa-vhost6-scsi21.qcow2,format=qcow2,if=none,id=drive-scsi1-0-0-2,serial=disk1
 -device 
scsi-hd,bus=scsi1.0,channel=0,scsi-id=0,lun=2,drive=drive-scsi1-0-0-2,id=scsi1-0-0-2
 -drive 
file=/mnt/libvirt-images/maas-vhost6-virtio0.qcow2,format=qcow2,if=none,id=drive-virtio-disk0
 -device 
virtio-blk-pci,scsi=off,bus=pci.6,addr=0x0,drive=drive-virtio-disk0,id=virtio-disk0
 -drive 
file=/mnt/libvirt-images/maas-vhost6-virtio1.qcow2,format=qcow2,if=none,id=drive-virtio-disk1,serial=disk3
 -device 
virtio-blk-pci,scsi=off,bus=pci.7,addr=0x0,drive=drive-virtio-disk1,id=virtio-disk1
 -drive 
file=/mnt/libvirt-images/maas-vhost6-sata0.qcow2,format=qcow2,if=none,id=drive-sata0-0-3,serial=disk4
 -device ide-hd,bus=ide.3,drive=drive-sata0-0-3,id=sat


virsh dumpxml exempt:

  
hvm

/mnt/libvirt-images/boot-resources-20190419-115735/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/boot-kernel

/mnt/libvirt-images/boot-resources-20190419-115735/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/boot-initrd

BOOT_IMAGE=http://10.10.101.2:5248/images/ubuntu/amd64/ga-18.04/bionic/daily/boot-kernel
 nomodeset ro 

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

The bionic/ga files from #63 need to be placed into both dirs:

1) /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-18.04/bionic/daily
2) /var/lib/maas/boot-resources/current/ubuntu/amd64/generic/bionic/daily

The sha256 of the *initrd file* that triggers the issue is

69ca457a119fe309d315972ca2756a17bd9bc55bc98f2bea5542566a7f41b08f

Be careful with daily image auto-updates because a recent update have
overridden the files for me and the issue was no longer possible to
reproduce.

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

tar -czvf boot-resources-20190419-115735-amd64-generic-bionic.tar.gz 
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/squashfs
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/boot-kernel
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/boot-initrd


** Attachment added: 
"boot-resources-20190419-115735-amd64-generic-bionic.tar.gz"
   
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5258219/+files/boot-resources-20190419-115735-amd64-generic-bionic.tar.gz

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

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

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

Tested bionic-hwe - the issue does not occur with 2048 MiB.

The closest issue filed upstream I found is this:
https://bugzilla.kernel.org/show_bug.cgi?id=199845

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

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

Found something interesting.

Bionic + 2048 MiB of RAM (bad):

[1.520243] Unpacking initramfs...
[   14.712821] Initramfs unpacking failed: broken padding
[   14.723088] Freeing initrd memory: 56636K

Bionic + 2049 MiB of RAM (good):

[0.752624] Unpacking initramfs...
[5.572407] Freeing initrd memory: 56636K

Xenial HWE + 2048 MiB of RAM (bad):

[5.598647] Unpacking initramfs...
[   84.494431] Initramfs unpacking failed: junk in compressed archive
[   84.503565] Freeing initrd memory: 54564K

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

I cannot reproduce the same with a xenial (GA kernel) image with 2048
MiB of RAM allocated to a VM.

So it seems to me that this is a kernel issue.

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

The kernel code path mentioned in #55 is only executed if there is no
"early userspace init" - in other words, if there is no /init on initrd:

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/tree/init/main.c?id=Ubuntu-4.15.0-47.50#n1087

/*
 * check if there is an early userspace init.  If yes, let it do all
 * the work
 */

if (!ramdisk_execute_command)
ramdisk_execute_command = "/init";  // <--- if there's no 
command specified, default to /init

if (sys_access((const char __user *) ramdisk_execute_command, 0) != 0) 
{  // <-- check if /init is present by doing the access syscall
ramdisk_execute_command = NULL;
prepare_namespace();  // <-- call prepare_namespace as 
mentioned in #55 which results in an error
}


However, I can see that the initrd used in my case contains the init script (so 
sys_access should be successful):

initrd=http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily
/boot-initrd

 lsinitramfs 
/var/lib/maas/boot-resources/current/ubuntu/amd64/generic/bionic/daily/boot-initrd
 | grep -P ^init$
init

If I increase the memory allocation from 2048 to 2049 MiB the machine
starts to boot just fine.

Unsuccessful boot log (2048 MiB): https://paste.ubuntu.com/p/CY834ZGnvS/
Successful boot log (2049 MiB): https://paste.ubuntu.com/p/3fYfFXW8qR/

Attached boot-initrd.


** Attachment added: "boot-initrd"
   
https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5257069/+files/boot-initrd

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

echo -n 
'BOOT_IMAGE=http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily/boot-kernel
 nomodeset ro 
root=squash:http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily/squashfs
 ip=maas-vhost6:BOOTIF ip6=off overlayroot=tmpfs 
overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc 
cloud-config-url=http://10.10.101.2:5248/MAAS/metadata/latest/by-id/xeqrrw/?op=get_preseed
 apparmor=0 log_host=10.10.101.2 log_port=5247 --- console=ttyS0,115200 
initrd=http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily/boot-initrd
 BOOTIF=01-52-54-00-3f-ae-46' | wc -c
576

arch/x86/include/asm/setup.h:

#define COMMAND_LINE_SIZE 2048
#define PARAM_SIZE 4096 /* sizeof(struct boot_params) */


Doesn't look like we are any close to the kernel limits on parameters.

However, the root argument as printed in the panic message looks like a
64-byte string (last byte for null termination):

echo -n 'squash:http://10.10.101.2:5248/images/ubuntu/amd64/generic/bion' | wc 
-c
63


It looks like this is coming from the following code (strlcpy into a 64-byte 
array):

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/tree/init/do_mounts.c?id=Ubuntu-4.15.0-47.50#n42

static char __initdata saved_root_name[64];

static int __init root_dev_setup(char *line)
{
strlcpy(saved_root_name, line, sizeof(saved_root_name));
return 1;
}

__setup("root=", root_dev_setup);


And the overall code-path (judging by the md auto-detection log messages):

https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/init/do_mounts.c?id=Ubuntu-4.15.0-47.50#n545
prepare_namespace -> 

if (saved_root_name[0]) {
root_device_name = saved_root_name;   // < (!) usage of a 
cut-down root param
if (!strncmp(root_device_name, "mtd", 3) ||
!strncmp(root_device_name, "ubi", 3)) {
mount_block_root(root_device_name, root_mountflags);

Does not look like we are hitting either EACCES or EINVAL and so we fall
through to panic():

https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/init/do_mounts.c?id=Ubuntu-4.15.0-47.50#n381
void __init mount_block_root(char *name, int flags)
// ...
for (p = fs_names; *p; p += strlen(p)+1) {
int err = do_mount_root(name, p, flags, root_mount_data);
switch (err) {
case 0:
goto out;
case -EACCES:
case -EINVAL:
continue;
}
/*
 * Allow the user to distinguish between failed sys_open
 * and bad superblock on root device.
 * and give them a list of the available devices
 */
#ifdef CONFIG_BLOCK
__bdevname(ROOT_DEV, b);
#endif
printk("VFS: Cannot open root device \"%s\" or %s: error %d\n",
root_device_name, b, err);
printk("Please append a correct \"root=\" boot option; here are 
the available partitions:\n");

printk_all_partitions();
#ifdef CONFIG_DEBUG_BLOCK_EXT_DEVT
printk("DEBUG_BLOCK_EXT_DEVT is enabled, you need to specify "
   "explicit textual name for \"root=\" boot option.\n");
#endif
panic("VFS: Unable to mount root fs on %s", b);

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

[Dmitrii Shcherbakov]

Just reproduced it on my env (where things used to work) after updating
from MAAS 2.5.0~rc2 to 2.5.2.

https://paste.ubuntu.com/p/CY834ZGnvS/
[   15.458594] VFS: Cannot open root device 
"squash:http://10.10.101.2:5248/images/ubuntu/amd64/generic/bion; or 
unknown-block(0,0): error -6

tree /var/lib/maas/boot-resources/
/var/lib/maas/boot-resources/
# ...

├── current -> snapshot-20190419-115735
└── snapshot-20190419-115735


Which binaries do I need to have uploaded?

sha256sum 
/var/lib/maas/boot-resources/snapshot-20190419-115735/ubuntu/amd64/ga-18.04/bionic/daily/*
69ca457a119fe309d315972ca2756a17bd9bc55bc98f2bea5542566a7f41b08f  
/var/lib/maas/boot-resources/snapshot-20190419-115735/ubuntu/amd64/ga-18.04/bionic/daily/boot-initrd
166853ad9342fdf5be17988e5e18cbf0458ab0da94f18f5e331b3581e3610b97  
/var/lib/maas/boot-resources/snapshot-20190419-115735/ubuntu/amd64/ga-18.04/bionic/daily/boot-kernel
1e7841d7fca13ef27c2742cfc2c3a2d59491a74c268b705a02eb4ee8f673d150  
/var/lib/maas/boot-resources/snapshot-20190419-115735/ubuntu/amd64/ga-18.04/bionic/daily/squashfs


ii  seabios1.10.2-1ubuntu1  
   all  Legacy BIOS implementation
ii  ipxe-qemu  
1.0.0+git-20180124.fbe8c52d-0ubuntu2.2  all 
 PXE boot firmware - ROM images for qemu
ii  qemu-kvm   1:2.11+dfsg-1ubuntu7.12  
   amd64QEMU Full virtualization on x86 
hardware
ii  libvirt0:amd64 4.0.0-1ubuntu8.8 
   amd64library for interfacing with 
different virtualization systems

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

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

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

[Kernel-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

[Dmitrii Shcherbakov]

Had this with nvidia graphics drivers after installing and then removing
proprietary drivers downloaded from nvidia website. I could not log in
at all at first boot.

If you see nvidia modules loaded, make sure that you select an xorg
session on the login screen (not wayland) if you this control presented
to you.

lsmod| grep nvidia
nvidia_uvm794624  0
nvidia_drm 40960  13
nvidia_modeset   1040384  1 nvidia_drm
nvidia  17285120  653 nvidia_uvm,nvidia_modeset
ipmi_msghandler   102400  2 ipmi_devintf,nvidia
drm_kms_helper172032  2 nvidia_drm,i915
drm   458752  13 drm_kms_helper,nvidia_drm,i915

Alternatively, just set WaylandEnable to false (and restart gdm).

cat /etc/gdm3/custom.conf
# ...
[daemon]
# Uncoment the line below to force the login screen to use Xorg
WaylandEnable=false
# ...

I also suspect that /etc/X11/xorg.conf generated by nvidia-xconfig
(which I ran during driver installation from the website) was causing
issues.

Steps I performed from a VT session:

1) sudo apt purge 'nvidia*'
2) reboot
3) sudo rm /etc/X11/xorg.conf
4) sudo apt install nvidia-driver- nvidia-dkms- 
nvidia-settings nvidia-prime
5) reboot

I also have 11-nvidia-prime.conf file at /usr/share/X11/xorg.conf.d
which is generated by ubuntu-drivers-common:

cat /usr/share/X11/xorg.conf.d/11-nvidia-prime.conf

# DO NOT EDIT. AUTOMATICALLY GENERATED BY gpu-manager

Section "OutputClass"
Identifier "Nvidia Prime"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
Option "IgnoreDisplayDevices" "CRT"
Option "PrimaryGPU" "Yes"
ModulePath "/x86_64-linux-gnu/nvidia/xorg"
EndSection

dpkg -l | grep ubuntu-drivers-common
ii  ubuntu-drivers-common 1:0.5.2.2  

https://github.com/tseliot/ubuntu-drivers-
common/blob/bionic/share/hybrid/gpu-manager.c#L1359-L1375

** Attachment added: 
"nvidia-x-server-settings-graphics-ppa-415-hwe-4.18-bionic.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+attachment/5239177/+files/nvidia-x-server-settings-graphics-ppa-415-hwe-4.18-bionic.png

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

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

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 

[Kernel-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69

[Dmitrii Shcherbakov]

nvidia-xconfig -generated xorg.conf looked like this
https://paste.ubuntu.com/p/4hRVzHmbJV/

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

Title:
  Unable to unlock the desktop session: systemd-logind: got pause for
  13:69

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

Bug description:
  When this issue happens, you won't be able to unlock your desktop session (VT 
works fine).
  This happened twice today for me, one is after a suspend, one is just a 
screen lock. Not sure what is the trigger yet.

  Syndrome:
  On the login screen after typing the correct password, you will see a small 
circle keep spinning and that's it. I need to restart my computer to get it 
back to normal.

  
  In the syslog this error message looks fishy:
  Aug  8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' 
failed

  
  This is part of the syslog fetching from a VT after a GUI unlock attempt 
(session 24 is the desktop login attempt):

  Aug  8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 226:0
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: 
Resuming AIGLX clients after VT switch
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
EDID vendor "AUO", prod id 4204
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1590  768 771 777 798 +hsync 
-vsync (47.9 kHz eP)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): 
Modeline "1366x768"x0.0   76.20  1366 1404 1426 1988  768 771 777 798 +hsync 
-vsync (38.3 kHz e)
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:78
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - 
Dell WMI hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:66
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2  - 
Sleep Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:79
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - 
Integrated_Webcam_HD: Integrate: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:68
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4  - AT 
Translated Set 2 keyboard: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:67
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3  - 
Power Button: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:71
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7  - 
AlpsPS/2 ALPS GlidePoint: device is a touchpad
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:72
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: is tagged by udev as: Keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8  - 
DELL Wireless hotkeys: device is a keyboard
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: 
PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is 
disabled.
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver 
cannot change properties on a disabled device
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) 
systemd-logind: got resume for 13:65
  Aug  8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event1  - 
Power Button: is tagged 

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

[Dmitrii Shcherbakov]

apport information

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

Title:
  The last console= argument is not used by the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran into a problem with the console argument handling on a physical
  system with a BMC (Dell R610) and also reproduced the same behavior on
  a QEMU/KVM VM with multiple serial ports.

  The kernel documentation notes that the last entry will be used for 
/dev/console
  https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-tty
  "What:/sys/class/tty/console/active
   Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
   The file supports poll() to detect virtual console switches."

  https://elixir.bootlin.com/linux/v4.15.18/source/kernel/printk/printk.c#L1960
  "The last preferred console added will be used for kernel messages and 
stdin/out/err for init."

  The actual behavior is different and the console specified in the last
  console argument does not become an active one. As a result, SOL
  functionality is not possible to use unless only one ttyS argument
  is specified in the kernel command line arguments. Setting the
  arguments to only contain the right one results in a proper behavior
  and I can see rx counters increasing in /proc/tty/driver/serial for
  the relevant port after I type something via the BMC.

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  journalctl -k | grep ttyS
  Dec 03 21:42:41 ubuntu kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: console [ttyS0] enabled
  Dec 03 21:42:41 ubuntu kernel: 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: tty ttyS3: hash matches

  Full dmesg: http://paste.ubuntu.com/p/bV2pDc4Hdw/

  $ cat /sys/class/tty/console/active
  ttyS0 tty0

  $ sudo cat /proc/tty/driver/serial
  serinfo:1.0 driver revision:
  0: uart:16550A port:03F8 irq:4 tx:78 rx:0 RTS|DTR
  1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD
  2: uart:unknown port:03E8 irq:4
  3: uart:unknown port:02E8 irq:3
  # ...

  ~~~
  GRUB setttings:

  # the ones that override /etc/default/grub
  $ cat /etc/default/grub.d/50-curtin-settings.cfg
  cat: cat: No such file or directory
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 
console=ttyS1,115200"
  # disable grub os prober that might find other OS installs.
  GRUB_DISABLE_OS_PROBER=true
  GRUB_TERMINAL=console

  /etc/default/grub: https://paste.ubuntu.com/p/sdWQrY7JwN/

  # grub.cfg: http://paste.ubuntu.com/p/zKGTqDh6sR/
  # two entries, both with the proper arg and properly sent to the kernel 
cmdline based on /proc/cmdline
  grep ttyS grub.cfg
  linux /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
   linux/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  ~~~

  I managed to reproduce the exact same behavior on a VM with multiple
  8250 serial ports.

  ubuntu@maas-vhost5:~$ cat /sys/class/tty/console/active
  ttyS0

  ubuntu@maas-vhost5:~$ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-39-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  # changed to the following config with only ttyS1 present:
  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux 

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

[Dmitrii Shcherbakov]

apport information

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

Title:
  The last console= argument is not used by the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran into a problem with the console argument handling on a physical
  system with a BMC (Dell R610) and also reproduced the same behavior on
  a QEMU/KVM VM with multiple serial ports.

  The kernel documentation notes that the last entry will be used for 
/dev/console
  https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-tty
  "What:/sys/class/tty/console/active
   Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
   The file supports poll() to detect virtual console switches."

  https://elixir.bootlin.com/linux/v4.15.18/source/kernel/printk/printk.c#L1960
  "The last preferred console added will be used for kernel messages and 
stdin/out/err for init."

  The actual behavior is different and the console specified in the last
  console argument does not become an active one. As a result, SOL
  functionality is not possible to use unless only one ttyS argument
  is specified in the kernel command line arguments. Setting the
  arguments to only contain the right one results in a proper behavior
  and I can see rx counters increasing in /proc/tty/driver/serial for
  the relevant port after I type something via the BMC.

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  journalctl -k | grep ttyS
  Dec 03 21:42:41 ubuntu kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: console [ttyS0] enabled
  Dec 03 21:42:41 ubuntu kernel: 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: tty ttyS3: hash matches

  Full dmesg: http://paste.ubuntu.com/p/bV2pDc4Hdw/

  $ cat /sys/class/tty/console/active
  ttyS0 tty0

  $ sudo cat /proc/tty/driver/serial
  serinfo:1.0 driver revision:
  0: uart:16550A port:03F8 irq:4 tx:78 rx:0 RTS|DTR
  1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD
  2: uart:unknown port:03E8 irq:4
  3: uart:unknown port:02E8 irq:3
  # ...

  ~~~
  GRUB setttings:

  # the ones that override /etc/default/grub
  $ cat /etc/default/grub.d/50-curtin-settings.cfg
  cat: cat: No such file or directory
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 
console=ttyS1,115200"
  # disable grub os prober that might find other OS installs.
  GRUB_DISABLE_OS_PROBER=true
  GRUB_TERMINAL=console

  /etc/default/grub: https://paste.ubuntu.com/p/sdWQrY7JwN/

  # grub.cfg: http://paste.ubuntu.com/p/zKGTqDh6sR/
  # two entries, both with the proper arg and properly sent to the kernel 
cmdline based on /proc/cmdline
  grep ttyS grub.cfg
  linux /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
   linux/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  ~~~

  I managed to reproduce the exact same behavior on a VM with multiple
  8250 serial ports.

  ubuntu@maas-vhost5:~$ cat /sys/class/tty/console/active
  ttyS0

  ubuntu@maas-vhost5:~$ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-39-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  # changed to the following config with only ttyS1 present:
  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux 

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

[Dmitrii Shcherbakov]

apport information

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

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

Title:
  The last console= argument is not used by the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran into a problem with the console argument handling on a physical
  system with a BMC (Dell R610) and also reproduced the same behavior on
  a QEMU/KVM VM with multiple serial ports.

  The kernel documentation notes that the last entry will be used for 
/dev/console
  https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-tty
  "What:/sys/class/tty/console/active
   Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
   The file supports poll() to detect virtual console switches."

  https://elixir.bootlin.com/linux/v4.15.18/source/kernel/printk/printk.c#L1960
  "The last preferred console added will be used for kernel messages and 
stdin/out/err for init."

  The actual behavior is different and the console specified in the last
  console argument does not become an active one. As a result, SOL
  functionality is not possible to use unless only one ttyS argument
  is specified in the kernel command line arguments. Setting the
  arguments to only contain the right one results in a proper behavior
  and I can see rx counters increasing in /proc/tty/driver/serial for
  the relevant port after I type something via the BMC.

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  journalctl -k | grep ttyS
  Dec 03 21:42:41 ubuntu kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: console [ttyS0] enabled
  Dec 03 21:42:41 ubuntu kernel: 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: tty ttyS3: hash matches

  Full dmesg: http://paste.ubuntu.com/p/bV2pDc4Hdw/

  $ cat /sys/class/tty/console/active
  ttyS0 tty0

  $ sudo cat /proc/tty/driver/serial
  serinfo:1.0 driver revision:
  0: uart:16550A port:03F8 irq:4 tx:78 rx:0 RTS|DTR
  1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD
  2: uart:unknown port:03E8 irq:4
  3: uart:unknown port:02E8 irq:3
  # ...

  ~~~
  GRUB setttings:

  # the ones that override /etc/default/grub
  $ cat /etc/default/grub.d/50-curtin-settings.cfg
  cat: cat: No such file or directory
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 
console=ttyS1,115200"
  # disable grub os prober that might find other OS installs.
  GRUB_DISABLE_OS_PROBER=true
  GRUB_TERMINAL=console

  /etc/default/grub: https://paste.ubuntu.com/p/sdWQrY7JwN/

  # grub.cfg: http://paste.ubuntu.com/p/zKGTqDh6sR/
  # two entries, both with the proper arg and properly sent to the kernel 
cmdline based on /proc/cmdline
  grep ttyS grub.cfg
  linux /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
   linux/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  ~~~

  I managed to reproduce the exact same behavior on a VM with multiple
  8250 serial ports.

  ubuntu@maas-vhost5:~$ cat /sys/class/tty/console/active
  ttyS0

  ubuntu@maas-vhost5:~$ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-39-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  # changed to the following config with only ttyS1 present:
  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux 

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

[Dmitrii Shcherbakov]

apport information

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

Title:
  The last console= argument is not used by the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran into a problem with the console argument handling on a physical
  system with a BMC (Dell R610) and also reproduced the same behavior on
  a QEMU/KVM VM with multiple serial ports.

  The kernel documentation notes that the last entry will be used for 
/dev/console
  https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-tty
  "What:/sys/class/tty/console/active
   Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
   The file supports poll() to detect virtual console switches."

  https://elixir.bootlin.com/linux/v4.15.18/source/kernel/printk/printk.c#L1960
  "The last preferred console added will be used for kernel messages and 
stdin/out/err for init."

  The actual behavior is different and the console specified in the last
  console argument does not become an active one. As a result, SOL
  functionality is not possible to use unless only one ttyS argument
  is specified in the kernel command line arguments. Setting the
  arguments to only contain the right one results in a proper behavior
  and I can see rx counters increasing in /proc/tty/driver/serial for
  the relevant port after I type something via the BMC.

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  journalctl -k | grep ttyS
  Dec 03 21:42:41 ubuntu kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: console [ttyS0] enabled
  Dec 03 21:42:41 ubuntu kernel: 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: tty ttyS3: hash matches

  Full dmesg: http://paste.ubuntu.com/p/bV2pDc4Hdw/

  $ cat /sys/class/tty/console/active
  ttyS0 tty0

  $ sudo cat /proc/tty/driver/serial
  serinfo:1.0 driver revision:
  0: uart:16550A port:03F8 irq:4 tx:78 rx:0 RTS|DTR
  1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD
  2: uart:unknown port:03E8 irq:4
  3: uart:unknown port:02E8 irq:3
  # ...

  ~~~
  GRUB setttings:

  # the ones that override /etc/default/grub
  $ cat /etc/default/grub.d/50-curtin-settings.cfg
  cat: cat: No such file or directory
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 
console=ttyS1,115200"
  # disable grub os prober that might find other OS installs.
  GRUB_DISABLE_OS_PROBER=true
  GRUB_TERMINAL=console

  /etc/default/grub: https://paste.ubuntu.com/p/sdWQrY7JwN/

  # grub.cfg: http://paste.ubuntu.com/p/zKGTqDh6sR/
  # two entries, both with the proper arg and properly sent to the kernel 
cmdline based on /proc/cmdline
  grep ttyS grub.cfg
  linux /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
   linux/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  ~~~

  I managed to reproduce the exact same behavior on a VM with multiple
  8250 serial ports.

  ubuntu@maas-vhost5:~$ cat /sys/class/tty/console/active
  ttyS0

  ubuntu@maas-vhost5:~$ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-39-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  # changed to the following config with only ttyS1 present:
  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux 

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

[Dmitrii Shcherbakov]

apport information

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

Title:
  The last console= argument is not used by the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran into a problem with the console argument handling on a physical
  system with a BMC (Dell R610) and also reproduced the same behavior on
  a QEMU/KVM VM with multiple serial ports.

  The kernel documentation notes that the last entry will be used for 
/dev/console
  https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-tty
  "What:/sys/class/tty/console/active
   Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
   The file supports poll() to detect virtual console switches."

  https://elixir.bootlin.com/linux/v4.15.18/source/kernel/printk/printk.c#L1960
  "The last preferred console added will be used for kernel messages and 
stdin/out/err for init."

  The actual behavior is different and the console specified in the last
  console argument does not become an active one. As a result, SOL
  functionality is not possible to use unless only one ttyS argument
  is specified in the kernel command line arguments. Setting the
  arguments to only contain the right one results in a proper behavior
  and I can see rx counters increasing in /proc/tty/driver/serial for
  the relevant port after I type something via the BMC.

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  journalctl -k | grep ttyS
  Dec 03 21:42:41 ubuntu kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: console [ttyS0] enabled
  Dec 03 21:42:41 ubuntu kernel: 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: tty ttyS3: hash matches

  Full dmesg: http://paste.ubuntu.com/p/bV2pDc4Hdw/

  $ cat /sys/class/tty/console/active
  ttyS0 tty0

  $ sudo cat /proc/tty/driver/serial
  serinfo:1.0 driver revision:
  0: uart:16550A port:03F8 irq:4 tx:78 rx:0 RTS|DTR
  1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD
  2: uart:unknown port:03E8 irq:4
  3: uart:unknown port:02E8 irq:3
  # ...

  ~~~
  GRUB setttings:

  # the ones that override /etc/default/grub
  $ cat /etc/default/grub.d/50-curtin-settings.cfg
  cat: cat: No such file or directory
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 
console=ttyS1,115200"
  # disable grub os prober that might find other OS installs.
  GRUB_DISABLE_OS_PROBER=true
  GRUB_TERMINAL=console

  /etc/default/grub: https://paste.ubuntu.com/p/sdWQrY7JwN/

  # grub.cfg: http://paste.ubuntu.com/p/zKGTqDh6sR/
  # two entries, both with the proper arg and properly sent to the kernel 
cmdline based on /proc/cmdline
  grep ttyS grub.cfg
  linux /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
   linux/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  ~~~

  I managed to reproduce the exact same behavior on a VM with multiple
  8250 serial ports.

  ubuntu@maas-vhost5:~$ cat /sys/class/tty/console/active
  ttyS0

  ubuntu@maas-vhost5:~$ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-39-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  # changed to the following config with only ttyS1 present:
  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux 

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

[Dmitrii Shcherbakov]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1807140/+attachment/5219758/+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/1807140

Title:
  The last console= argument is not used by the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran into a problem with the console argument handling on a physical
  system with a BMC (Dell R610) and also reproduced the same behavior on
  a QEMU/KVM VM with multiple serial ports.

  The kernel documentation notes that the last entry will be used for 
/dev/console
  https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-tty
  "What:/sys/class/tty/console/active
   Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
   The file supports poll() to detect virtual console switches."

  https://elixir.bootlin.com/linux/v4.15.18/source/kernel/printk/printk.c#L1960
  "The last preferred console added will be used for kernel messages and 
stdin/out/err for init."

  The actual behavior is different and the console specified in the last
  console argument does not become an active one. As a result, SOL
  functionality is not possible to use unless only one ttyS argument
  is specified in the kernel command line arguments. Setting the
  arguments to only contain the right one results in a proper behavior
  and I can see rx counters increasing in /proc/tty/driver/serial for
  the relevant port after I type something via the BMC.

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  journalctl -k | grep ttyS
  Dec 03 21:42:41 ubuntu kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: console [ttyS0] enabled
  Dec 03 21:42:41 ubuntu kernel: 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: tty ttyS3: hash matches

  Full dmesg: http://paste.ubuntu.com/p/bV2pDc4Hdw/

  $ cat /sys/class/tty/console/active
  ttyS0 tty0

  $ sudo cat /proc/tty/driver/serial
  serinfo:1.0 driver revision:
  0: uart:16550A port:03F8 irq:4 tx:78 rx:0 RTS|DTR
  1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD
  2: uart:unknown port:03E8 irq:4
  3: uart:unknown port:02E8 irq:3
  # ...

  ~~~
  GRUB setttings:

  # the ones that override /etc/default/grub
  $ cat /etc/default/grub.d/50-curtin-settings.cfg
  cat: cat: No such file or directory
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 
console=ttyS1,115200"
  # disable grub os prober that might find other OS installs.
  GRUB_DISABLE_OS_PROBER=true
  GRUB_TERMINAL=console

  /etc/default/grub: https://paste.ubuntu.com/p/sdWQrY7JwN/

  # grub.cfg: http://paste.ubuntu.com/p/zKGTqDh6sR/
  # two entries, both with the proper arg and properly sent to the kernel 
cmdline based on /proc/cmdline
  grep ttyS grub.cfg
  linux /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
   linux/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  ~~~

  I managed to reproduce the exact same behavior on a VM with multiple
  8250 serial ports.

  ubuntu@maas-vhost5:~$ cat /sys/class/tty/console/active
  ttyS0

  ubuntu@maas-vhost5:~$ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-39-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  # changed to the following config with only ttyS1 present:
  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux 

[Kernel-packages] [Bug 1807140] Re: The last console= argument is not used by the kernel

[Dmitrii Shcherbakov]

The information above is from a VM with a reproducer.

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

Title:
  The last console= argument is not used by the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran into a problem with the console argument handling on a physical
  system with a BMC (Dell R610) and also reproduced the same behavior on
  a QEMU/KVM VM with multiple serial ports.

  The kernel documentation notes that the last entry will be used for 
/dev/console
  https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-tty
  "What:/sys/class/tty/console/active
   Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
   The file supports poll() to detect virtual console switches."

  https://elixir.bootlin.com/linux/v4.15.18/source/kernel/printk/printk.c#L1960
  "The last preferred console added will be used for kernel messages and 
stdin/out/err for init."

  The actual behavior is different and the console specified in the last
  console argument does not become an active one. As a result, SOL
  functionality is not possible to use unless only one ttyS argument
  is specified in the kernel command line arguments. Setting the
  arguments to only contain the right one results in a proper behavior
  and I can see rx counters increasing in /proc/tty/driver/serial for
  the relevant port after I type something via the BMC.

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  journalctl -k | grep ttyS
  Dec 03 21:42:41 ubuntu kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: console [ttyS0] enabled
  Dec 03 21:42:41 ubuntu kernel: 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: tty ttyS3: hash matches

  Full dmesg: http://paste.ubuntu.com/p/bV2pDc4Hdw/

  $ cat /sys/class/tty/console/active
  ttyS0 tty0

  $ sudo cat /proc/tty/driver/serial
  serinfo:1.0 driver revision:
  0: uart:16550A port:03F8 irq:4 tx:78 rx:0 RTS|DTR
  1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD
  2: uart:unknown port:03E8 irq:4
  3: uart:unknown port:02E8 irq:3
  # ...

  ~~~
  GRUB setttings:

  # the ones that override /etc/default/grub
  $ cat /etc/default/grub.d/50-curtin-settings.cfg
  cat: cat: No such file or directory
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 
console=ttyS1,115200"
  # disable grub os prober that might find other OS installs.
  GRUB_DISABLE_OS_PROBER=true
  GRUB_TERMINAL=console

  /etc/default/grub: https://paste.ubuntu.com/p/sdWQrY7JwN/

  # grub.cfg: http://paste.ubuntu.com/p/zKGTqDh6sR/
  # two entries, both with the proper arg and properly sent to the kernel 
cmdline based on /proc/cmdline
  grep ttyS grub.cfg
  linux /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
   linux/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  ~~~

  I managed to reproduce the exact same behavior on a VM with multiple
  8250 serial ports.

  ubuntu@maas-vhost5:~$ cat /sys/class/tty/console/active
  ttyS0

  ubuntu@maas-vhost5:~$ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-39-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  # changed to the following config with only ttyS1 present:
  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux /boot/vmlinuz-4.15.0-42-generic 

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

[Dmitrii Shcherbakov]

apport information

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

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

Title:
  The last console= argument is not used by the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran into a problem with the console argument handling on a physical
  system with a BMC (Dell R610) and also reproduced the same behavior on
  a QEMU/KVM VM with multiple serial ports.

  The kernel documentation notes that the last entry will be used for 
/dev/console
  https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-tty
  "What:/sys/class/tty/console/active
   Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
   The file supports poll() to detect virtual console switches."

  https://elixir.bootlin.com/linux/v4.15.18/source/kernel/printk/printk.c#L1960
  "The last preferred console added will be used for kernel messages and 
stdin/out/err for init."

  The actual behavior is different and the console specified in the last
  console argument does not become an active one. As a result, SOL
  functionality is not possible to use unless only one ttyS argument
  is specified in the kernel command line arguments. Setting the
  arguments to only contain the right one results in a proper behavior
  and I can see rx counters increasing in /proc/tty/driver/serial for
  the relevant port after I type something via the BMC.

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  journalctl -k | grep ttyS
  Dec 03 21:42:41 ubuntu kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: console [ttyS0] enabled
  Dec 03 21:42:41 ubuntu kernel: 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: tty ttyS3: hash matches

  Full dmesg: http://paste.ubuntu.com/p/bV2pDc4Hdw/

  $ cat /sys/class/tty/console/active
  ttyS0 tty0

  $ sudo cat /proc/tty/driver/serial
  serinfo:1.0 driver revision:
  0: uart:16550A port:03F8 irq:4 tx:78 rx:0 RTS|DTR
  1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD
  2: uart:unknown port:03E8 irq:4
  3: uart:unknown port:02E8 irq:3
  # ...

  ~~~
  GRUB setttings:

  # the ones that override /etc/default/grub
  $ cat /etc/default/grub.d/50-curtin-settings.cfg
  cat: cat: No such file or directory
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 
console=ttyS1,115200"
  # disable grub os prober that might find other OS installs.
  GRUB_DISABLE_OS_PROBER=true
  GRUB_TERMINAL=console

  /etc/default/grub: https://paste.ubuntu.com/p/sdWQrY7JwN/

  # grub.cfg: http://paste.ubuntu.com/p/zKGTqDh6sR/
  # two entries, both with the proper arg and properly sent to the kernel 
cmdline based on /proc/cmdline
  grep ttyS grub.cfg
  linux /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
   linux/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  ~~~

  I managed to reproduce the exact same behavior on a VM with multiple
  8250 serial ports.

  ubuntu@maas-vhost5:~$ cat /sys/class/tty/console/active
  ttyS0

  ubuntu@maas-vhost5:~$ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-39-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  # changed to the following config with only ttyS1 present:
  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux 

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

[Dmitrii Shcherbakov]

apport information

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

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

Title:
  The last console= argument is not used by the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran into a problem with the console argument handling on a physical
  system with a BMC (Dell R610) and also reproduced the same behavior on
  a QEMU/KVM VM with multiple serial ports.

  The kernel documentation notes that the last entry will be used for 
/dev/console
  https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-tty
  "What:/sys/class/tty/console/active
   Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
   The file supports poll() to detect virtual console switches."

  https://elixir.bootlin.com/linux/v4.15.18/source/kernel/printk/printk.c#L1960
  "The last preferred console added will be used for kernel messages and 
stdin/out/err for init."

  The actual behavior is different and the console specified in the last
  console argument does not become an active one. As a result, SOL
  functionality is not possible to use unless only one ttyS argument
  is specified in the kernel command line arguments. Setting the
  arguments to only contain the right one results in a proper behavior
  and I can see rx counters increasing in /proc/tty/driver/serial for
  the relevant port after I type something via the BMC.

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  journalctl -k | grep ttyS
  Dec 03 21:42:41 ubuntu kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: console [ttyS0] enabled
  Dec 03 21:42:41 ubuntu kernel: 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: tty ttyS3: hash matches

  Full dmesg: http://paste.ubuntu.com/p/bV2pDc4Hdw/

  $ cat /sys/class/tty/console/active
  ttyS0 tty0

  $ sudo cat /proc/tty/driver/serial
  serinfo:1.0 driver revision:
  0: uart:16550A port:03F8 irq:4 tx:78 rx:0 RTS|DTR
  1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD
  2: uart:unknown port:03E8 irq:4
  3: uart:unknown port:02E8 irq:3
  # ...

  ~~~
  GRUB setttings:

  # the ones that override /etc/default/grub
  $ cat /etc/default/grub.d/50-curtin-settings.cfg
  cat: cat: No such file or directory
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 
console=ttyS1,115200"
  # disable grub os prober that might find other OS installs.
  GRUB_DISABLE_OS_PROBER=true
  GRUB_TERMINAL=console

  /etc/default/grub: https://paste.ubuntu.com/p/sdWQrY7JwN/

  # grub.cfg: http://paste.ubuntu.com/p/zKGTqDh6sR/
  # two entries, both with the proper arg and properly sent to the kernel 
cmdline based on /proc/cmdline
  grep ttyS grub.cfg
  linux /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
   linux/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  ~~~

  I managed to reproduce the exact same behavior on a VM with multiple
  8250 serial ports.

  ubuntu@maas-vhost5:~$ cat /sys/class/tty/console/active
  ttyS0

  ubuntu@maas-vhost5:~$ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-39-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  # changed to the following config with only ttyS1 present:
  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux 

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

[Dmitrii Shcherbakov]

apport information

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

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

Title:
  The last console= argument is not used by the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran into a problem with the console argument handling on a physical
  system with a BMC (Dell R610) and also reproduced the same behavior on
  a QEMU/KVM VM with multiple serial ports.

  The kernel documentation notes that the last entry will be used for 
/dev/console
  https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-tty
  "What:/sys/class/tty/console/active
   Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
   The file supports poll() to detect virtual console switches."

  https://elixir.bootlin.com/linux/v4.15.18/source/kernel/printk/printk.c#L1960
  "The last preferred console added will be used for kernel messages and 
stdin/out/err for init."

  The actual behavior is different and the console specified in the last
  console argument does not become an active one. As a result, SOL
  functionality is not possible to use unless only one ttyS argument
  is specified in the kernel command line arguments. Setting the
  arguments to only contain the right one results in a proper behavior
  and I can see rx counters increasing in /proc/tty/driver/serial for
  the relevant port after I type something via the BMC.

  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  journalctl -k | grep ttyS
  Dec 03 21:42:41 ubuntu kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: console [ttyS0] enabled
  Dec 03 21:42:41 ubuntu kernel: 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: tty ttyS3: hash matches

  Full dmesg: http://paste.ubuntu.com/p/bV2pDc4Hdw/

  $ cat /sys/class/tty/console/active
  ttyS0 tty0

  $ sudo cat /proc/tty/driver/serial
  serinfo:1.0 driver revision:
  0: uart:16550A port:03F8 irq:4 tx:78 rx:0 RTS|DTR
  1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD
  2: uart:unknown port:03E8 irq:4
  3: uart:unknown port:02E8 irq:3
  # ...

  ~~~
  GRUB setttings:

  # the ones that override /etc/default/grub
  $ cat /etc/default/grub.d/50-curtin-settings.cfg
  cat: cat: No such file or directory
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 
console=ttyS1,115200"
  # disable grub os prober that might find other OS installs.
  GRUB_DISABLE_OS_PROBER=true
  GRUB_TERMINAL=console

  /etc/default/grub: https://paste.ubuntu.com/p/sdWQrY7JwN/

  # grub.cfg: http://paste.ubuntu.com/p/zKGTqDh6sR/
  # two entries, both with the proper arg and properly sent to the kernel 
cmdline based on /proc/cmdline
  grep ttyS grub.cfg
  linux /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
   linux/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200

  ~~~

  I managed to reproduce the exact same behavior on a VM with multiple
  8250 serial ports.

  ubuntu@maas-vhost5:~$ cat /sys/class/tty/console/active
  ttyS0

  ubuntu@maas-vhost5:~$ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-39-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

  # changed to the following config with only ttyS1 present:
  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux 

[Kernel-packages] [Bug 1807140] Re: The last console= argument is not used by the kernel

[Dmitrii Shcherbakov]

apport information

** Tags added: apport-collected uec-images

** Description changed:

  I ran into a problem with the console argument handling on a physical
  system with a BMC (Dell R610) and also reproduced the same behavior on a
  QEMU/KVM VM with multiple serial ports.
  
  The kernel documentation notes that the last entry will be used for 
/dev/console
  https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-tty
  "What:/sys/class/tty/console/active
   Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
   The file supports poll() to detect virtual console switches."
  
  https://elixir.bootlin.com/linux/v4.15.18/source/kernel/printk/printk.c#L1960
  "The last preferred console added will be used for kernel messages and 
stdin/out/err for init."
  
  The actual behavior is different and the console specified in the last
  console argument does not become an active one. As a result, SOL
  functionality is not possible to use unless only one ttyS argument is
  specified in the kernel command line arguments. Setting the arguments to
  only contain the right one results in a proper behavior and I can see rx
  counters increasing in /proc/tty/driver/serial for the relevant port
  after I type something via the BMC.
  
  $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  
  journalctl -k | grep ttyS
  Dec 03 21:42:41 ubuntu kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: console [ttyS0] enabled
  Dec 03 21:42:41 ubuntu kernel: 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: tty ttyS3: hash matches
  
  Full dmesg: http://paste.ubuntu.com/p/bV2pDc4Hdw/
  
  $ cat /sys/class/tty/console/active
  ttyS0 tty0
  
  $ sudo cat /proc/tty/driver/serial
  serinfo:1.0 driver revision:
  0: uart:16550A port:03F8 irq:4 tx:78 rx:0 RTS|DTR
  1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD
  2: uart:unknown port:03E8 irq:4
  3: uart:unknown port:02E8 irq:3
  # ...
  
  ~~~
  GRUB setttings:
  
  # the ones that override /etc/default/grub
  $ cat /etc/default/grub.d/50-curtin-settings.cfg
  cat: cat: No such file or directory
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 
console=ttyS1,115200"
  # disable grub os prober that might find other OS installs.
  GRUB_DISABLE_OS_PROBER=true
  GRUB_TERMINAL=console
  
  /etc/default/grub: https://paste.ubuntu.com/p/sdWQrY7JwN/
  
  # grub.cfg: http://paste.ubuntu.com/p/zKGTqDh6sR/
  # two entries, both with the proper arg and properly sent to the kernel 
cmdline based on /proc/cmdline
  grep ttyS grub.cfg
  linux /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
   linux/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  
  ~~~
  
  I managed to reproduce the exact same behavior on a VM with multiple
  8250 serial ports.
  
  ubuntu@maas-vhost5:~$ cat /sys/class/tty/console/active
  ttyS0
  
  ubuntu@maas-vhost5:~$ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
  
  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-39-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
  
  # changed to the following config with only ttyS1 present:
  ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg
  linux /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS1,115200
   linux/boot/vmlinuz-4.15.0-39-generic 

[Kernel-packages] [Bug 1807140] Re: The last console= argument is not used by the kernel

[Dmitrii Shcherbakov]

** Description changed:

  I ran into a problem with the console argument handling on a physical
  system with a BMC (Dell R610) and also reproduced the same behavior on a
  QEMU/KVM VM with multiple serial ports.
  
- The kernel documentation notes that the last entry will 
+ The kernel documentation notes that the last entry will be used for 
/dev/console
  https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-tty
  "What:/sys/class/tty/console/active
-  Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
-  The file supports poll() to detect virtual console switches."
+  Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
+  The file supports poll() to detect virtual console switches."
  
  https://elixir.bootlin.com/linux/v4.15.18/source/kernel/printk/printk.c#L1960
  "The last preferred console added will be used for kernel messages and 
stdin/out/err for init."
  
  The actual behavior is different and the console specified in the last
  console argument does not become an active one. As a result, SOL
  functionality is not possible to use unless only one ttyS argument is
  specified in the kernel command line arguments. Setting the arguments to
  only contain the right one results in a proper behavior and I can see rx
  counters increasing in /proc/tty/driver/serial for the relevant port
  after I type something via the BMC.
  
- $ cat /proc/cmdline 
+ $ cat /proc/cmdline
  BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  
  journalctl -k | grep ttyS
  Dec 03 21:42:41 ubuntu kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  Dec 03 21:42:41 ubuntu kernel: console [ttyS0] enabled
  Dec 03 21:42:41 ubuntu kernel: 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud 
= 115200) is a 16550A
  Dec 03 21:42:41 ubuntu kernel: tty ttyS3: hash matches
  
  Full dmesg: http://paste.ubuntu.com/p/bV2pDc4Hdw/
  
  $ cat /sys/class/tty/console/active
  ttyS0 tty0
  
  $ sudo cat /proc/tty/driver/serial
  serinfo:1.0 driver revision:
  0: uart:16550A port:03F8 irq:4 tx:78 rx:0 RTS|DTR
  1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD
  2: uart:unknown port:03E8 irq:4
  3: uart:unknown port:02E8 irq:3
  # ...
  
- 
  ~~~
  GRUB setttings:
  
  # the ones that override /etc/default/grub
  $ cat /etc/default/grub.d/50-curtin-settings.cfg
  cat: cat: No such file or directory
  GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 
console=ttyS1,115200"
  # disable grub os prober that might find other OS installs.
  GRUB_DISABLE_OS_PROBER=true
  GRUB_TERMINAL=console
  
  /etc/default/grub: https://paste.ubuntu.com/p/sdWQrY7JwN/
  
  # grub.cfg: http://paste.ubuntu.com/p/zKGTqDh6sR/
  # two entries, both with the proper arg and properly sent to the kernel 
cmdline based on /proc/cmdline
- grep ttyS grub.cfg 
- linux /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
-   linux   /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
- 
+ grep ttyS grub.cfg
+ linux /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
+  linux/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
  
  ~~~
  
- 
- I managed to reproduce the exact same behavior on a VM with multiple 8250 
serial ports.
+ I managed to reproduce the exact same behavior on a VM with multiple
+ 8250 serial ports.
  
  ubuntu@maas-vhost5:~$ cat /sys/class/tty/console/active
  ttyS0
  
- ubuntu@maas-vhost5:~$ cat /proc/cmdline 
+ ubuntu@maas-vhost5:~$ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
  
- ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg 
- linux /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
-   linux   /boot/vmlinuz-4.15.0-42-generic 

[Kernel-packages] [Bug 1807140] [NEW] The last console= argument is not used by the kernel

[Dmitrii Shcherbakov]

Public bug reported:

I ran into a problem with the console argument handling on a physical
system with a BMC (Dell R610) and also reproduced the same behavior on a
QEMU/KVM VM with multiple serial ports.

The kernel documentation notes that the last entry will 
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-tty
"What:/sys/class/tty/console/active
 Shows the list of currently configured console devices, like 'tty1 
ttyS0'. The last entry in the file is the active device connected to 
/dev/console.
 The file supports poll() to detect virtual console switches."

https://elixir.bootlin.com/linux/v4.15.18/source/kernel/printk/printk.c#L1960
"The last preferred console added will be used for kernel messages and 
stdin/out/err for init."

The actual behavior is different and the console specified in the last
console argument does not become an active one. As a result, SOL
functionality is not possible to use unless only one ttyS argument is
specified in the kernel command line arguments. Setting the arguments to
only contain the right one results in a proper behavior and I can see rx
counters increasing in /proc/tty/driver/serial for the relevant port
after I type something via the BMC.

$ cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200

journalctl -k | grep ttyS
Dec 03 21:42:41 ubuntu kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
Dec 03 21:42:41 ubuntu kernel: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200
Dec 03 21:42:41 ubuntu kernel: console [ttyS0] enabled
Dec 03 21:42:41 ubuntu kernel: 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 
115200) is a 16550A
Dec 03 21:42:41 ubuntu kernel: 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 
115200) is a 16550A
Dec 03 21:42:41 ubuntu kernel: tty ttyS3: hash matches

Full dmesg: http://paste.ubuntu.com/p/bV2pDc4Hdw/

$ cat /sys/class/tty/console/active
ttyS0 tty0

$ sudo cat /proc/tty/driver/serial
serinfo:1.0 driver revision:
0: uart:16550A port:03F8 irq:4 tx:78 rx:0 RTS|DTR
1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD
2: uart:unknown port:03E8 irq:4
3: uart:unknown port:02E8 irq:3
# ...


~~~
GRUB setttings:

# the ones that override /etc/default/grub
$ cat /etc/default/grub.d/50-curtin-settings.cfg
cat: cat: No such file or directory
GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200 
console=ttyS1,115200"
# disable grub os prober that might find other OS installs.
GRUB_DISABLE_OS_PROBER=true
GRUB_TERMINAL=console

/etc/default/grub: https://paste.ubuntu.com/p/sdWQrY7JwN/

# grub.cfg: http://paste.ubuntu.com/p/zKGTqDh6sR/
# two entries, both with the proper arg and properly sent to the kernel cmdline 
based on /proc/cmdline
grep ttyS grub.cfg 
linux   /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200
linux   /vmlinuz-4.15.0-42-generic 
root=UUID=580a3c58-1040-4c7d-b94f-93230874caf5 ro  console=tty0 
console=ttyS0,115200 console=ttyS1,115200


~~~


I managed to reproduce the exact same behavior on a VM with multiple 8250 
serial ports.

ubuntu@maas-vhost5:~$ cat /sys/class/tty/console/active
ttyS0

ubuntu@maas-vhost5:~$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg 
linux   /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
linux   /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200
linux   /boot/vmlinuz-4.15.0-39-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS0,115200 
console=ttyS2,115200 console=ttyS1,115200

# changed to the following config with only ttyS1 present:
ubuntu@maas-vhost5:~$ grep -RP ttyS /boot/grub/grub.cfg 
linux   /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS1,115200
linux   /boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS1,115200
linux   /boot/vmlinuz-4.15.0-39-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro  console=ttyS1,115200

# 1 tty passed only
ubuntu@maas-vhost5:~$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=a60217c2-6752-4c69-afb9-55f86a2b6c1d ro console=ttyS1,115200

# now it's shown as active

[Kernel-packages] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64

[Dmitrii Shcherbakov]

Got similar behavior with windows server 2012r2 VMs.

Environment:

uname -a
Linux ubuntu-q87 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

ii  linux-image-4.13.0-36-generic
4.13.0-36.40~16.04.1   amd64
Linux kernel image for version 4.13.0 on 64 bit x86 SMP

apt policy qemu
qemu:
  Installed: (none)
  Candidate: 1:2.11+dfsg-1ubuntu5~cloud0
  Version table:
 1:2.11+dfsg-1ubuntu5~cloud0 500

Windows VMs error out and create a memory dump:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0109
(0xa3a01f5891f186c5, 0xb3b72bdee47188a0, 0x0320,
0x0017). A dump was saved in: C:\Windows\MEMORY.DMP. Report
Id: 033018-31234-01.

Based on microsoft docs:

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x109---critical-structure-corruption
CRITICAL_STRUCTURE_CORRUPTION Parameters
Parameter  Description
1 Reserved
2 Reserved
3 Reserved
4 The type of the corrupted region. (See the following table later on this 
page.)

...
0x17 Local APIC modification <--- this


Which is the same as with other reports out there:

https://www.spinics.net/lists/kvm/msg159977.html
https://forum.proxmox.com/threads/new-windows-vm-keeps-dying.39145/#post-193639


>From what I see the change was backported but there was no new build yet.
 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/arch/x86/kvm/x86.c?h=hwe=78d2542b88d16

See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738972

I suggest this is marked as a duplicate to 1738972

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

Title:
  Memory corruption in Windows 10 guest / amd64

Status in QEMU:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Win 10 Pro x64 guest inside a qemu/kvm running on an Arch x86_64 
host. The VM has a physical GPU passed through, as well as the physical USB 
controllers, as well as a dedicated SSD attached via SATA; you can find the 
complete libvirt xml here: https://pastebin.com/U1ZAXBNg
  I built qemu from source using the qemu-minimal-git AUR package; you can find 
the build script here: 
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=qemu-minimal-git (if you 
aren't familiar with Arch, this is essentially a bash script where build() and 
package() are run to build the files, and then install them into the $pkgdir to 
later tar them up.)

  Starting with qemu v2.10.0, Windows crashes randomly with a bluescreen
  about CRITICAL_STRUCTURE_CORRUPTION. I also tested the git heads
  f90ea7ba7c, 861cd431c9 and e822e81e35, before I went back to v2.9.0,
  which is running stable for over 50 hours right now.

  During my tests I found that locking the memory pages alleviates the
  problem somewhat, but never completely avoids it. However, with the
  crashes occuring randomly, that could as well be false conclusions; I
  had crashes within minutes after boot with that too.

  I will now start `git bisect`ing; if you have any other suggestions on
  what I could try or possible patches feel free to leave them with me.

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

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

[Kernel-packages] [Bug 1738972] Re: [A] KVM Windows BSOD on 4.13.x

[Dmitrii Shcherbakov]

Dup:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728256
https://bugs.launchpad.net/qemu/+bug/1728256/comments/11

This affects other guests like W2k12r2 and Windows 10 as well.

** Tags added: cpe-onsite

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

Title:
  [A] KVM Windows BSOD on 4.13.x

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

Bug description:
  == SRU Justification ==

  Impact: Windows 2016 and 10 VMs running in Qemu VMs using KVM trigger
  BSODs under certain memory conditions

  Fix: Single follow-up upstream cherry pick which fixes the problem.

  Regression Potential: Merged in 4.15 and 4.14.6, tested by multiple
  affected users.

  ---

  see https://marc.info/?l=linux-kernel=151203441531472=2 for the
  long writeup

  58582f04bc87b9d8d848d9163ce3355dd6f00602 is the cherry-pick in 4.14-6 (only 
context changes outside of the actual diff)
  b1394e745b9453dcb5b0671c205b770e87dedb87 is the fix as applied in 4.15-rc3

  I'll send the SRU patch as well.

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

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

[Kernel-packages] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64

[Dmitrii Shcherbakov]

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

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

Title:
  Memory corruption in Windows 10 guest / amd64

Status in QEMU:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Win 10 Pro x64 guest inside a qemu/kvm running on an Arch x86_64 
host. The VM has a physical GPU passed through, as well as the physical USB 
controllers, as well as a dedicated SSD attached via SATA; you can find the 
complete libvirt xml here: https://pastebin.com/U1ZAXBNg
  I built qemu from source using the qemu-minimal-git AUR package; you can find 
the build script here: 
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=qemu-minimal-git (if you 
aren't familiar with Arch, this is essentially a bash script where build() and 
package() are run to build the files, and then install them into the $pkgdir to 
later tar them up.)

  Starting with qemu v2.10.0, Windows crashes randomly with a bluescreen
  about CRITICAL_STRUCTURE_CORRUPTION. I also tested the git heads
  f90ea7ba7c, 861cd431c9 and e822e81e35, before I went back to v2.9.0,
  which is running stable for over 50 hours right now.

  During my tests I found that locking the memory pages alleviates the
  problem somewhat, but never completely avoids it. However, with the
  crashes occuring randomly, that could as well be false conclusions; I
  had crashes within minutes after boot with that too.

  I will now start `git bisect`ing; if you have any other suggestions on
  what I could try or possible patches feel free to leave them with me.

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

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

[Kernel-packages] [Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing

[Dmitrii Shcherbakov]

John,

Interfaces of a host carry enough information to be used to make routing
decisions - that's the core idea of host and router-side VRF
implementations. Network spaces as of now do not help you to solve
routing problems in any way unless you have one big L2 network and
"routing" is done without routers: via ARP/NDP in a single broadcast
domain.

Static routes are not flexible enough and are a workaround for the lack
of VRF support. They require many additional steps from a deployer's
perspective to worry about: one should just take a set of VLANs and
subnets to configure in MAAS and assign them to a network space. With a
default gateway per subnet there is always a next hop to delegate a
routing decision to for a given network space from a host's perspective.
Charms and potentially applications do need to be VRF-aware (discussed
above on how).

BGP on a host, while feasible in some scenarios, is not always doable in
practice: not every network and/or security department will give you an
ability to deploy something and set up peering with their BGP-enabled
routers.

I'd be happy to discuss scenarios in-depth here or out of band but the
idea is that Network Spaces need to learn how to assist with Routing and
Forwarding parts - currently they solve only end-end discovery via
relation data.

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

Title:
  VRF support to solve routing problems associated with multi-homing

Status in juju:
  Incomplete
Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem description:

  * a host is multi-homed if it has multiple network interfaces with L3
  addresses configured (physical or virtual interfaces, natural to
  OpenStack regardless of IPv4/IPv6 and IPv6 in general);

  (see 3.3.4  Local Multihoming
  https://tools.ietf.org/html/rfc1122#page-60 and 3.3.4.2  Multihoming
  Requirements)

  * if all hosts that need to participate in L3 communication are
  located on the same L2 network there is no need for a routing device
  to be present. ARP/NDP and auto-created directly connected routes are
  enough;

  * multi-homing with hosts located on different L2 networks requires more 
intelligent routing:
    - "directly connected" routes are no longer enough to talk to all relevant 
hosts in the same network space;
    - a default gateway in the main routing table may not be the correct 
routing device that knows where to forward traffic (management network traffic 
goes to a management switch and router, other traffic goes to L3 ToR switch but 
may go via different bonds);
    - even if a default gateway knows where to forward traffic, it may not be 
the intended physical path (storage replication traffic must go through a 
specific outgoing interface, not the same interface as storage access traffic 
although both interfaces are connected to the same ToR);
    - there is no longer a single "default gateway" as applications need either 
per-logical-direction routers or to become routers themselves (if destination 
== X, forward to next-hop Y). Leaf-spine architecture is a good example of how 
multiple L2 networks force you to use spaces that have VLANs in different 
switch fabrics => one or more hops between hosts with interfaces associated 
with the same network space;
    - while network spaces implicitly require L3 reachability between each host 
that has a NIC associated with a network space, the current definition does not 
mention routing infrastructure required for that. For a single L2 this problem 
is hidden by directly connected routes, for multi-L2, no solution is provided 
or discussed;

  * existing solutions to multi-homing require routing table management
  on a given host: complex static routing rules, dynamic routing (e.g.
  running an OSPF or BGP daemon on a host);

  * using static routes is rigid and requires network planning (i.e.
  working with network engineers which may have varying degrees of
  experience, doing VLSM planning etc.);

  * using dynamic routing requires a broader integration into an
  organization's L3 network infrastructure. Routing can be implemented
  differently across different organizations and it is a security and
  operational burden to integrate with a company's routing
  infrastructure.

  Summary: a mechanism is needed to associate an interface with a
  forwarding table (FIB) which has its own default gateway and make an
  application with a listen(2)ing socket(2) return connected sockets
  associated with different FIBs. In other words, applications need to
  implicitly get source/destination-based routing capabilities without
  the need to use static routing schemes or dynamic routing and with
  minimum or no modifications to the applications themselves.

  Goals:

  * avoid turning individual hosts into routers;
  * avoid complex static rules;
  * better 

[Kernel-packages] [Bug 1734243] Re: Intel 9260/9462/9560 firmware support

[Dmitrii Shcherbakov]

One additional detail. Even on 4.15 "Unhandled alg" can be reproduced
occasionally after disconnecting and reconnecting the adapter to an STA:

дек 22 22:12:45 blade kernel: iwlwifi :3b:00.0: Unhandled alg: 0x707
дек 22 22:12:45 blade kernel: iwlwifi :3b:00.0: Unhandled alg: 0x707
дек 22 22:12:45 blade kernel: iwlwifi :3b:00.0: No association and the time 
event is over already...

Sometimes there is only one message, sometimes two at the same time and
sometimes no message at all.

Seems to be coming from here:
http://elixir.free-electrons.com/linux/v4.15-rc4/source/drivers/net/wireless/intel/iwlwifi/mvm/rx.c#L197

Doesn't affect connectivity though and the card comes up and
transmits/receives even after 10 consecutive reconnects.

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

Title:
  Intel 9260/9462/9560 firmware support

Status in HWE Next:
  New
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 Zesty:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification
  [Impact]
  Intel 9260/9462/9560 require new firmwares to enable them.

  [ 7.492326] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-33.ucode failed with error -2
  [ 7.492349] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-32.ucode failed with error -2
  [ 7.492362] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-31.ucode failed with error -2
  [ 7.492375] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-30.ucode failed with error -2
  [ 7.492378] iwlwifi :00:0c.0: no suitable firmware found!

  For v4.13 kernel, it uses firmware version 33, so we only need this.

  commit c4276b65390d32d33c8263a7e3c8be0db8cccad4 (tag: 
refs/tags/iwlwifi-fw-2017-11-03)
  Author: Luca Coelho 
  Date:   Fri Oct 13 14:22:26 2017 +0300

  iwlwifi: add firmware version 33 for new 9000 series

  Build number: WFFW53774_R30_FW610294

  Revision number: 610294

  Signed-off-by: Luca Coelho 

  [Test Case]
  After applying the firmwares, confirm the 9260/9560 can connect to 6 
different APs(bg/n/ac * open/wap)

  [Regression Potential]
  There is no regression for the new devices and new firmwares.

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

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

[Kernel-packages] [Bug 1734243] Re: Intel 9260/9462/9560 firmware support

[Dmitrii Shcherbakov]

Tested 9260NGW with different kernels (-33 for 4.13, -34 for 4.14 and
4.15):

1) 4.13.0-21.24 + iwlwifi-9260-th-b0-jf-b0-33.ucode: could not connect
to any network, "Unhandled alg: 0x707"

wlp59s0: associated

and then immediately

deauthenticating from ...

see https://paste.ubuntu.com/26234416/

2) 4.14.0-041400-generic + iwlwifi-9260-th-b0-jf-b0-34.ucode (used -34 as 
recommended by Intel): Microcode SW error detected + kernel traces
https://paste.ubuntu.com/26234397/

3) 4.15.0-041500rc4-generic + iwlwifi-9260-th-b0-jf-b0-34.ucode - all
good except for pad.lv/1720930

https://paste.ubuntu.com/26234428/

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

Title:
  Intel 9260/9462/9560 firmware support

Status in HWE Next:
  New
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 Zesty:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Committed

Bug description:
  SRU Justification
  [Impact]
  Intel 9260/9462/9560 require new firmwares to enable them.

  [ 7.492326] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-33.ucode failed with error -2
  [ 7.492349] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-32.ucode failed with error -2
  [ 7.492362] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-31.ucode failed with error -2
  [ 7.492375] iwlwifi :00:0c.0: Direct firmware load for 
iwlwifi-9000-pu-a0-jf-b0-30.ucode failed with error -2
  [ 7.492378] iwlwifi :00:0c.0: no suitable firmware found!

  For v4.13 kernel, it uses firmware version 33, so we only need this.

  commit c4276b65390d32d33c8263a7e3c8be0db8cccad4 (tag: 
refs/tags/iwlwifi-fw-2017-11-03)
  Author: Luca Coelho 
  Date:   Fri Oct 13 14:22:26 2017 +0300

  iwlwifi: add firmware version 33 for new 9000 series

  Build number: WFFW53774_R30_FW610294

  Revision number: 610294

  Signed-off-by: Luca Coelho 

  [Test Case]
  After applying the firmwares, confirm the 9260/9560 can connect to 6 
different APs(bg/n/ac * open/wap)

  [Regression Potential]
  There is no regression for the new devices and new firmwares.

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

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

[Kernel-packages] [Bug 1720930] Re: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)

[Dmitrii Shcherbakov]

I can confirm this behavior on 4.13 -> 4.15rc4 with Intel 9260NGW.

3b:00.0 Network controller: Intel Corporation Device 2526 (rev 29)
Subsystem: Intel Corporation Device 0014
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at dd20 (64-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [154] L1 PM Substates
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

Only happens when the adapter is disconnected. It is functional after a
reconnect.

uname -r
4.15.0-041500rc4-generic

➜  ~ dmesg | grep -P 'firmware|iwlwifi|wlp59s0'
[2.197645] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
[   18.280244] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   18.282836] Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi
[   18.304357] platform regulatory.0: Direct firmware load for regulatory.db 
failed with error -2
[   18.313635] iwlwifi :3b:00.0: enabling device ( -> 0002)
[   18.346079] iwlwifi :3b:00.0: loaded firmware version 34.0.0 op_mode 
iwlmvm
[   18.368702] iwlwifi :3b:00.0: Detected Intel(R) Dual Band Wireless AC 
9260, REV=0x324
[   18.423757] iwlwifi :3b:00.0: base HW address: 
[   18.516593] iwlwifi :3b:00.0 wlp59s0: renamed from wlan0
[   19.474561] Bluetooth: hci0: Waiting for firmware download to complete
[   21.961162] IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
[   22.162515] IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
[   22.376361] IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
[   22.550022] IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
[  182.737439] IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
[  182.814300] wlp59s0: authenticate with 
[  182.823878] wlp59s0: send auth to  (try 1/3)
[  182.862803] wlp59s0: authenticated
[  182.866749] wlp59s0: associate with  (try 1/3)
[  182.869577] wlp59s0: RX AssocResp from  (capab=0x511 status=0 
aid=34)
[  182.871828] wlp59s0: associated
[  182.979380] IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready
[  588.512073] wlp59s0: deauthenticating from  by local choice 
(Reason: 3=DEAUTH_LEAVING)
[  588.522598] wlp59s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from 
hardware (-22)
[  595.913221] IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
[  596.006391] IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
[  599.531660] IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready
[  599.591620] wlp59s0: authenticate with 
[  599.598771] wlp59s0: send auth to  (try 1/3)
[  599.637989] wlp59s0: authenticated
[  599.640025] wlp59s0: associate with  (try 1/3)
[  599.643170] wlp59s0: RX AssocResp from  (capab=0x511 status=0 
aid=35)
[  599.645843] wlp59s0: associated
[  599.718402] IPv6: ADDRCONF(NETDEV_CHANGE): wlp59s0: link becomes ready

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

Title:
  wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware
  (-22)

Status in linux package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  When running artful on a new Zenbook Pro (uses Intel Wireless 8265), I
  get a hung shutdown with the message "wlp3s0: failed to remove key (1,
  ff:ff:ff:ff:ff:ff) from hardware (-22)". The kernel is also trying to
  load firmware versions that do not exist on the system i.e. versions
  33 then 32 of the firmware. It then seems to load version 31 of the
  firmware. Wireless features seem to work normally. The issues are just
  at shutdown time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dylan  1621 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Oct  3 06:12:13 2017
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux 

[Kernel-packages] [Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing

[Dmitrii Shcherbakov]

Andres,

I'm not going to be at the sprint but the problems described need a
proper solution in MAAS and Juju at least from the end host perspective.
Similar to how VLANs are supported natively in MAAS & Juju, L3
virtualization technologies like VRF should be as well. I hope the
information I will give here will be enough to understand the use-cases
and past experience in this field.

The concept is very similar to VLANs but for L3 which is probably less
familiar and spans many hosts and routers/L3 switches within a single
organization instead of being tied to a given switch fabric and either
the same process or a group of processes on a host need to (1) receive &
respond and (2) send data using different L3 topologies. Instead of
virtual broadcast domains you get virtual paths because of per-
virtual-L3 routing topologies. Good L2 analogies are Multiple Spanning
Tree Protocol (MSTP) or PVST+ that were created to avoid blocking of
switchports depending on logical L2 topologies related to a VLAN or
group of VLANs (this is hidden on L2 though - no end host modifications
required).

The use-cases I am talking about are not new - they were not used as
much in data center networks until a certain point. They were used in
service provider networks for multi-site L3 VPN for many years
(https://tools.ietf.org/html/rfc4364). There are still many deployments
which rely on large L2 domains where those problems do not occur as much
because routing is done trivially via using directly connected routes
and ARP broadcasts (there is never a hop between a source and
destination host in most cases).

I may be wrong but it seems to me that Network Spaces were originally
designed with multi-homing in mind but with limited support for multi-L2
and routing in mind (I don't judge, VRFs are fairly new to the Linux
kernel). They are not that far from supporting that though because of
the recent upstream kernel work.

With leaf-spine you are building a complex L3 network with different
virtual topologies for different purposes and different SLAs for various
kinds of traffic (IOW, a multi-tenant network). This is a typical
service provider scenario with different customers on a shared
infrastructure. You need to build many parallel dedicated communication
lines but since infrastructure is shared it is not possible physically,
however, you still need to do load-sharing across links, use distinct
paths for different kinds of traffic and other optimizations to make
sure your physical links are utilized and clients get certain quality of
service and are separated from each other. In this case L3 VPNs are
built not for clients (companies "x" and "y") but for different
purposes: general purpose data, storage access or replication,
management, public API traffic (originally, this was done for
voice/video/data, see the first two paragraphs in the "background"
section https://www.google.ch/patents/US8457117).

I can describe this in many ways, i.e. we need:

* multi-point L3VPN between racks to simulate L3 virtual circuits/pseudowires 
for different types of traffic;
* virtual routing domains (VRFs);
* traffic and routing separation for multi-L2 segment networks;
* L3 network multi-tenancy.

This is definitely not new, the service provider concepts may be less
familiar though:

1) Static routes + VLSM - DIY routing - doesn't scale and difficult to manage 
when a deployment grows beyond the original VLSM design;
2) VRF-lite (VRF without MPLS) - separate address spaces and routing tables for 
different traffic on routers and, potentially, hosts, interface-based selection 
of a VRF on a given network device;
3) MPLS - this is like VXLAN for virtual L3 networks. In a service provider 
network two MPLS labels are used: one for VRF identification and another one 
for next-hop router identification (in a data center network think of an 
internal or public API label, storage access label, storage replication label 
etc.).

This has been used for years to separate out traffic of different
customers or, for example, general purpose data, voice and video for a
single customer. Containers do not solve this problem with a separate
network namespace because the same process or a group of processes need
to use a different routing table "per-purpose".

What I am asking for is not that difficult because we are only concerned
with end hosts (unless MAAS resides on a ToR or a leaf and we control
the switch OS). I need building blocks to use either VRF-lite or full
VRFs with MPLS in a sane way while keeping routing complexity (BGP, MPLS
etc.) in a data center provider network managed by other people.

Terminology-wise, I think changes are needed as well:
https://github.com/CanonicalLtd/maas-docs/issues/737 - Routing Domain,
L3VPN or VRF are common names for what we refer to as a Network Space,
and what is actually a virtual L3 network with its own complete address
space, routing table copies and dedicated host/router physical or
logical interfaces.

Examples:

[Kernel-packages] [Bug 1729608] Re: arithmetic expression: expecting primary: " (32-)/4 "

[Dmitrii Shcherbakov]

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

** This bug has been marked a duplicate of bug 1737640
   /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured 
interfaces cause ifup failures

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

Title:
  arithmetic expression: expecting primary: " (32-)/4 "

Status in juju:
  New
Status in OPNFV:
  New
Status in ubuntu-fan package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've configured a bridge interface (named vlan0) through interfaces,
  but can't take it up with ifup, since the if-up-script from ubuntu-fan
  aborts with error status

  
  reason:

  # fanctl net start vlan0
  /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting 
primary: " (32-)/4 "


  As far as I can see the problem is that in cmd_net_up() the line

  
  addr="${addr%/*}"

  cuts the mask from the interface config and passes the pure ip address
  only, but later config_filename() calls width_to_mask(), which tries
  to use the (now missing) mask.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-fan 0.12.6
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Nov  2 14:26:42 2017
  InstallationDate: Installed on 2017-10-24 (9 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-fan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

[Dmitrii Shcherbakov]

Tested that on a "broken" environment (after a reboot with a broken
package):

root@maas-xenial3:~# apt install ubuntu-fan
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  ubuntu-fan
1 upgraded, 0 newly installed, 0 to remove and 94 not upgraded.
Need to get 36.4 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ppa.launchpad.net/canonical-kernel-team/fan-fixes/ubuntu 
xenial/main amd64 ubuntu-fan all 0.12.8~16.04.2~rc1 [36.4 kB]
Fetched 36.4 kB in 0s (0 B/s)   
(Reading database ... 60144 files and directories currently installed.)
Preparing to unpack .../ubuntu-fan_0.12.8~16.04.2~rc1_all.deb ...
Unpacking ubuntu-fan (0.12.8~16.04.2~rc1) over (0.12.8~16.04.1) ...
Processing triggers for systemd (229-4ubuntu19) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up ubuntu-fan (0.12.8~16.04.2~rc1) ...

# after a reboot with a broken package an address was present but the
interface was not considered as "configured" by ifupdown - had to
manually delete an address to avoid RTNETLINK answers: File exists on
ifup

root@maas-xenial3:~# ip a d 10.10.101.104/24 dev ens3

root@maas-xenial3:~# ifdown ens3
ifdown: interface ens3 not configured

root@maas-xenial3:~# ifup ens3

root@maas-xenial3:~# ip a s
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: ens3:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether 52:54:00:82:7d:16 brd ff:ff:ff:ff:ff:ff
inet 10.10.101.104/24 brd 10.10.101.255 scope global ens3
   valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe82:7d16/64 scope link 
   valid_lft forever preferred_lft forever

# all good
root@maas-xenial3:~# ifdown -a
root@maas-xenial3:~# ifup -a

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

Title:
  /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Triaged
Status in ubuntu-fan package in Ubuntu:
  Confirmed

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1737640] Re: bridge activaction error: bridge activation failed | unconfigured interfaces cause ifup failures

[Dmitrii Shcherbakov]

This is reproducible on a machine with a single NIC:

https://paste.ubuntu.com/26170595/

** Summary changed:

- bridge activaction error: bridge activation failed | unconfigured interfaces 
cause ifup failures
+ /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured 
interfaces cause ifup failures

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

Title:
  /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Triaged
Status in ubuntu-fan package in Ubuntu:
  Confirmed

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1737640] Re: bridge activaction error: bridge activation failed | unconfigured interfaces cause ifup failures

[Dmitrii Shcherbakov]

Before and after ifdown -> ifup with fan:

http://paste.ubuntu.com/26169937/


After purging:

http://paste.ubuntu.com/26169950/

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

Title:
  bridge activaction error: bridge activation failed | unconfigured
  interfaces cause ifup failures

Status in juju:
  Triaged
Status in ubuntu-fan package in Ubuntu:
  New

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1737640] Re: bridge activaction error: bridge activation failed

[Dmitrii Shcherbakov]

ubuntu-fan clearly triggers the problem.

Clean machine, no bridges after Juju installs ubuntu-fan and networking
still works as bridges were not created yet => no ifup/down executions:

root@maas-xenial3:/home/ubuntu# ifdown -a ; ifup -a
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting 
primary: " (32-)/4 "
run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2
Failed to bring up ens3.

root@maas-xenial3:/home/ubuntu# ifdown -a
root@maas-xenial3:/home/ubuntu# ifup -a
RTNETLINK answers: File exists
Failed to bring up ens3. 

root@maas-xenial3:/home/ubuntu# apt purge ubuntu-fan
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  ubuntu-fan*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 148 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 65843 files and directories currently installed.)
ubuntu-fan: removing default /etc/network/fan configuration
Purging configuration files for ubuntu-fan (0.12.8~16.04.1) ...

root@maas-xenial3:/home/ubuntu# ifdown -a
root@maas-xenial3:/home/ubuntu# ifup -a
RTNETLINK answers: File exists
Failed to bring up ens3.

root@maas-xenial3:/home/ubuntu# ifdown ens3
ifdown: interface ens3 not configured

root@maas-xenial3:/home/ubuntu# ip a d 10.10.101.103/24 dev ens3
root@maas-xenial3:/home/ubuntu# ifup -a

root@maas-xenial3:/home/ubuntu# apt install ubuntu-fan
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  ubuntu-fan
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/35.6 kB of archives.
Selecting previously unselected package ubuntu-fan.ce will be used.
Processing triggers for systemd (229-4ubuntu21) ...urrently installed.)
Processing triggers for ureadahead (0.100.0-19) ...ll.deb ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu21) ...
root@maas-xenial3:/home/ubuntu# ifdown -a
root@maas-xenial3:/home/ubuntu# ifup -a
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting 
primary: " (32-)/4 "
run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2
Failed to bring up ens3.
root@maas-xenial3:/home/ubuntu# ifup -a
RTNETLINK answers: File exists
Failed to bring up ens3.

** Also affects: ubuntu-fan (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- bridge activaction error: bridge activation failed
+ bridge activaction error: bridge activation failed | unconfigured interfaces 
cause ifup failures

** Tags added: cpe-onsite

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

Title:
  bridge activaction error: bridge activation failed | unconfigured
  interfaces cause ifup failures

Status in juju:
  Triaged
Status in ubuntu-fan package in Ubuntu:
  New

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

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

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

[Kernel-packages] [Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing

[Dmitrii Shcherbakov]

** Description changed:

  Problem description:
  
  * a host is multi-homed if it has multiple network interfaces with L3
  addresses configured (physical or virtual interfaces, natural to
  OpenStack regardless of IPv4/IPv6 and IPv6 in general);
+ 
+ (see 3.3.4  Local Multihoming
+ https://tools.ietf.org/html/rfc1122#page-60 and 3.3.4.2  Multihoming
+ Requirements)
  
  * if all hosts that need to participate in L3 communication are located
  on the same L2 network there is no need for a routing device to be
  present. ARP/NDP and auto-created directly connected routes are enough;
  
  * multi-homing with hosts located on different L2 networks requires more 
intelligent routing:
    - "directly connected" routes are no longer enough to talk to all relevant 
hosts in the same network space;
    - a default gateway in the main routing table may not be the correct 
routing device that knows where to forward traffic (management network traffic 
goes to a management switch and router, other traffic goes to L3 ToR switch but 
may go via different bonds);
    - even if a default gateway knows where to forward traffic, it may not be 
the intended physical path (storage replication traffic must go through a 
specific outgoing interface, not the same interface as storage access traffic 
although both interfaces are connected to the same ToR);
    - there is no longer a single "default gateway" as applications need either 
per-logical-direction routers or to become routers themselves (if destination 
== X, forward to next-hop Y). Leaf-spine architecture is a good example of how 
multiple L2 networks force you to use spaces that have VLANs in different 
switch fabrics => one or more hops between hosts with interfaces associated 
with the same network space;
    - while network spaces implicitly require L3 reachability between each host 
that has a NIC associated with a network space, the current definition does not 
mention routing infrastructure required for that. For a single L2 this problem 
is hidden by directly connected routes, for multi-L2, no solution is provided 
or discussed;
  
  * existing solutions to multi-homing require routing table management on
  a given host: complex static routing rules, dynamic routing (e.g.
  running an OSPF or BGP daemon on a host);
  
  * using static routes is rigid and requires network planning (i.e.
  working with network engineers which may have varying degrees of
  experience, doing VLSM planning etc.);
  
  * using dynamic routing requires a broader integration into an
  organization's L3 network infrastructure. Routing can be implemented
  differently across different organizations and it is a security and
  operational burden to integrate with a company's routing infrastructure.
  
  Summary: a mechanism is needed to associate an interface with a
  forwarding table (FIB) which has its own default gateway and make an
  application with a listen(2)ing socket(2) return connected sockets
  associated with different FIBs. In other words, applications need to
  implicitly get source/destination-based routing capabilities without the
  need to use static routing schemes or dynamic routing and with minimum
  or no modifications to the applications themselves.
  
  Goals:
  
  * avoid turning individual hosts into routers;
  * avoid complex static rules;
  * better support multi-fabric deployments with minimum effort (Juju, charms, 
MAAS, applications, network infrastructure);
  * reduce operational complexity (custom L3 infrastructure integration for 
each deployment);
  * reduce delivery risks (L3 infrastructure, L3 department responsiveness 
varies);
  * avoid any form of L2 stretching at the infrastructure level - this is 
inefficient for various reasons.
  
  NOTE: https://cumulusnetworks.com/blog/vrf-for-linux/ - I recommend to
  read this post to understand suggestions below.
  
  How to solve it?
  
  What does it mean for Juju to support VRF devices?
  
  * enslave certain devices on provisioning based on network space information 
(physical NICs, VLAN devices, bonds AND bridges created for containers must be 
considered) - VRF devices logically enslave devices similar to bridges but work 
differently (on L3, not L2);
  * the above is per network namespace so it will work equally well in a LXD 
container;
  
  Conceptually:
  
  # echo 'net.ipv4.tcp_l3mdev_accept = 1' >> /etc/sysctl.conf
  # echo 'net.ipv4.udp_l3mdev_accept = 1' >> /etc/sysctl.conf
  # sysctl -p
  
  # # create additional routing tables
  # cat >> /etc/iproute2/rt_tables.d/vrf.conf 

[Kernel-packages] [Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing

[Dmitrii Shcherbakov]

** Description changed:

  Problem description:
  
  * a host is multi-homed if it has multiple network interfaces with L3
  addresses configured (physical or virtual interfaces, natural to
  OpenStack regardless of IPv4/IPv6 and IPv6 in general);
  
  * if all hosts that need to participate in L3 communication are located
  on the same L2 network there is no need for a routing device to be
  present. ARP/NDP and auto-created directly connected routes are enough;
  
  * multi-homing with hosts located on different L2 networks requires more 
intelligent routing:
-   - "directly connected" routes are no longer enough to talk to all relevant 
hosts in the same network space;
-   - a default gateway in the main routing table may not be the correct 
routing device that knows where to forward traffic (management network traffic 
goes to a management switch and router, other traffic goes to L3 ToR switch but 
may go via different bonds);
-   - even if a default gateway knows where to forward traffic, it may not be 
the intended physical path (storage replication traffic must go through a 
specific outgoing interface, not the same interface as storage access traffic 
although both interfaces are connected to the same ToR);
-   - there is no longer a single "default gateway" as applications need either 
per-logical-direction routers or to become routers themselves (if destination 
== X, forward to next-hop Y). Leaf-spine architecture is a good example of how 
multiple L2 networks force you to use spaces that have VLANs in different 
switch fabrics => one or more hops between hosts with interfaces associated 
with the same network space;
-   - while network spaces implicitly require L3 reachability between each host 
that has a NIC associated with a network space, the current definition does not 
mention routing infrastructure required for that. For a single L2 this problem 
is hidden by directly connected routes, for multi-L2, no solution is provided 
or discussed;
+   - "directly connected" routes are no longer enough to talk to all relevant 
hosts in the same network space;
+   - a default gateway in the main routing table may not be the correct 
routing device that knows where to forward traffic (management network traffic 
goes to a management switch and router, other traffic goes to L3 ToR switch but 
may go via different bonds);
+   - even if a default gateway knows where to forward traffic, it may not be 
the intended physical path (storage replication traffic must go through a 
specific outgoing interface, not the same interface as storage access traffic 
although both interfaces are connected to the same ToR);
+   - there is no longer a single "default gateway" as applications need either 
per-logical-direction routers or to become routers themselves (if destination 
== X, forward to next-hop Y). Leaf-spine architecture is a good example of how 
multiple L2 networks force you to use spaces that have VLANs in different 
switch fabrics => one or more hops between hosts with interfaces associated 
with the same network space;
+   - while network spaces implicitly require L3 reachability between each host 
that has a NIC associated with a network space, the current definition does not 
mention routing infrastructure required for that. For a single L2 this problem 
is hidden by directly connected routes, for multi-L2, no solution is provided 
or discussed;
  
  * existing solutions to multi-homing require routing table management on
  a given host: complex static routing rules, dynamic routing (e.g.
  running an OSPF or BGP daemon on a host);
  
  * using static routes is rigid and requires network planning (i.e.
  working with network engineers which may have varying degrees of
  experience, doing VLSM planning etc.);
  
  * using dynamic routing requires a broader integration into an
  organization's L3 network infrastructure. Routing can be implemented
  differently across different organizations and it is a security and
  operational burden to integrate with a company's routing infrastructure.
  
  Summary: a mechanism is needed to associate an interface with a
  forwarding table (FIB) which has its own default gateway and make an
  application with a listen(2)ing socket(2) return connected sockets
  associated with different FIBs. In other words, applications need to
  implicitly get source/destination-based routing capabilities without the
  need to use static routing schemes or dynamic routing and with minimum
  or no modifications to the applications themselves.
  
  Goals:
  
  * avoid turning individual hosts into routers;
  * avoid complex static rules;
  * better support multi-fabric deployments with minimum effort (Juju, charms, 
MAAS, applications, network infrastructure);
  * reduce operational complexity (custom L3 infrastructure integration for 
each deployment);
  * reduce delivery risks (L3 infrastructure, L3 department responsiveness 
varies);
  * avoid any form of L2 stretching at the 

[Kernel-packages] [Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing

[Dmitrii Shcherbakov]

For Ubuntu kernel this is a backport request.

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

Title:
  VRF support to solve routing problems associated with multi-homing

Status in juju:
  New
Status in MAAS:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Problem description:

  * a host is multi-homed if it has multiple network interfaces with L3
  addresses configured (physical or virtual interfaces, natural to
  OpenStack regardless of IPv4/IPv6 and IPv6 in general);

  * if all hosts that need to participate in L3 communication are
  located on the same L2 network there is no need for a routing device
  to be present. ARP/NDP and auto-created directly connected routes are
  enough;

  * multi-homing with hosts located on different L2 networks requires more 
intelligent routing:
- "directly connected" routes are no longer enough to talk to all relevant 
hosts in the same network space;
- a default gateway in the main routing table may not be the correct 
routing device that knows where to forward traffic (management network traffic 
goes to a management switch and router, other traffic goes to L3 ToR switch but 
may go via different bonds);
- even if a default gateway knows where to forward traffic, it may not be 
the intended physical path (storage replication traffic must go through a 
specific outgoing interface, not the same interface as storage access traffic 
although both interfaces are connected to the same ToR);
- there is no longer a single "default gateway" as applications need either 
per-logical-direction routers or to become routers themselves (if destination 
== X, forward to next-hop Y). Leaf-spine architecture is a good example of how 
multiple L2 networks force you to use spaces that have VLANs in different 
switch fabrics => one or more hops between hosts with interfaces associated 
with the same network space;
- while network spaces implicitly require L3 reachability between each host 
that has a NIC associated with a network space, the current definition does not 
mention routing infrastructure required for that. For a single L2 this problem 
is hidden by directly connected routes, for multi-L2, no solution is provided 
or discussed;

  * existing solutions to multi-homing require routing table management
  on a given host: complex static routing rules, dynamic routing (e.g.
  running an OSPF or BGP daemon on a host);

  * using static routes is rigid and requires network planning (i.e.
  working with network engineers which may have varying degrees of
  experience, doing VLSM planning etc.);

  * using dynamic routing requires a broader integration into an
  organization's L3 network infrastructure. Routing can be implemented
  differently across different organizations and it is a security and
  operational burden to integrate with a company's routing
  infrastructure.

  Summary: a mechanism is needed to associate an interface with a
  forwarding table (FIB) which has its own default gateway and make an
  application with a listen(2)ing socket(2) return connected sockets
  associated with different FIBs. In other words, applications need to
  implicitly get source/destination-based routing capabilities without
  the need to use static routing schemes or dynamic routing and with
  minimum or no modifications to the applications themselves.

  Goals:

  * avoid turning individual hosts into routers;
  * avoid complex static rules;
  * better support multi-fabric deployments with minimum effort (Juju, charms, 
MAAS, applications, network infrastructure);
  * reduce operational complexity (custom L3 infrastructure integration for 
each deployment);
  * reduce delivery risks (L3 infrastructure, L3 department responsiveness 
varies);
  * avoid any form of L2 stretching at the infrastructure level - this is 
inefficient for various reasons.

  NOTE: https://cumulusnetworks.com/blog/vrf-for-linux/ - I recommend to
  read this post to understand suggestions below.

  How to solve it?

  What does it mean for Juju to support VRF devices?

  * enslave certain devices on provisioning based on network space information 
(physical NICs, VLAN devices, bonds AND bridges created for containers must be 
considered) - VRF devices logically enslave devices similar to bridges but work 
differently (on L3, not L2);
  * the above is per network namespace so it will work equally well in a LXD 
container;

  Conceptually:

  # echo 'net.ipv4.tcp_l3mdev_accept = 1' >> /etc/sysctl.conf
  # echo 'net.ipv4.udp_l3mdev_accept = 1' >> /etc/sysctl.conf
  # sysctl -p

  # ip link add mgmt type vrf table 1 && ip link set dev mgmt up
  # ip link add pub type vrf table 2 && ip link set dev pub up

  # ip link set mgmtbr0 master management
  # ip link set pubbr0 master public

  # make your services use INADDR_ANY for listening sockets in charms if
  not done 

[Kernel-packages] [Bug 1737428] [NEW] VRF support to solve routing problems associated with multi-homing

[Dmitrii Shcherbakov]

Public bug reported:

Problem description:

* a host is multi-homed if it has multiple network interfaces with L3
addresses configured (physical or virtual interfaces, natural to
OpenStack regardless of IPv4/IPv6 and IPv6 in general);

* if all hosts that need to participate in L3 communication are located
on the same L2 network there is no need for a routing device to be
present. ARP/NDP and auto-created directly connected routes are enough;

* multi-homing with hosts located on different L2 networks requires more 
intelligent routing:
  - "directly connected" routes are no longer enough to talk to all relevant 
hosts in the same network space;
  - a default gateway in the main routing table may not be the correct routing 
device that knows where to forward traffic (management network traffic goes to 
a management switch and router, other traffic goes to L3 ToR switch but may go 
via different bonds);
  - even if a default gateway knows where to forward traffic, it may not be the 
intended physical path (storage replication traffic must go through a specific 
outgoing interface, not the same interface as storage access traffic although 
both interfaces are connected to the same ToR);
  - there is no longer a single "default gateway" as applications need either 
per-logical-direction routers or to become routers themselves (if destination 
== X, forward to next-hop Y). Leaf-spine architecture is a good example of how 
multiple L2 networks force you to use spaces that have VLANs in different 
switch fabrics => one or more hops between hosts with interfaces associated 
with the same network space;
  - while network spaces implicitly require L3 reachability between each host 
that has a NIC associated with a network space, the current definition does not 
mention routing infrastructure required for that. For a single L2 this problem 
is hidden by directly connected routes, for multi-L2, no solution is provided 
or discussed;

* existing solutions to multi-homing require routing table management on
a given host: complex static routing rules, dynamic routing (e.g.
running an OSPF or BGP daemon on a host);

* using static routes is rigid and requires network planning (i.e.
working with network engineers which may have varying degrees of
experience, doing VLSM planning etc.);

* using dynamic routing requires a broader integration into an
organization's L3 network infrastructure. Routing can be implemented
differently across different organizations and it is a security and
operational burden to integrate with a company's routing infrastructure.

Summary: a mechanism is needed to associate an interface with a
forwarding table (FIB) which has its own default gateway and make an
application with a listen(2)ing socket(2) return connected sockets
associated with different FIBs. In other words, applications need to
implicitly get source/destination-based routing capabilities without the
need to use static routing schemes or dynamic routing and with minimum
or no modifications to the applications themselves.

Goals:

* avoid turning individual hosts into routers;
* avoid complex static rules;
* better support multi-fabric deployments with minimum effort (Juju, charms, 
MAAS, applications, network infrastructure);
* reduce operational complexity (custom L3 infrastructure integration for each 
deployment);
* reduce delivery risks (L3 infrastructure, L3 department responsiveness 
varies);
* avoid any form of L2 stretching at the infrastructure level - this is 
inefficient for various reasons.

NOTE: https://cumulusnetworks.com/blog/vrf-for-linux/ - I recommend to
read this post to understand suggestions below.

How to solve it?

What does it mean for Juju to support VRF devices?

* enslave certain devices on provisioning based on network space information 
(physical NICs, VLAN devices, bonds AND bridges created for containers must be 
considered) - VRF devices logically enslave devices similar to bridges but work 
differently (on L3, not L2);
* the above is per network namespace so it will work equally well in a LXD 
container;

Conceptually:

# echo 'net.ipv4.tcp_l3mdev_accept = 1' >> /etc/sysctl.conf
# echo 'net.ipv4.udp_l3mdev_accept = 1' >> /etc/sysctl.conf
# sysctl -p

# ip link add mgmt type vrf table 1 && ip link set dev mgmt up
# ip link add pub type vrf table 2 && ip link set dev pub up

# ip link set mgmtbr0 master management
# ip link set pubbr0 master public

# make your services use INADDR_ANY for listening sockets in charms if
not done already (use 0.0.0.0)

charm-related:

* (no-op) services with listening sockets on INADDR_ANY will not need
any modifications either on the charm side or at the application level -
this is the cheapest way to solve multi-homing problems;

* (later) a more advanced functionality for applications that do not use
INADDR_ANY but bind a listening socket to a specific address - this
requires `ip vrf exec` functionality in iproute2 or application
modifications.

Notes:

* Let's 

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

[Dmitrii Shcherbakov]

Looks like masking systemd-udevd removes this behavior. Need to figure
out where it actually clears everything out.

ubuntu@maas-xenial4:~$ sudo systemctl mask systemd-udevd
11:32 PM Created symlink from /etc/systemd/system/systemd-udevd.service to 
/dev/null.

# reboot

ubuntu@maas-xenial4:~$ ls /dev/bcache/by-uuid/
2963855b-3d2b-4387-abd1-3ae788919de4  727212eb-0f0b-4d20-9191-f0577a38454e  
835afacf-6213-48a9-864c-43733822668b  aa04ab39-a42c-446f-aff5-addbd9c80e06

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

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

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

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

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

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

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

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

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

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

  then rootfs ismounted and systemd starts systemd-udev

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or 

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

[Dmitrii Shcherbakov]

Ryan,

As discussed in IRC, I tweaked locations for testing in #11 and added
all paths in #14.

Looks like after `mount -n -o move /dev ${rootmnt}/dev` ${rootmnt}/dev
has the proper content (see the bcache rule as well)

https://paste.ubuntu.com/26082611/
== before ==
lrwxrwxrwx113 
/dev/bcache/by-uuid/aa04ab39-a42c-446f-aff5-addbd9c80e06 -> ../../bcache0
lrwxrwxrwx113 
/dev/bcache/by-uuid/835afacf-6213-48a9-864c-43733822668b -> ../../bcache3
lrwxrwxrwx113 
/dev/bcache/by-uuid/727212eb-0f0b-4d20-9191-f0577a38454e -> ../../bcache1
lrwxrwxrwx113 
/dev/bcache/by-uuid/2963855b-3d2b-4387-abd1-3ae788919de4 -> ../../bcache2

== after ==
lrwxrwxrwx113 
/root/dev/bcache/by-uuid/aa04ab39-a42c-446f-aff5-addbd9c80e06 -> ../../bcache0
lrwxrwxrwx113 
/root/dev/bcache/by-uuid/835afacf-6213-48a9-864c-43733822668b -> ../../bcache3
lrwxrwxrwx113 
/root/dev/bcache/by-uuid/727212eb-0f0b-4d20-9191-f0577a38454e -> ../../bcache1
lrwxrwxrwx113 
/root/dev/bcache/by-uuid/2963855b-3d2b-4387-abd1-3ae788919de4 -> ../../bcache2

So the problem must be further down.

And about the only thing I see in the init script is run-init from
klibc:

# Chain to real filesystem
exec run-init ${drop_caps} ${rootmnt} ${init} "$@" 
${recovery:+--startup-event=recovery} <${rootmnt}/dev/console 
>${rootmnt}/dev/console 2>&1

So it's either somewhere in run-init code

https://git.launchpad.net/~usd-import-
team/ubuntu/+source/klibc/tree/usr/kinit/run-
init/runinitlib.c?h=applied/ubuntu/xenial-updates#n158

or in systemd.

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

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

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

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

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

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

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

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

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

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

  then rootfs ismounted and systemd starts systemd-udev

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

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

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

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

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

  where env includes: 
  "DRIVER=bcache",
  

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

[Dmitrii Shcherbakov]

Just in case also checked with this rule that creates links at /dev
/dev/disk/by-uuid /dev/bcache/by-uuid https://paste.ubuntu.com/26081756/

They are all there originally (see the screenshot).

But not there afterwards. So it's not just a problem with a different
path.

https://paste.ubuntu.com/26081775/

ubuntu@maas-xenial4:~$ tree /dev/ | grep bcache
├── bcache0
├── bcache1
├── bcache2
├── bcache3
│   ├── 251:0 -> ../bcache0
│   ├── 251:1 -> ../bcache1
│   ├── 251:2 -> ../bcache2
│   ├── 251:3 -> ../bcache3
│   │   ├── bcache0 -> ../../bcache0
│   │   ├── bcache1 -> ../../bcache1
│   │   ├── bcache2 -> ../../bcache2
│   │   ├── bcache3 -> ../../bcache3


** Attachment added: "bcache-multiple-links.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+attachment/5016592/+files/bcache-multiple-links.png

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

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

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

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

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

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

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

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

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

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

  then rootfs ismounted and systemd starts systemd-udev

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  

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

[Dmitrii Shcherbakov]

After booting with break=bottom kernel parameter I can see that symlinks
are in fact present at the initramfs stage.

They are gone afterwards post pivot_root & systemd start (the bcache dir
isn't even present while it was there)

ubuntu@maas-xenial4:~$ ls /dev/disk/
by-dname  by-id  by-label  by-path  by-uuid


** Attachment added: "bcache-symlinks-initramfs.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+attachment/5016556/+files/bcache-symlinks-initramfs.png

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

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

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

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

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

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

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

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

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

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

  then rootfs ismounted and systemd starts systemd-udev

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No 

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

[Dmitrii Shcherbakov]

We do run udevd at the initramfs stage in init-top and stop it in init-
bottom:

➜  scripts git:(ubuntu/xenial-updates) ✗ grep -RiP udev
init-bottom/udev:# Stop udevd, we'll miss a few events while we run init, but 
we catch up
init-bottom/udev:udevadm control --exit

init-top/udev:SYSTEMD_LOG_LEVEL=$log_level /lib/systemd/systemd-udevd --daemon 
--resolve-names=never
init-top/udev:udevadm trigger --type=subsystems --action=add
init-top/udev:udevadm trigger --type=devices --action=add
init-top/udev:udevadm settle || true


And, from what I can see after adding some logging to the udev rule and 
updating initramfs, KOBJ_CHANGE events generated by the bcache driver are 
processed by 69-bcache.rules:

http://paste.ubuntu.com/26080228/ (rule)


https://paste.ubuntu.com/26080236/ (dmesg)
[1.789254] AFTER DRIVER BCACHE: devpath: /devices/virtual/block/bcache0 
UUID: dd563676-f731-420c-a65d-93992321eb14, LABEL:
[1.790563] AFTER DRIVER BCACHE: devpath: /devices/virtual/block/bcache1 
UUID: 3aec199f-d1d7-452f-a56d-9c946c72cae1, LABEL:
[1.794265] PROBING BCACHE /devices/virtual/block/bcache3
[1.795957] BEFORE DRIVER BCACHE /devices/virtual/block/bcache3
[1.798215] AFTER DRIVER BCACHE: devpath: /devices/virtual/block/bcache3 
UUID: 2c8f2de3-a1a5-4f53-ad00-09294eb19512, LABEL:
[1.801311] PROBING BCACHE /devices/virtual/block/bcache2
[1.803180] BEFORE DRIVER BCACHE /devices/virtual/block/bcache2
[1.804731] AFTER DRIVER BCACHE: devpath: /devices/virtual/block/bcache2 
UUID: dcdb4830-78f2-494a-905b-efa549b484fc, LABEL:

So the UUID is present in the environment of the CHANGE uevent but the
symlink is not present when I ssh into the system after the boot
process.


I wonder why that happens as devtmpfs mounted at /dev is moved to the new 
rootfs before init script exits and systemd is started - so if it's created on 
that devtmpfs, it should be there at the end:

https://git.launchpad.net/~usd-import-
team/ubuntu/+source/systemd/tree/debian/extra/initramfs-tools/scripts
/init-bottom/udev?h=applied/ubuntu/xenial-updates

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

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

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

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

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

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

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

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

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

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

  then rootfs ismounted and systemd starts systemd-udev

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

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

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

  The problem then is that only a kernel call to bch_cached_dev_run()
  

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

[Dmitrii Shcherbakov]

So, the kernel fix could look like this:

* instead of just failing with "device already registered"
* the kernel would emit another uevent with CACHED_UUID which would be 
processed another time to set up a symlink

It seems like this approach with "synthetic uevents" may be used for
other purposes as well with changes that landed in 4.13

http://elixir.free-electrons.com/linux/v4.14.2/source/Documentation/ABI/testing/sysfs-uevent
"Enable passing additional variables for synthetic uevents that are generated 
by writing /sys/.../uevent file

Recognized extended format is ACTION [UUID [KEY=VALUE ...]

Users: udev, userspace tools generating synthetic uevents"

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

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

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

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

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

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

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

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

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

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

  then rootfs ismounted and systemd starts systemd-udev

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 

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

[Dmitrii Shcherbakov]

I reviewed this once again:

1. persistent /dev/bcache - not possible or needed due to how kernel 
enumeration works
2. our userspace handles /dev/by-dname/ properly so we just need 
CACHED_UUID given to us during coldplug in some way to properly create 
/dev/bcache/by-uuid/ symlinks and consequently by-dname symlinks. 

3. bcache, like almost all block device drivers, gets "struct
device_type disk_type" by using alloc_disk from genhd.c which gives us
standard contents for the uevent file. Partitions are a notable
exception and use "struct device_type part_type" which has a .uevent
field (http://elixir.free-electrons.com/linux/v4.14.2/source/block
/partition-generic.c#L223) that allows customization of uevent file
contents in a bus-, class- and type-specific manner (http://elixir.free-
electrons.com/linux/v4.14.2/source/drivers/base/core.c#L903).

cat /sys/class/block/nvme0n1/uevent  
MAJOR=259
MINOR=0
DEVNAME=nvme0n1
DEVTYPE=disk


as opposed to the following with partitions

cat /sys/class/block/nvme0n1p1/uevent 
MAJOR=259
MINOR=1
DEVNAME=nvme0n1p1
DEVTYPE=partition
PARTN=1
PARTNAME=Basic data partition


While we could have a new block device type of "bcache" with a custom uevent 
content that had CACHED_UUID of a superblock this would be a userspace breakage 
which is hardly upstreamable.

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

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

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

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

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

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

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

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

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

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

  then rootfs ismounted and systemd starts systemd-udev

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[Dmitrii Shcherbakov]

Marcos,

#68

Regardless of fastboot on/off I get the same behavior without
pcie_aspm=off

➜  ~ uname -r
4.13.0-16-generic

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

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

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

[Dmitrii Shcherbakov]

** Tags added: cpe-onsite

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

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

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

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

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

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

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

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

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

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

  then rootfs ismounted and systemd starts systemd-udev

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] 

[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)

[Dmitrii Shcherbakov]

So, going back to question in #60, the Dell link just says to get the
latest stuff from kvalo's firmware repo.

If you are on 17.10 like myself then you already have it and it doesn't
help with the original problem:

➜  ~ apt policy linux-firmware 
linux-firmware:
  Installed: 1.169
  Candidate: 1.169
  Version table:
 *** 1.169 500
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu artful/main i386 Packages
500 http://ru.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://ru.archive.ubuntu.com/ubuntu artful/main i386 Packages
100 /var/lib/dpkg/status


➜  ~ sha256sum /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin 
dc74ba148cf88f1f99a62854112ec574d8c265d88417a4d969461448b0ab60c5  
/lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin


➜  hw3.0 sha256sum 
~/src/ath10k-firmware/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1
 
dc74ba148cf88f1f99a62854112ec574d8c265d88417a4d969461448b0ab60c5  
/home/username/src/ath10k-firmware/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1


[ ID] Interval   Transfer Bandwidth   Retr
[  5]   0.00-10.04  sec  29.2 MBytes  24.4 Mbits/sec0 sender
[  5]   0.00-10.04  sec  29.2 MBytes  24.4 Mbits/sec  receiver

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

Title:
  Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
  1535)

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

Bug description:
  Update (2017-05-20):
  Kalle Valo suggested a hack which increased client -> AP TCP performance - so 
it does not look like a firmware issue as I thought originally, rather an 
ath10k driver issue:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11
  https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom)
  Tested here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17

  Update: added some forensics in the paste (a long read):
  http://paste.ubuntu.com/24118478/

  -

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535

  Original message:
  --
  I experience a very poor 802.11ac performance of a QCA6174 Wireless card 
(Killer Wireless 1535).

  This is a dev version of Zesty with a recently released 4.10 kernel:

  uname -r
  4.10.0-9-generic

  dpkg -l linux-firmware | grep ii
  ii  linux-firmware 1.163all  Firmware for Linux kernel drivers

  lspci -vvv:

  ...
  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: ath10k_pci
  Kernel modules: ath10k_pci

  -

  Testing wireless speed with RT-87U 802.11ac router shows that the
  speed is only 27.3 megabits per second which is very low for an
  802.11ac card:

  iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [  3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001
  [ ID] Interval   Transfer Bandwidth
  [  3]  0.0-10.0 sec  32.6 MBytes  27.3 Mbits/sec

  

  For comparison, on the same network (from the same distance to the
  router) I have the following result with an Intel's card (on a 4.8
  kernel, different laptop):

  UX32LN:~$ lspci | grep 7260
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  UX32LN:~$ iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001
  [ ID] Interval Transfer Bandwidth
  [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec
  administrator@UX32LN:~$ lsp
  lspci lspcmcia lspgpot

  200 Mbps is much better.

  ---

  Back to the problematic card:

  Booted 16.04.2 with the rolling HWE kernel 4.8:

  journalctl -k | grep -i ath
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( 
-> 0002)
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  Mar 04 18:28:31 

[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)

[Dmitrii Shcherbakov]

There's also Intel 9260 coming up (wave 2):

https://wikidevi.com/wiki/Intel_Dual_Band_Wireless-AC_9260_(9260NGW)

Judging by this https://communities.intel.com/message/506847#506847 it's
only available for OEMs as of now so maybe those will go into
circulation soon for regular folks.

Meanwhile, I'll try the latest firmware from kvalo.

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

Title:
  Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
  1535)

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

Bug description:
  Update (2017-05-20):
  Kalle Valo suggested a hack which increased client -> AP TCP performance - so 
it does not look like a firmware issue as I thought originally, rather an 
ath10k driver issue:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11
  https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom)
  Tested here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17

  Update: added some forensics in the paste (a long read):
  http://paste.ubuntu.com/24118478/

  -

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535

  Original message:
  --
  I experience a very poor 802.11ac performance of a QCA6174 Wireless card 
(Killer Wireless 1535).

  This is a dev version of Zesty with a recently released 4.10 kernel:

  uname -r
  4.10.0-9-generic

  dpkg -l linux-firmware | grep ii
  ii  linux-firmware 1.163all  Firmware for Linux kernel drivers

  lspci -vvv:

  ...
  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: ath10k_pci
  Kernel modules: ath10k_pci

  -

  Testing wireless speed with RT-87U 802.11ac router shows that the
  speed is only 27.3 megabits per second which is very low for an
  802.11ac card:

  iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [  3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001
  [ ID] Interval   Transfer Bandwidth
  [  3]  0.0-10.0 sec  32.6 MBytes  27.3 Mbits/sec

  

  For comparison, on the same network (from the same distance to the
  router) I have the following result with an Intel's card (on a 4.8
  kernel, different laptop):

  UX32LN:~$ lspci | grep 7260
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  UX32LN:~$ iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001
  [ ID] Interval Transfer Bandwidth
  [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec
  administrator@UX32LN:~$ lsp
  lspci lspcmcia lspgpot

  200 Mbps is much better.

  ---

  Back to the problematic card:

  Booted 16.04.2 with the rolling HWE kernel 4.8:

  journalctl -k | grep -i ath
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( 
-> 0002)
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch 
firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 
debugfs 1 tracing 1 dfs 0 testmode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: 

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

[Dmitrii Shcherbakov]

There is a scenario where a real rootfs is located on a bcache device,
however, for that we need to register a bcache device at the initrd
stage which already happens now. Then we'd locate a file system on it
and do pivot_root and so on.

The bcache naming, I believe, is not guaranteed at this point unless
we have a rule that says so.

Side-tracking to our field use-cases, we need persistence in
/dev/bcache names based on superblock UUIDs. So, I expect
/dev/bcache/ names to be persisted by UUID on first discovery (which
corresponds to MAAS deploy stage, not commissioning as in case of disk
serial numbers).

However, we also expect bcache names to match names in MAAS which may
not happen in this scenario because  : bcache
mapping is not enforced.

Going back to https://bugs.launchpad.net/curtin/+bug/1728742, I think we
can break it down into two problems:

1. bcache device numbers are not static across reboots and we need a
static mapping of superblock UUID to bcache for a given device. This
requires CACHED_UUID to be present in uevent environment which is only
possible during a successful registration where this code path is
triggered. As a result of rootfs on bcache requirement, this makes sense
to do at the initrd stage before we have to do pivot_root to the real
rootfs.

Doing something like that when systemd is running post pivot_root and
/dev devtmpfs transfer to the real rootfs doesn't sound right to me as
we have this problem with double registration. In summary, I think
/dev/bcache/by-uuid/ symlinks for bcache devices that exist on initial
boot should be created via udev rules in initrd.

This is what this bug is about.

2. bcache device names may not match the ones in MAAS. This has
implications for our use of Juju Storage functionality when we need
device special files with static names without file systems or partition
tables present. After commissioning in MAAS there's already metadata
present about a given machine - disk serial numbers are gathered (if
present, this is not guaranteed and block driver-specific AFAIK but a
sane assumption to make) and device names that were assigned during
ephemeral image boot are presented and stored in a database with
associated serial numbers available for querying to set up dname
symlinks on deployment.

In order to make  : bcache mapping static we need
to essentially have a mapping of disk serial numbers to bcache
superblock UUIDs which are in turn mapped to bcache names.

I would say that https://bugs.launchpad.net/curtin/+bug/1728742 is about
p.2.



The rationale for p. 1 is that the init script sets up devtmpfs
initially which then gets moved over to the real rootfs (init-bottom
script) before pivot_root is performed. systemd then runs its mount
point set up code which checks if a given entry in its hard-coded table
of mount points is already a mount point and skips its setup if this is
the case. So anything set up during initrd stage will stay there after
systemd runs as devtmpfs is moved and reused.

https://git.launchpad.net/~usd-import-team/ubuntu/+source/systemd/tree/src/core/mount-setup.c?h=applied/ubuntu/xenial-updates#n77
  { "devtmpfs", "/dev", "devtmpfs", "mode=755", MS_NOSUID|MS_STRICTATIME,

path_is_mount_point -> fd_is_mount_point
https://git.launchpad.net/~usd-import-team/ubuntu/+source/systemd/tree/src/core/mount-setup.c?h=applied/ubuntu/xenial-updates#n161

static int mount_one(const MountPoint *p, bool relabel) {
...
r = path_is_mount_point(p->where, AT_SYMLINK_FOLLOW);
if (r < 0 && r != -ENOENT) {
log_full_errno((p->mode & MNT_FATAL) ? LOG_ERR : LOG_DEBUG, r, 
"Failed to determine whether %s is a mount point: %m", p->where);
return (p->mode & MNT_FATAL) ? r : 0;
}
if (r > 0)
return 0;


init script:
https://git.launchpad.net/~usd-import-team/ubuntu/+source/initramfs-tools/tree/init?h=applied/ubuntu/xenial-updates
[ -d /dev ] || mkdir -m 0755 /dev
...

# Note that this only becomes /dev on the real filesystem if udev's scripts
# are used; which they will be, but it's worth pointing out
if ! mount -t devtmpfs -o nosuid,mode=0755 udev /dev; then
 echo "W: devtmpfs not available, falling back to tmpfs for /dev"
 mount -t tmpfs -o nosuid,mode=0755 udev /dev
 [ -e /dev/console ] || mknod -m 0600 /dev/console c 5 1
 [ -e /dev/null ] || mknod /dev/null c 1 3
fi
...


init-bottom:
https://git.launchpad.net/~usd-import-team/ubuntu/+source/systemd/tree/debian/extra/initramfs-tools/scripts/init-bottom/udev?h=applied/ubuntu/xenial-updates

...
# move the /dev tmpfs to the rootfs
mount -n -o move /dev ${rootmnt}/dev

# create a temporary symlink to the final /dev for other initramfs scripts
if command -v nuke >/dev/null; then
  nuke /dev
else
  rm -rf /dev
fi
ln -s ${rootmnt}/dev /dev

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

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

[Dmitrii Shcherbakov]

Just to clarify on UUIDs - there are 3 types of UUIDs in question:

1. cache set UUIDs (upstream docs mention that multiple cache devices per cache 
set are not supported but a configuration with M:N as in 
: has been taken into account)
2. cache device superblock UUIDs;
3. backing device superblock UUIDs.

We are interested in uevents containing backing device superblock UUIDs
to reliably create by-uuid symlinks and, ideally, have persistent
/dev/bcache names based on those UUIDs (although the latter is out of
scope for this particular bug).

The following code in bcache-tools provides more clarity on how
suberblock UUIDs are generated in userspace:

https://github.com/g2p/bcache-tools/blob/v1.0.8/make-bcache.c#L448-L458 loops 
over cache devices and backing devices calling write_sb for each device
https://github.com/g2p/bcache-tools/blob/v1.0.8/make-bcache.c#L170-L174 
(write_sb which takes device type into account)
https://github.com/g2p/bcache-tools/blob/v1.0.8/make-bcache.c#L211-L221 - 
selects a type of suberblock which is either cache or backing device (cdev or 
bdev), writes bcache magic, generates a ***suberblock UUID***, writes a passed 
cache set UUID into in-memory suberblock representation along with block size 
and bucket size
https://github.com/g2p/bcache-tools/blob/v1.0.8/make-bcache.c#L284-L288 
(pwrites the in-memory representation to a given block device)

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

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

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

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

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

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

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

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

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

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

  then rootfs ismounted and systemd starts systemd-udev

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   

[Kernel-packages] [Bug 1728271] [NEW] drm/i915: Resetting chip after gpu hang

[Dmitrii Shcherbakov]

Public bug reported:

I wanted to test a snap application called clementine and opened up
preferences after it was launched and playing music. After clicking on
something my whole system hanged.

Regardless of the app, I decided to lookup how something like that could
manage to "kill" the whole system and make it completely unresponsive.

Device info is in the collected information attached. I am using NVIDIA
1060 as a primary graphics card.

I have persistent journald logging enabled so the kernel log was saved
up to a certain point.

The interesting part is here, too bad I could not get
/sys/class/drm/card1/error state:

окт 28 19:45:03 blade org.gnome.Nautilus[5312]: libGL error: MESA-LOADER: 
failed to retrieve device information
окт 28 19:45:03 blade kernel: kauditd_printk_skb: 6 callbacks suppressed
окт 28 19:45:03 blade kernel: audit: type=1400 audit(1509209103.252:186): 
apparmor="DENIED" operation="open" profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:
окт 28 19:45:03 blade kernel: audit: type=1400 audit(1509209103.252:187): 
apparmor="DENIED" operation="open" profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:
окт 28 19:45:03 blade kernel: audit: type=1400 audit(1509209103.252:188): 
apparmor="DENIED" operation="open" profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:
окт 28 19:45:03 blade kernel: audit: type=1400 audit(1509209103.252:189): 
apparmor="DENIED" operation="open" profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:
окт 28 19:45:03 blade kernel: audit: type=1400 audit(1509209103.252:190): 
apparmor="DENIED" operation="open" profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:
окт 28 19:45:03 blade kernel: audit: type=1400 audit(1509209103.252:191): 
apparmor="DENIED" operation="open" profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:
окт 28 19:45:03 blade kernel: audit: type=1400 audit(1509209103.252:192): 
apparmor="DENIED" operation="open" profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:
окт 28 19:45:03 blade kernel: audit: type=1400 audit(1509209103.252:193): 
apparmor="DENIED" operation="open" profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:
окт 28 19:45:03 blade org.gnome.Nautilus[5312]: libGL error: Version 4 or later 
of flush extension not found
окт 28 19:45:03 blade org.gnome.Nautilus[5312]: libGL error: failed to load 
driver: i915
окт 28 19:45:03 blade audit[13782]: AVC apparmor="DENIED" operation="open" 
profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:02.0/revision" pid=13782 comm="cle
окт 28 19:45:03 blade kernel: audit: type=1400 audit(1509209103.346:194): 
apparmor="DENIED" operation="open" profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:
окт 28 19:45:03 blade kernel: audit: type=1400 audit(1509209103.346:195): 
apparmor="DENIED" operation="open" profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:
окт 28 19:45:03 blade audit[13782]: AVC apparmor="DENIED" operation="open" 
profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:02.0/config" pid=13782 comm="cleme
окт 28 19:45:03 blade audit[13782]: AVC apparmor="DENIED" operation="open" 
profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:02.0/revision" pid=13782 comm="cle
окт 28 19:45:03 blade audit[13782]: AVC apparmor="DENIED" operation="open" 
profile="snap.clementine.clementine" 
name="/sys/devices/pci:00/:00:02.0/config" pid=13782 comm="cleme
окт 28 19:45:03 blade org.gnome.Nautilus[5312]: libGL error: MESA-LOADER: 
failed to retrieve device information
окт 28 19:45:03 blade gnome-shell[5472]: STACK_OP_ADD: window 0x4800095 already 
in stack
окт 28 19:45:03 blade gnome-shell[5472]: STACK_OP_ADD: window 0x4800095 already 
in stack
окт 28 19:45:03 blade org.gnome.Nautilus[5312]: [projectM] Allocating idle 
preset...
окт 28 19:45:03 blade org.gnome.Nautilus[5312]: [PresetFactory] path is Geiss & 
Sperl - Feedback (projectM idle HDR mix).milk
окт 28 19:45:03 blade org.gnome.Nautilus[5312]: [PresetFactory] url is 
idle://Geiss & Sperl - Feedback (projectM idle HDR mix).milk
окт 28 19:45:09 blade kernel: [drm] GPU HANG: ecode 9:0:0xefde, in 
clementine [13782], reason: Hang on rcs0, action: reset
окт 28 19:45:09 blade kernel: [drm] GPU hangs can indicate a bug anywhere in 
the entire gfx stack, including userspace.
окт 28 19:45:09 blade kernel: [drm] Please file a _new_ bug report on 
bugs.freedesktop.org against DRI -> DRM/Intel
окт 28 19:45:09 blade kernel: [drm] drm/i915 developers can then reassign to 
the right component if it's not a kernel issue.
окт 28 19:45:09 blade kernel: [drm] The gpu crash dump is required to analyze 
gpu hangs, so please always attach it.
окт 28 19:45:09 blade kernel: [drm] GPU crash dump saved to 
/sys/class/drm/card1/error
окт 28 19:45:09 blade 

[Kernel-packages] [Bug 1721835] Re: GPU HANG: ecode 9:0:0x96dbccee, in qtdemux0:sink [5106], reason: Hang on rcs0, action: reset

[Dmitrii Shcherbakov]

Haven't noticed that issue on previous kernels although I was mostly
using NVIDIA GPU not integrated intel GPU as in this case.

I will try to reproduce this on 4.14

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

Title:
   GPU HANG: ecode 9:0:0x96dbccee, in qtdemux0:sink [5106], reason: Hang
  on rcs0, action: reset

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

Bug description:
  окт 06 13:49:20 blade kernel: asynchronous wait on fence 
i915:gnome-shell[2505]/1:42b timed out
  окт 06 13:49:21 blade kernel: [drm] GPU HANG: ecode 9:0:0x96dbccee, in 
qtdemux0:sink [5106], reason: Hang on rcs0, action: reset
  окт 06 13:49:21 blade kernel: [drm] GPU hangs can indicate a bug anywhere in 
the entire gfx stack, including userspace.
  окт 06 13:49:21 blade kernel: [drm] Please file a _new_ bug report on 
bugs.freedesktop.org against DRI -> DRM/Intel
  окт 06 13:49:21 blade kernel: [drm] drm/i915 developers can then reassign to 
the right component if it's not a kernel issue.
  окт 06 13:49:21 blade kernel: [drm] The gpu crash dump is required to analyze 
gpu hangs, so please always attach it.
  окт 06 13:49:21 blade kernel: [drm] GPU crash dump saved to 
/sys/class/drm/card1/error
  окт 06 13:49:21 blade kernel: drm/i915: Resetting chip after gpu hang
  окт 06 13:49:21 blade kernel: [drm] RC6 on

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1838 F pulseaudio
dima   2514 F pulseaudio
  Date: Fri Oct  6 13:49:59 2017
  InstallationDate: Installed on 2017-02-27 (221 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1532:0224 Razer USA, Ltd 
   Bus 001 Device 003: ID 0bda:579f Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open pcie_aspm=off ath10k_core.debug_mask=0x4041
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-09-13 (22 days ago)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.family: 1A586755
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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

[Kernel-packages] [Bug 1721835] Re: GPU HANG: ecode 9:0:0x96dbccee, in qtdemux0:sink [5106], reason: Hang on rcs0, action: reset

[Dmitrii Shcherbakov]

Haven't noticed that issue on previous kernels although I was mostly
using NVIDIA GPU not integrated intel GPU as in this case.

I will try to reproduce this on 4.14

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

Title:
   GPU HANG: ecode 9:0:0x96dbccee, in qtdemux0:sink [5106], reason: Hang
  on rcs0, action: reset

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

Bug description:
  окт 06 13:49:20 blade kernel: asynchronous wait on fence 
i915:gnome-shell[2505]/1:42b timed out
  окт 06 13:49:21 blade kernel: [drm] GPU HANG: ecode 9:0:0x96dbccee, in 
qtdemux0:sink [5106], reason: Hang on rcs0, action: reset
  окт 06 13:49:21 blade kernel: [drm] GPU hangs can indicate a bug anywhere in 
the entire gfx stack, including userspace.
  окт 06 13:49:21 blade kernel: [drm] Please file a _new_ bug report on 
bugs.freedesktop.org against DRI -> DRM/Intel
  окт 06 13:49:21 blade kernel: [drm] drm/i915 developers can then reassign to 
the right component if it's not a kernel issue.
  окт 06 13:49:21 blade kernel: [drm] The gpu crash dump is required to analyze 
gpu hangs, so please always attach it.
  окт 06 13:49:21 blade kernel: [drm] GPU crash dump saved to 
/sys/class/drm/card1/error
  окт 06 13:49:21 blade kernel: drm/i915: Resetting chip after gpu hang
  окт 06 13:49:21 blade kernel: [drm] RC6 on

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1838 F pulseaudio
dima   2514 F pulseaudio
  Date: Fri Oct  6 13:49:59 2017
  InstallationDate: Installed on 2017-02-27 (221 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1532:0224 Razer USA, Ltd 
   Bus 001 Device 003: ID 0bda:579f Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open pcie_aspm=off ath10k_core.debug_mask=0x4041
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-09-13 (22 days ago)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.family: 1A586755
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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

[Kernel-packages] [Bug 1721835] [NEW] GPU HANG: ecode 9:0:0x96dbccee, in qtdemux0:sink [5106], reason: Hang on rcs0, action: reset

[Dmitrii Shcherbakov]

Public bug reported:

окт 06 13:49:20 blade kernel: asynchronous wait on fence 
i915:gnome-shell[2505]/1:42b timed out
окт 06 13:49:21 blade kernel: [drm] GPU HANG: ecode 9:0:0x96dbccee, in 
qtdemux0:sink [5106], reason: Hang on rcs0, action: reset
окт 06 13:49:21 blade kernel: [drm] GPU hangs can indicate a bug anywhere in 
the entire gfx stack, including userspace.
окт 06 13:49:21 blade kernel: [drm] Please file a _new_ bug report on 
bugs.freedesktop.org against DRI -> DRM/Intel
окт 06 13:49:21 blade kernel: [drm] drm/i915 developers can then reassign to 
the right component if it's not a kernel issue.
окт 06 13:49:21 blade kernel: [drm] The gpu crash dump is required to analyze 
gpu hangs, so please always attach it.
окт 06 13:49:21 blade kernel: [drm] GPU crash dump saved to 
/sys/class/drm/card1/error
окт 06 13:49:21 blade kernel: drm/i915: Resetting chip after gpu hang
окт 06 13:49:21 blade kernel: [drm] RC6 on

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-12-generic 4.13.0-12.13
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1838 F pulseaudio
  dima   2514 F pulseaudio
Date: Fri Oct  6 13:49:59 2017
InstallationDate: Installed on 2017-02-27 (221 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 1532:0224 Razer USA, Ltd 
 Bus 001 Device 003: ID 0bda:579f Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Razer Blade
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open pcie_aspm=off ath10k_core.debug_mask=0x4041
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-12-generic N/A
 linux-backports-modules-4.13.0-12-generic  N/A
 linux-firmware 1.168
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-09-13 (22 days ago)
dmi.bios.date: 01/10/2017
dmi.bios.vendor: Razer
dmi.bios.version: 1.00
dmi.board.name: Razer
dmi.board.vendor: Razer
dmi.chassis.type: 9
dmi.chassis.vendor: Razer
dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
dmi.product.family: 1A586755
dmi.product.name: Blade
dmi.product.version: 6.06
dmi.sys.vendor: Razer

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


** Tags: amd64 apport-bug artful

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

Title:
   GPU HANG: ecode 9:0:0x96dbccee, in qtdemux0:sink [5106], reason: Hang
  on rcs0, action: reset

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  окт 06 13:49:20 blade kernel: asynchronous wait on fence 
i915:gnome-shell[2505]/1:42b timed out
  окт 06 13:49:21 blade kernel: [drm] GPU HANG: ecode 9:0:0x96dbccee, in 
qtdemux0:sink [5106], reason: Hang on rcs0, action: reset
  окт 06 13:49:21 blade kernel: [drm] GPU hangs can indicate a bug anywhere in 
the entire gfx stack, including userspace.
  окт 06 13:49:21 blade kernel: [drm] Please file a _new_ bug report on 
bugs.freedesktop.org against DRI -> DRM/Intel
  окт 06 13:49:21 blade kernel: [drm] drm/i915 developers can then reassign to 
the right component if it's not a kernel issue.
  окт 06 13:49:21 blade kernel: [drm] The gpu crash dump is required to analyze 
gpu hangs, so please always attach it.
  окт 06 13:49:21 blade kernel: [drm] GPU crash dump saved to 
/sys/class/drm/card1/error
  окт 06 13:49:21 blade kernel: drm/i915: Resetting chip after gpu hang
  окт 06 13:49:21 blade kernel: [drm] RC6 on

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1838 F pulseaudio
dima   2514 F pulseaudio
  Date: Fri Oct  6 13:49:59 2017
  InstallationDate: Installed on 2017-02-27 (221 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1532:0224 Razer USA, Ltd 
   Bus 001 Device 003: 

[Kernel-packages] [Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Dmitrii Shcherbakov]

Gathering more evidence in support of a faulty motherboard theory.

At some point I got this (system wasn't under heavy load - just a
browser opened + remote video playback):

https://gist.github.com/dshcherb/06f4e4a0260b6d5313df1594d959849a#file-
nvme-failure-razer-dmesg-log-L2073


сен 10 22:23:39 blade kernel: nvme nvme0: I/O 916 QID 3 timeout, aborting
сен 10 22:23:39 blade kernel: nvme nvme0: I/O 917 QID 3 timeout, aborting
сен 10 22:23:39 blade kernel: nvme nvme0: I/O 918 QID 3 timeout, aborting
сен 10 22:23:39 blade kernel: nvme nvme0: I/O 919 QID 3 timeout, aborting
сен 10 22:23:45 blade kernel: nvme nvme0: I/O 920 QID 3 timeout, aborting
сен 10 22:23:55 blade kernel: nvme nvme0: I/O 921 QID 3 timeout, aborting
сен 10 22:24:10 blade kernel: nvme nvme0: I/O 916 QID 3 timeout, reset 
controller
сен 10 22:24:39 blade kernel: nvme nvme0: I/O 11 QID 0 timeout, reset controller
сен 10 22:25:42 blade kernel: nvme nvme0: Device not ready; aborting reset

So the kernel tried to reset a controller after a timeout which is
normal and could not do so after 100ms => aborted reset.

http://elixir.free-
electrons.com/linux/v4.13/source/drivers/nvme/host/core.c#L1378

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

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Disabled a wireless adapter via NetworkManager. Got a kernel trace in
  dmesg.

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
  Network Adapter (rev 32)

  uname -r
  4.10.0-9-generic

  https://paste.ubuntu.com/24131142/

  There are also usb hot-plug messages in between ath10k related ones -
  this is because I disabled a wireless adapter and immediately plugged
  in a usb type-c dock so don't mind those.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-9-generic 4.10.0-9.11
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dima   3007 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar  7 17:28:37 2017
  InstallationDate: Installed on 2017-02-27 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-9-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open pcie_aspm=off
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-9-generic N/A
   linux-backports-modules-4.10.0-9-generic  N/A
   linux-firmware1.163
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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

[Kernel-packages] [Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Dmitrii Shcherbakov]

Sorry, I should have mentioned that before: in the original test I also
had a device plugged in via usb type-c (thunderbolt 3) - that device had
an ethernet interface which you can see in the logs. It's another
problem that I need to debug because type-c hot-plug of that device
worked once but successive attempts did not (no devices were attached) -
will try that on 4.13 but not in the scope of this thread.

I think we can safely ignore ax88179_178a for now:

мар 07 17:23:47 blade kernel: ax88179_178a 4-1.1:1.0 eth0: register
'ax88179_178a' at usb-:10:00.0-1.1, ASIX AX88179 USB 3.0 Gigabit
Ethernet, 00:05:6b:00:6a:d7

Regarding hid-rmi - I have not encountered visible problems with a
touchpad or keyboard after restore (or have not noticed them).

The original log messages were on suspend:

[18433.618894] PM: Suspending system (mem)
[18433.618956] Suspending console(s) (use no_console_suspend to debug)
[18434.736072] hid-rmi 0018:06CB:5F41.0005: rmi_read_block: timeout elapsed
[18435.760072] hid-rmi 0018:06CB:5F41.0005: rmi_read_block: timeout elapsed
[18436.784071] hid-rmi 0018:06CB:5F41.0005: rmi_read_block: timeout elapsed
[18437.808071] hid-rmi 0018:06CB:5F41.0005: rmi_read_block: timeout elapsed
[18438.832072] hid-rmi 0018:06CB:5F41.0005: rmi_read_block: timeout elapsed
[18438.832076] hid-rmi 0018:06CB:5F41.0005: can not read F11 control registers
[18439.041909] pcieport :03:02.0: Refused to change power state, currently 
in D3
[18439.041917] pcieport :03:00.0: Refused to change power state, currently 
in D3
[18439.168298] ACPI : EC: event blocked
[18439.377161] PM: suspend of devices complete after 5653.226 msecs
[18439.399735] PM: late suspend of devices complete after 22.568 msecs

After systemctl suspend and resume on 4.13:

http://paste.ubuntu.com/25505431/
http://paste.ubuntu.com/25505433/ (full dmesg)
[132638.096488] PM: Suspending system (mem)
[132638.096517] Suspending console(s) (use no_console_suspend to debug)
[132639.666295] PM: suspend of devices complete after 1356.062 msecs
[132639.689669] PM: late suspend of devices complete after 23.366 msecs
[132639.774466] PM: noirq suspend of devices complete after 84.791 msecs
...

---

So, I think both of those may be ignored for now.

** Attachment added: "type-c-device-razer-core.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+attachment/4947391/+files/type-c-device-razer-core.png

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

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Disabled a wireless adapter via NetworkManager. Got a kernel trace in
  dmesg.

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
  Network Adapter (rev 32)

  uname -r
  4.10.0-9-generic

  https://paste.ubuntu.com/24131142/

  There are also usb hot-plug messages in between ath10k related ones -
  this is because I disabled a wireless adapter and immediately plugged
  in a usb type-c dock so don't mind those.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-9-generic 4.10.0-9.11
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dima   3007 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar  7 17:28:37 2017
  InstallationDate: Installed on 2017-02-27 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-9-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open pcie_aspm=off
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-9-generic N/A
   linux-backports-modules-4.10.0-9-generic  N/A
   linux-firmware1.163
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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

[Kernel-packages] [Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))

[Dmitrii Shcherbakov]

I will try 2 things:

1. re-seat the card

2. get a card from a different manufacturer and test.

It might be a buggy slot in the motherboard and if the problem persists
with a new card I will know for sure that the slot is defective.

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

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros
  QCA6174 802.11ac (rev 32))

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Disabled a wireless adapter via NetworkManager. Got a kernel trace in
  dmesg.

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
  Network Adapter (rev 32)

  uname -r
  4.10.0-9-generic

  https://paste.ubuntu.com/24131142/

  There are also usb hot-plug messages in between ath10k related ones -
  this is because I disabled a wireless adapter and immediately plugged
  in a usb type-c dock so don't mind those.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-9-generic 4.10.0-9.11
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dima   3007 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar  7 17:28:37 2017
  InstallationDate: Installed on 2017-02-27 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-9-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open pcie_aspm=off
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-9-generic N/A
   linux-backports-modules-4.10.0-9-generic  N/A
   linux-firmware1.163
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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