[Kernel-packages] [Bug 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008

2022-07-19 Thread lilideng
We didn't have repro steps; customers encounter this in some rate. So we
can't verify the commit.

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

Title:
  BUG: kernel NULL pointer dereference, address: 0008

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.4 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-hwe-5.4 source package in Bionic:
  Confirmed

Bug description:
  Hi,

  On one of the main US Ubuntu Archive servers (banjo), we decided to
  reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so,
  ran into this kernel panic:

  | [  350.776585] BUG: kernel NULL pointer dereference, address: 
0008
  | [  350.783674] #PF: supervisor read access in kernel mode
  | [  350.788846] #PF: error_code(0x) - not-present page
  | [  350.794019] PGD 0 P4D 0
  | [  350.796631] Oops:  [#1] SMP NOPTI
  | [  350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic 
#138~18.04.1-Ubuntu
  | [  350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 
Gen10, BIOS A40 02/10/2022
  | [  350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0
  | [  350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 
00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 
40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83
  | [  350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246
  | [  350.847324] RAX:  RBX: 897618739c80 RCX: 
0007
  | [  350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 
897605c85580
  | [  350.861682] RBP: 9a958cce8878 R08: 0178 R09: 
89763e407800
  | [  350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 
897607afb0b0
  | [  350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 
89762688b400
  | [  350.883219] FS:  () GS:89763ec0() 
knlGS:
  | [  350.891358] CS:  0010 DS:  ES:  CR0: 80050033
  | [  350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 
00340ee0
  | [  350.904319] Call Trace:
  | [  350.906787]  
  | [  350.908824]  tcp_v6_syn_recv_sock+0x8d/0x710
  | [  350.913259]  ? ip6_route_output_flags_noref+0xd0/0x110
  | [  350.918435]  tcp_get_cookie_sock+0x48/0x140
  | [  350.922688]  cookie_v6_check+0x5a2/0x700
  | [  350.926714]  tcp_v6_do_rcv+0x36c/0x3e0
  | [  350.930589]  ? tcp_v6_do_rcv+0x36c/0x3e0
  | [  350.934589]  tcp_v6_rcv+0xa16/0xa60
  | [  350.938102]  ip6_protocol_deliver_rcu+0xd8/0x4d0
  | [  350.942750]  ip6_input+0x41/0xb0
  | [  350.946000]  ip6_sublist_rcv_finish+0x42/0x60
  | [  350.950385]  ip6_sublist_rcv+0x235/0x260
  | [  350.954333]  ? __netif_receive_skb_core+0x19d/0xc60
  | [  350.959245]  ipv6_list_rcv+0x110/0x140
  | [  350.963018]  __netif_receive_skb_list_core+0x157/0x260
  | [  350.968192]  ? build_skb+0x17/0x80
  | [  350.971615]  netif_receive_skb_list_internal+0x187/0x2a0
  | [  350.976961]  gro_normal_list.part.131+0x1e/0x40
  | [  350.981519]  napi_complete_done+0x94/0x120
  | [  350.985700]  mlx5e_napi_poll+0x178/0x630 [mlx5_core]
  | [  350.990697]  net_rx_action+0x140/0x3e0
  | [  350.994475]  __do_softirq+0xe4/0x2da
  | [  350.998079]  irq_exit+0xae/0xb0
  | [  351.001239]  do_IRQ+0x59/0xe0
  | [  351.004228]  common_interrupt+0xf/0xf
  | [  351.007913]  
  | [  351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440
  | [  351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 
00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 
ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4
  | [  351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: 
ffd6
  | [  351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 
001f
  | [  351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: 

  | [  351.055997] RBP: 9a958026fe88 R08: 0002 R09: 
0002f680
  | [  351.063176] R10: 9a958026fe18 R11: 0115 R12: 
8976274c3800
  | [  351.070355] R13: 0001 R14: 84b66bb8 R15: 
0051abe96150
  | [  351.077540]  ? cpuidle_enter_state+0x98/0x440
  | [  351.081930]  ? menu_select+0x377/0x600
  | [  351.085706]  cpuidle_enter+0x2e/0x40
  | [  351.089310]  call_cpuidle+0x23/0x40
  | [  351.092821]  do_idle+0x1f6/0x270
  | [  351.096069]  cpu_startup_entry+0x1d/0x20
  | [  351.100024]  start_secondary+0x166/0x1c0
  | [  351.103977]  secondary_startup_64+0xa4/0xb0
  | [  351.108186] Modules linked in: binfmt_misc bonding nls_iso8859_1 
ipmi_ssif edac_mce_amd kvm_amd kvm hpilo ccp ipmi_si ipmi_devintf 
ipmi_msghandler acpi_tad k10temp mac_hid acpi_power_meter sch_fq tcp_bbr 
ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi 

[Kernel-packages] [Bug 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008

2022-07-19 Thread lilideng
we also see this issue on azure ubuntu 1804, kernel version is
5.4.0-1086-azure

[  823.785727] BUG: kernel NULL pointer dereference, address: 0008
[  823.791661] #PF: supervisor read access in kernel mode
[  823.791661] #PF: error_code(0x) - not-present page
[  823.798898] PGD 0 P4D 0
[  823.798898] Oops:  [#1] SMP PTI
[  823.798898] CPU: 21 PID: 0 Comm: swapper/21 Not tainted 5.4.0-1086-azure 
#91~18.04.1-Ubuntu
[  823.798898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090008  12/07/2018
[  823.798898] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0
[  823.798898] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 
00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 
08 e8 b6 81 4b 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83
[  823.798898] RSP: 0018:bcee00510950 EFLAGS: 00010246
[  823.798898] RAX:  RBX: 9e64f0c53d40 RCX: 0007
[  823.798898] RDX: 0020 RSI: 9e6cd950fb60 RDI: 9e6ccf8d3480
[  823.798898] RBP: bcee00510970 R08:  R09: 9e6d19007800
[  823.798898] R10: 0514 R11: bcee00510a37 R12: 9e6cd950fb60
[  823.798898] R13: 9e6ccf8d3480 R14: 9e6cd7c1e200 R15: 9e6d1305e600
[  823.798898] FS:  () GS:9e6d1f94() 
knlGS:
[  823.798898] CS:  0010 DS:  ES:  CR0: 80050033
[  823.798898] CR2: 0008 CR3: 00105216e004 CR4: 003706e0
[  823.798898] DR0:  DR1:  DR2: 
[  823.798898] DR3:  DR6: fffe0ff0 DR7: 0400
[  823.798898] Call Trace:
[  823.798898]  
[  823.798898]  tcp_v4_syn_recv_sock+0x5a/0x3d0
[  823.798898]  tcp_get_cookie_sock+0x48/0x140
[  823.798898]  cookie_v4_check+0x561/0x660
[  823.798898]  tcp_v4_do_rcv+0x1a0/0x1d0
[  823.956063]  tcp_v4_rcv+0xa86/0xad0
[  823.956063]  ip_protocol_deliver_rcu+0x31/0x1b0
[  823.956063]  ip_local_deliver_finish+0x48/0x50
[  823.956063]  ip_local_deliver+0x7e/0xe0
[  823.956063]  ? ip_protocol_deliver_rcu+0x1b0/0x1b0
[  823.956063]  ip_sublist_rcv_finish+0x42/0x60
[  823.956063]  ip_sublist_rcv+0x239/0x270
[  823.956063]  ? ip_rcv_finish_core.isra.18+0x3b0/0x3b0
[  823.956063]  ip_list_rcv+0x10d/0x130
[  823.956063]  __netif_receive_skb_list_core+0x23e/0x260
[  823.956063]  netif_receive_skb_list_internal+0x17a/0x290
[  823.956063]  gro_normal_list.part.132+0x1e/0x40
[  823.956063]  napi_complete_done+0x94/0x110
[  823.956063]  mlx5e_napi_poll+0x178/0x630 [mlx5_core]
[  823.956063]  net_rx_action+0x134/0x3c0
[  823.956063]  __do_softirq+0xde/0x2ce
[  823.956063]  irq_exit+0xd7/0xe0
[  823.956063]  hyperv_vector_handler+0x63/0x70
[  823.956063]  hyperv_callback_vector+0xf/0x20
[  823.956063]  
[  823.956063] RIP: 0010:default_idle+0x2b/0x150
[  823.956063] Code: 1f 44 00 00 55 48 89 e5 41 56 41 55 41 54 53 65 44 8b 25 
58 85 1c 4e 0f 1f 44 00 00 0f 1f 44 00 00 0f 00 2d 79 99 5b 00 fb f4 <65> 44 8b 
25 3d 85 1c 4e 0f 1f 44 00 00 5b 41 5c 41 5d 41 5e 5d c3
[  823.956063] RSP: 0018:bcee0011be78 EFLAGS: 0246 ORIG_RAX: 
ff0c
[  823.956063] RAX: b1e4cde0 RBX: 0015 RCX: 0001
[  823.956063] RDX: 0015 RSI: bcee0011be58 RDI: 
[  823.956063] RBP: bcee0011be98 R08: 0006 R09: 00fca75c93534208
[  823.956063] R10: bcee0011be38 R11: 0013b454 R12: 0015
[  823.956063] R13:  R14:  R15: fff0
[  823.956063]  ? __sched_text_end+0x2/0x2
[  824.148152]  arch_cpu_idle+0x15/0x20
[  824.148152]  default_idle_call+0x26/0x30
[  824.148152]  do_idle+0x1d7/0x2a0
[  824.148152]  cpu_startup_entry+0x1d/0x20
[  824.148152]  start_secondary+0x159/0x1b0
[  824.148152]  secondary_startup_64+0xa4/0xb0
[  824.148152] Modules linked in: tcp_diag inet_diag nfnetlink_queue ipt_REJECT 
nf_reject_ipv4 xt_mark xt_comment xt_NFQUEUE iptable_mangle xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat xt_addrtype 
iptable_filter nf_nat br_netfilter bridge stp llc aufs overlay xt_tcpudp 
xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 iptable_security 
nf_defrag_ipv4 bpfilter mlx5_ib ib_uverbs mlx5_core tls mlxfw udf crc_itu_t 
nls_iso8859_1 isst_if_mbox_msr isst_if_common kvm_intel kvm hv_balloon rapl 
serio_raw joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel hid_generic aesni_intel crypto_simd hid_hyperv 
cryptd pata_acpi hid glue_helper hyperv_fb hv_netvsc hyperv_keyboard hv_utils
[  824.148152] CR2: 0008
[  824.148151] BUG: kernel NULL pointer dereference, address: 

[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22

2022-06-09 Thread lilideng
below kernels on azure have this issue. please hold on the new images which 
contain these kernel releases. thanks.
focal/linux-azure-5.13: 5.13.0-1026-azure
focal/linux-azure-5.15: 5.15.0-1008-azure

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

Title:
  Docker container creation causes kernel oops on linux-aws
  5.13.0.1028.31~20.04.22

Status in linux-aws-5.13 package in Ubuntu:
  Confirmed
Status in linux-azure-5.13 package in Ubuntu:
  Confirmed
Status in linux-gcp-5.13 package in Ubuntu:
  Confirmed
Status in linux-intel-iotg-5.15 package in Ubuntu:
  Confirmed
Status in linux-oracle-5.13 package in Ubuntu:
  Confirmed
Status in linux-aws-5.13 source package in Focal:
  In Progress
Status in linux-azure-5.13 source package in Focal:
  In Progress
Status in linux-gcp-5.13 source package in Focal:
  Confirmed
Status in linux-intel-iotg-5.15 source package in Focal:
  Confirmed
Status in linux-oracle-5.13 source package in Focal:
  Confirmed

Bug description:
  Running the attached script on the latest AWS AMI for Ubuntu 20.04, I
  get a kernel panic and hard reset of the node.

  [   12.314552] VFS: Close: file count is 0
  [   12.351090] [ cut here ]
  [   12.351093] kernel BUG at include/linux/fs.h:3104!
  [   12.355272] invalid opcode:  [#1] SMP PTI
  [   12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws 
#31~20.04.1-Ubuntu
  [   12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017
  [   12.371130] RIP: 0010:__fput+0x247/0x250
  [   12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff 
e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 
1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48
  [   12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246
  [   12.393425] RAX:  RBX: 000a801d RCX: 
9152e0716000
  [   12.398679] RDX: 9152cf075280 RSI: 0001 RDI: 

  [   12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 
9152dfcba2c8
  [   12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 
9152d04e9d00
  [   12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 
9152dfc2e180
  [   12.419533] FS:  () GS:9153ea90() 
knlGS:
  [   12.426937] CS:  0010 DS:  ES:  CR0: 80050033
  [   12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 
007706e0
  [   12.436716] DR0:  DR1:  DR2: 

  [   12.441941] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   12.447170] PKRU: 5554
  [   12.450355] Call Trace:
  [   12.453408]  
  [   12.456296]  fput+0xe/0x10
  [   12.459633]  task_work_run+0x70/0xb0
  [   12.463157]  do_exit+0x37b/0xaf0
  [   12.466570]  do_group_exit+0x43/0xb0
  [   12.470142]  __x64_sys_exit_group+0x18/0x20
  [   12.473989]  do_syscall_64+0x61/0xb0
  [   12.477565]  ? exit_to_user_mode_prepare+0x9b/0x1c0
  [   12.481734]  ? do_user_addr_fault+0x1d0/0x650
  [   12.485665]  ? irqentry_exit_to_user_mode+0x9/0x20
  [   12.489790]  ? irqentry_exit+0x19/0x30
  [   12.493443]  ? exc_page_fault+0x8f/0x170
  [   12.497199]  ? asm_exc_page_fault+0x8/0x30
  [   12.501013]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   12.505289] RIP: 0033:0x7f80d42a1bd6
  [   12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac.
  [   12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 
00e7
  [   12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 
7f80d42a1bd6
  [   12.526115] RDX:  RSI: 003c RDI: 

  [   12.531328] RBP:  R08: 00e7 R09: 
fe98
  [   12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 
7f80d45a4740
  [   12.541687] R13: 0002 R14: 7f80d45ad708 R15: 

  [   12.546916]  
  [   12.549829] Modules linked in: xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c 
bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul 
ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc 
input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr 
drm ip_tables x_tables autofs4
  [   12.583913] ---[ end trace 77367fed4d782aa4 ]---
  [   12.587963] RIP: 0010:__fput+0x247/0x250
  [   12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff 
e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 
1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48
  [   12.605796] RSP: 

[Kernel-packages] [Bug 1755999] Re: Reproducible hang in generic/430 with xfstest from upstream

2021-07-22 Thread lilideng
generic/430 still hung on ubuntu 18.04 on azure, kernel version is
5.4.0-1055-azure, file system type is xfs.

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

Title:
  Reproducible hang in generic/430 with xfstest from upstream

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in xfsprogs package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in xfsprogs source package in Bionic:
  New

Bug description:
  While testing the latest xfstest from upstream, the generic/430 test
  will hang, no matter using ext4/xfs/btrfs.

  It looks like this issue was caused by the following command to copy beyond 
the file:
  /usr/sbin/xfs_io -i -f -c "copy_range -s 4000 -l 2000 
/home/ubuntu/test/test-430/file" "/home/ubuntu/test/test-430/beyond"

  The copied file will have a correct MD5 as expected.
  e68d4a150c4e42f4f9ea3ffe4c9cf4ed  beyond

  But the command will never return.

  The file size of test-430/file is 5000, so a copy_range call with
  source offset 4000 with length 1000 works, but > 1000 does not.

  Steps:
   1. Deploy a node with Bionic (should have a /dev/sdb available for the test)
   2. Run:
  sudo apt-get install git python-minimal -y
  git clone --depth=1 
https://github.com/Cypresslin/autotest-client-tests.git -b 
kteam-xfstest-upstream
  git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
  rm -fr autotest/client/tests
  ln -sf ~/autotest-client-tests autotest/client/tests
   3. Run the test with the following command:
  AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose autotest/client/tests/

  (The test suite can be built manually, but it's easier to do this with
  autotest framework)

  To run this test solely after the test partition has been creation on 
/dev/sdb:
  mkdir /home/ubuntu/test
  cd autotest/client/tmp/xfstests/src/xfstests-bld/xfstests-dev
  sudo su
  export TEST_DIR=/home/ubuntu/test
  export TEST_DEV=/dev/sdb1
  ./check generic/430

  Tested with the latest mainline kernel, 4.16.0-041600rc5-generic, and
  the bug still exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11 [modified: 
boot/vmlinuz-4.15.0-10-generic]
  ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1148 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1148 F pulseaudio
  Date: Thu Mar 15 14:24:46 2018
  InstallationDate: Installed on 2018-03-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  MachineType: Dell Inc. Dell Precision M3800
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d1980d27-9063-4d92-aa10-1fb240453d8d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/14/2014:svnDellInc.:pnDellPrecisionM3800:pvrA07:rvnDellInc.:rnDellPrecisionM3800:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1755999/+subscriptions


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


[Kernel-packages] [Bug 1882624] Re: nested kvm doesn't work

2020-08-30 Thread lilideng
Hi Marcelo, it works without -cpu host

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

Title:
  nested kvm doesn't work

Status in linux-azure package in Ubuntu:
  New

Bug description:
  Create VM on Azure using Canonical UbuntuServer 14.04.5-LTS latest
  using size Standard E4s v3

  Enable private-ppa canonical-kernel-esm

  Install kernel linux-azure, reboot VM, kernel version
  4.15.0-1084-azure

  Install qemu-kvm, download
  https://eosgnestedstorage.blob.core.windows.net/images/nested-
  ubuntu-4.15.0-23-generic.qcow2

  Launch nested VM using command qemu-system-x86_64 -smp 2 -m 2048 -hda
  /mnt/resource/nested.qcow2 -display none -device e1000,netdev=user.0
  -netdev user,id=user.0,hostfwd=tcp::60022-:22 -enable-kvm -daemonize

  Expected ssh -p 60022 nesteduser@localhost will ask password to login

  We can't connect to it, see below call trace in dmesg
 qemu-kvm version doesn't change after kernel upgraded. 
   
 2.0.0+dfsg-2ubuntu1.46
  [   53.420589] hv_balloon: Max. dynamic memory size: 32768 MB
  [   60.928772] L1TF CPU bug present and SMT on, data leak possible. See 
CVE-2018-3646 and 
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for 
details.
  [   60.940895] kvm: SMP vm created on host with unstable TSC; guest TSC will 
not be reliable
  [   60.967454] BUG: unable to handle kernel paging request at 56b8
  [   60.971140] IP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel]
  [   60.971140] PGD 0 P4D 0
  [   60.971140] Oops:  [#1] SMP PTI
  [   60.971140] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner 
iptable_security xt_conntrack nf_conntrack libcrc32c ip_tables x_tables udf 
crc_itu_t dm_crypt joydev hid_generic kvm_intel kvm irqbypass hid_hyperv hid 
hyperv_keyboard hv_balloon serio_raw crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
hyperv_fb cfbfillrect pata_acpi cfbimgblt cfbcopyarea hv_netvsc hv_utils
  [   60.971140] CPU: 2 PID: 1903 Comm: qemu-system-x86 Not tainted 
4.15.0-1084-azure #94~14.04.1-Ubuntu
  [   60.971140] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   60.971140] RIP: 0010:vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel]
  [   60.971140] RSP: 0018:a44847a53cc0 EFLAGS: 00010002
  [   60.971140] RAX:  RBX:  RCX: 

  [   61.020070] RDX: 6c14 RSI:  RDI: 

  [   61.020070] RBP: a44847a53d10 R08:  R09: 

  [   61.020070] R10:  R11:  R12: 

  [   61.020070] R13:  R14:  R15: 

  [   61.020070] FS:  7f753bba4700() GS:8fefdd68() 
knlGS:
  [   61.020070] CS:  0010 DS:  ES:  CR0: 80050033
  [   61.020070] CR2: 56b8 CR3: 000888c42005 CR4: 
003726e0
  [   61.020070] Call Trace:
  [   61.020070]  vcpu_enter_guest+0x909/0x12a0 [kvm]
  [   61.020070]  kvm_arch_vcpu_ioctl_run+0x2d8/0x3f0 [kvm]
  [   61.020070]  kvm_vcpu_ioctl+0x2a8/0x630 [kvm]
  [   61.020070]  ? dequeue_signal+0x3e/0x160
  [   61.020070]  ? do_sigtimedwait+0xbd/0x210
  [   61.020070]  ? copy_siginfo_to_user+0x12e/0x2d0
  [   61.020070]  do_vfs_ioctl+0x9b/0x5f0
  [   61.020070]  ? SyS_futex+0x71/0x150
  [   61.020070]  SyS_ioctl+0x79/0x90
  [   61.020070]  ? _copy_to_user+0x26/0x40
  [   61.020070]  do_syscall_64+0x80/0x1e0
  [   61.020070]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [   61.020070] RIP: 0033:0x7f7545f34ea7
  [   61.020070] RSP: 002b:7f753bba3bd8 EFLAGS: 0246 ORIG_RAX: 
0010
  [   61.020070] RAX: ffda RBX: 7f754bbed000 RCX: 
7f7545f34ea7
  [   61.020070] RDX:  RSI: ae80 RDI: 
000c
  [   61.020070] RBP: 55c68fd7f160 R08:  R09: 
0002
  [   61.020070] R10: 0008 R11: 0246 R12: 

  [   61.020070] R13:  R14: 7f753bba49c0 R15: 
55c68ee809a0
  [   61.020070] Code: 31 ed 45 31 f6 45 31 ff 0f 20 d0 48 89 81 e0 02 00 00 31 
c0 31 db 31 c9 31 d2 31 f6 31 ff 31 ed 5d 5a f6 05 0c c0 01 00 10 74 1b <48> 8b 
81 b8 56 00 00 48 8b 40 40 48 8b 80 08 08 00 00 f6 c4 01
  [   61.020070] RIP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] RSP: a44847a53cc0
  [   61.020070] CR2: 56b8
  [   61.020070] ---[ end trace ab52be3a09d557f5 ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1882624/+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 1882624] Re: nested kvm doesn't work

2020-07-24 Thread lilideng
The issue still exist on 4.15.0-1092-azure, probably I just verify the
basic nested vm scenario against 4.15.0-1091-azure, will double check.

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

Title:
  nested kvm doesn't work

Status in linux-azure package in Ubuntu:
  New

Bug description:
  Create VM on Azure using Canonical UbuntuServer 14.04.5-LTS latest
  using size Standard E4s v3

  Enable private-ppa canonical-kernel-esm

  Install kernel linux-azure, reboot VM, kernel version
  4.15.0-1084-azure

  Install qemu-kvm, download
  https://eosgnestedstorage.blob.core.windows.net/images/nested-
  ubuntu-4.15.0-23-generic.qcow2

  Launch nested VM using command qemu-system-x86_64 -smp 2 -m 2048 -hda
  /mnt/resource/nested.qcow2 -display none -device e1000,netdev=user.0
  -netdev user,id=user.0,hostfwd=tcp::60022-:22 -enable-kvm -daemonize

  Expected ssh -p 60022 nesteduser@localhost will ask password to login

  We can't connect to it, see below call trace in dmesg
 qemu-kvm version doesn't change after kernel upgraded. 
   
 2.0.0+dfsg-2ubuntu1.46
  [   53.420589] hv_balloon: Max. dynamic memory size: 32768 MB
  [   60.928772] L1TF CPU bug present and SMT on, data leak possible. See 
CVE-2018-3646 and 
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for 
details.
  [   60.940895] kvm: SMP vm created on host with unstable TSC; guest TSC will 
not be reliable
  [   60.967454] BUG: unable to handle kernel paging request at 56b8
  [   60.971140] IP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel]
  [   60.971140] PGD 0 P4D 0
  [   60.971140] Oops:  [#1] SMP PTI
  [   60.971140] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner 
iptable_security xt_conntrack nf_conntrack libcrc32c ip_tables x_tables udf 
crc_itu_t dm_crypt joydev hid_generic kvm_intel kvm irqbypass hid_hyperv hid 
hyperv_keyboard hv_balloon serio_raw crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
hyperv_fb cfbfillrect pata_acpi cfbimgblt cfbcopyarea hv_netvsc hv_utils
  [   60.971140] CPU: 2 PID: 1903 Comm: qemu-system-x86 Not tainted 
4.15.0-1084-azure #94~14.04.1-Ubuntu
  [   60.971140] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   60.971140] RIP: 0010:vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel]
  [   60.971140] RSP: 0018:a44847a53cc0 EFLAGS: 00010002
  [   60.971140] RAX:  RBX:  RCX: 

  [   61.020070] RDX: 6c14 RSI:  RDI: 

  [   61.020070] RBP: a44847a53d10 R08:  R09: 

  [   61.020070] R10:  R11:  R12: 

  [   61.020070] R13:  R14:  R15: 

  [   61.020070] FS:  7f753bba4700() GS:8fefdd68() 
knlGS:
  [   61.020070] CS:  0010 DS:  ES:  CR0: 80050033
  [   61.020070] CR2: 56b8 CR3: 000888c42005 CR4: 
003726e0
  [   61.020070] Call Trace:
  [   61.020070]  vcpu_enter_guest+0x909/0x12a0 [kvm]
  [   61.020070]  kvm_arch_vcpu_ioctl_run+0x2d8/0x3f0 [kvm]
  [   61.020070]  kvm_vcpu_ioctl+0x2a8/0x630 [kvm]
  [   61.020070]  ? dequeue_signal+0x3e/0x160
  [   61.020070]  ? do_sigtimedwait+0xbd/0x210
  [   61.020070]  ? copy_siginfo_to_user+0x12e/0x2d0
  [   61.020070]  do_vfs_ioctl+0x9b/0x5f0
  [   61.020070]  ? SyS_futex+0x71/0x150
  [   61.020070]  SyS_ioctl+0x79/0x90
  [   61.020070]  ? _copy_to_user+0x26/0x40
  [   61.020070]  do_syscall_64+0x80/0x1e0
  [   61.020070]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [   61.020070] RIP: 0033:0x7f7545f34ea7
  [   61.020070] RSP: 002b:7f753bba3bd8 EFLAGS: 0246 ORIG_RAX: 
0010
  [   61.020070] RAX: ffda RBX: 7f754bbed000 RCX: 
7f7545f34ea7
  [   61.020070] RDX:  RSI: ae80 RDI: 
000c
  [   61.020070] RBP: 55c68fd7f160 R08:  R09: 
0002
  [   61.020070] R10: 0008 R11: 0246 R12: 

  [   61.020070] R13:  R14: 7f753bba49c0 R15: 
55c68ee809a0
  [   61.020070] Code: 31 ed 45 31 f6 45 31 ff 0f 20 d0 48 89 81 e0 02 00 00 31 
c0 31 db 31 c9 31 d2 31 f6 31 ff 31 ed 5d 5a f6 05 0c c0 01 00 10 74 1b <48> 8b 
81 b8 56 00 00 48 8b 40 40 48 8b 80 08 08 00 00 f6 c4 01
  [   61.020070] RIP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] RSP: a44847a53cc0
  [   61.020070] CR2: 56b8
  [   61.020070] ---[ end trace ab52be3a09d557f5 ]---

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

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

[Kernel-packages] [Bug 1882623] Re: VM enter into hung status after triggering a crash

2020-07-13 Thread lilideng
Last time I did verification against gallery image, the default kernel version 
is 4.4.0-148-generic.
And I tried below kernel, found the kernel linux-image-4.15.0-1042-azure is the 
first one which we hit this bug, it is not specific for the esm kernel.

#   Kernel Version/Package  Result
0   Default kernel 4.4.0-148-generic => Good
1   linux-image-4.15.0-1023-azure => Good
2   linux-image-4.15.0-1030-azure   
3   linux-image-4.15.0-1031-azure   
4   linux-image-4.15.0-1032-azure   
5   linux-image-4.15.0-1035-azure   
6   linux-image-4.15.0-1036-azure => Good 
7   linux-image-4.15.0-1037-azure   
8   linux-image-4.15.0-1039-azure   
9   linux-image-4.15.0-1040-azure => Good
10  linux-image-4.15.0-1041-azure => Good
11  linux-image-4.15.0-1042-azure => Bad
12  linux-image-4.15.0-1045-azure => Bad

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

Title:
  VM enter into hung status after triggering a crash

Status in linux-azure package in Ubuntu:
  New

Bug description:
  Create VM on Azure using Canonical UbuntuServer 14.04.5-LTS latest
  using size Standard DS2 v2

  Install kexec-tools kdump-tools makedumpfile, configure boot kernel
  parameter crashkernel=512M

  Run sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools and
  sed -i 's/LOAD_KEXEC=true/LOAD_KEXEC=false/g' /etc/default/kexec

  Reboot VM, make sure crash kernel memory reserved successfully

  Trigger a crash by run echo 1 > /proc/sys/kernel/sysrq, then echo c >
  /proc/sysrq-trigger, VM will reboot automatically and after reboot,
  check crash dump is generated under /var/crash

  Install linux-azure kernel

  Enable private-ppa canonical-kernel-esm

  Install kernel linux-azure, reboot VM, kernel version
  4.15.0-1084-azure

  Trigger a crash by run echo 1 > /proc/sys/kernel/sysrq, then echo c >
  /proc/sysrq-trigger, VM entered into a hung status.

  Attach whole serial console
  [   65.452007] INFO: rcu_sched detected stalls on CPUs/tasks:
  [   65.456004]  1-...!: (0 ticks this GP) idle=488/0/0 softirq=1/1 fqs=0
  [   65.456004]  (detected by 0, t=15002 jiffies, g=707, c=706, q=8457)
  [   65.456004] rcu_sched kthread starved for 15002 jiffies! g707 c706 f0x0 
RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1
  [  360.020026] INFO: rcu_sched detected stalls on CPUs/tasks:
  [  360.024015]  1-...!: (10 GPs behind) idle=b34/0/0 softirq=1/1 fqs=1
  [  360.024015]  (detected by 0, t=15002 jiffies, g=717, c=716, q=6429)
  [  360.024015] rcu_sched kthread starved for 15000 jiffies! g717 c716 f0x0 
RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1
  [  420.048010] INFO: rcu_sched detected stalls on CPUs/tasks:
  [  420.052006]  1-...!: (0 ticks this GP) idle=f94/0/0 softirq=1/1 fqs=0
  [  420.052006]  (detected by 0, t=15002 jiffies, g=718, c=717, q=6429)
  [  420.052006] rcu_sched kthread starved for 15002 jiffies! g718 c717 f0x0 
RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1

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

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


[Kernel-packages] [Bug 1882624] Re: nested kvm doesn't work

2020-07-10 Thread lilideng
** Summary changed:

- nested kvm doesn't not work
+ nested kvm doesn't work

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

Title:
  nested kvm doesn't work

Status in linux-azure package in Ubuntu:
  New

Bug description:
  Create VM on Azure using Canonical UbuntuServer 14.04.5-LTS latest
  using size Standard E4s v3

  Enable private-ppa canonical-kernel-esm

  Install kernel linux-azure, reboot VM, kernel version
  4.15.0-1084-azure

  Install qemu-kvm, download
  https://eosgnestedstorage.blob.core.windows.net/images/nested-
  ubuntu-4.15.0-23-generic.qcow2

  Launch nested VM using command qemu-system-x86_64 -smp 2 -m 2048 -hda
  /mnt/resource/nested.qcow2 -display none -device e1000,netdev=user.0
  -netdev user,id=user.0,hostfwd=tcp::60022-:22 -enable-kvm -daemonize

  Expected ssh -p 60022 nesteduser@localhost will ask password to login

  We can't connect to it, see below call trace in dmesg
 qemu-kvm version doesn't change after kernel upgraded. 
   
 2.0.0+dfsg-2ubuntu1.46
  [   53.420589] hv_balloon: Max. dynamic memory size: 32768 MB
  [   60.928772] L1TF CPU bug present and SMT on, data leak possible. See 
CVE-2018-3646 and 
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for 
details.
  [   60.940895] kvm: SMP vm created on host with unstable TSC; guest TSC will 
not be reliable
  [   60.967454] BUG: unable to handle kernel paging request at 56b8
  [   60.971140] IP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel]
  [   60.971140] PGD 0 P4D 0
  [   60.971140] Oops:  [#1] SMP PTI
  [   60.971140] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner 
iptable_security xt_conntrack nf_conntrack libcrc32c ip_tables x_tables udf 
crc_itu_t dm_crypt joydev hid_generic kvm_intel kvm irqbypass hid_hyperv hid 
hyperv_keyboard hv_balloon serio_raw crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
hyperv_fb cfbfillrect pata_acpi cfbimgblt cfbcopyarea hv_netvsc hv_utils
  [   60.971140] CPU: 2 PID: 1903 Comm: qemu-system-x86 Not tainted 
4.15.0-1084-azure #94~14.04.1-Ubuntu
  [   60.971140] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   60.971140] RIP: 0010:vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel]
  [   60.971140] RSP: 0018:a44847a53cc0 EFLAGS: 00010002
  [   60.971140] RAX:  RBX:  RCX: 

  [   61.020070] RDX: 6c14 RSI:  RDI: 

  [   61.020070] RBP: a44847a53d10 R08:  R09: 

  [   61.020070] R10:  R11:  R12: 

  [   61.020070] R13:  R14:  R15: 

  [   61.020070] FS:  7f753bba4700() GS:8fefdd68() 
knlGS:
  [   61.020070] CS:  0010 DS:  ES:  CR0: 80050033
  [   61.020070] CR2: 56b8 CR3: 000888c42005 CR4: 
003726e0
  [   61.020070] Call Trace:
  [   61.020070]  vcpu_enter_guest+0x909/0x12a0 [kvm]
  [   61.020070]  kvm_arch_vcpu_ioctl_run+0x2d8/0x3f0 [kvm]
  [   61.020070]  kvm_vcpu_ioctl+0x2a8/0x630 [kvm]
  [   61.020070]  ? dequeue_signal+0x3e/0x160
  [   61.020070]  ? do_sigtimedwait+0xbd/0x210
  [   61.020070]  ? copy_siginfo_to_user+0x12e/0x2d0
  [   61.020070]  do_vfs_ioctl+0x9b/0x5f0
  [   61.020070]  ? SyS_futex+0x71/0x150
  [   61.020070]  SyS_ioctl+0x79/0x90
  [   61.020070]  ? _copy_to_user+0x26/0x40
  [   61.020070]  do_syscall_64+0x80/0x1e0
  [   61.020070]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [   61.020070] RIP: 0033:0x7f7545f34ea7
  [   61.020070] RSP: 002b:7f753bba3bd8 EFLAGS: 0246 ORIG_RAX: 
0010
  [   61.020070] RAX: ffda RBX: 7f754bbed000 RCX: 
7f7545f34ea7
  [   61.020070] RDX:  RSI: ae80 RDI: 
000c
  [   61.020070] RBP: 55c68fd7f160 R08:  R09: 
0002
  [   61.020070] R10: 0008 R11: 0246 R12: 

  [   61.020070] R13:  R14: 7f753bba49c0 R15: 
55c68ee809a0
  [   61.020070] Code: 31 ed 45 31 f6 45 31 ff 0f 20 d0 48 89 81 e0 02 00 00 31 
c0 31 db 31 c9 31 d2 31 f6 31 ff 31 ed 5d 5a f6 05 0c c0 01 00 10 74 1b <48> 8b 
81 b8 56 00 00 48 8b 40 40 48 8b 80 08 08 00 00 f6 c4 01
  [   61.020070] RIP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] RSP: a44847a53cc0
  [   61.020070] CR2: 56b8
  [   61.020070] ---[ end trace ab52be3a09d557f5 ]---

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

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

[Kernel-packages] [Bug 1882624] Re: nested kvm doesn't not work

2020-07-02 Thread lilideng
Hi Marcelo, this issue is fixed in kernel version 4.15.0-1091-azure from
private-ppa canonical-kernel-esm.

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

Title:
  nested kvm doesn't not work

Status in linux-azure package in Ubuntu:
  New

Bug description:
  Create VM on Azure using Canonical UbuntuServer 14.04.5-LTS latest
  using size Standard E4s v3

  Enable private-ppa canonical-kernel-esm

  Install kernel linux-azure, reboot VM, kernel version
  4.15.0-1084-azure

  Install qemu-kvm, download
  https://eosgnestedstorage.blob.core.windows.net/images/nested-
  ubuntu-4.15.0-23-generic.qcow2

  Launch nested VM using command qemu-system-x86_64 -smp 2 -m 2048 -hda
  /mnt/resource/nested.qcow2 -display none -device e1000,netdev=user.0
  -netdev user,id=user.0,hostfwd=tcp::60022-:22 -enable-kvm -daemonize

  Expected ssh -p 60022 nesteduser@localhost will ask password to login

  We can't connect to it, see below call trace in dmesg
 qemu-kvm version doesn't change after kernel upgraded. 
   
 2.0.0+dfsg-2ubuntu1.46
  [   53.420589] hv_balloon: Max. dynamic memory size: 32768 MB
  [   60.928772] L1TF CPU bug present and SMT on, data leak possible. See 
CVE-2018-3646 and 
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for 
details.
  [   60.940895] kvm: SMP vm created on host with unstable TSC; guest TSC will 
not be reliable
  [   60.967454] BUG: unable to handle kernel paging request at 56b8
  [   60.971140] IP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel]
  [   60.971140] PGD 0 P4D 0
  [   60.971140] Oops:  [#1] SMP PTI
  [   60.971140] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner 
iptable_security xt_conntrack nf_conntrack libcrc32c ip_tables x_tables udf 
crc_itu_t dm_crypt joydev hid_generic kvm_intel kvm irqbypass hid_hyperv hid 
hyperv_keyboard hv_balloon serio_raw crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
hyperv_fb cfbfillrect pata_acpi cfbimgblt cfbcopyarea hv_netvsc hv_utils
  [   60.971140] CPU: 2 PID: 1903 Comm: qemu-system-x86 Not tainted 
4.15.0-1084-azure #94~14.04.1-Ubuntu
  [   60.971140] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   60.971140] RIP: 0010:vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel]
  [   60.971140] RSP: 0018:a44847a53cc0 EFLAGS: 00010002
  [   60.971140] RAX:  RBX:  RCX: 

  [   61.020070] RDX: 6c14 RSI:  RDI: 

  [   61.020070] RBP: a44847a53d10 R08:  R09: 

  [   61.020070] R10:  R11:  R12: 

  [   61.020070] R13:  R14:  R15: 

  [   61.020070] FS:  7f753bba4700() GS:8fefdd68() 
knlGS:
  [   61.020070] CS:  0010 DS:  ES:  CR0: 80050033
  [   61.020070] CR2: 56b8 CR3: 000888c42005 CR4: 
003726e0
  [   61.020070] Call Trace:
  [   61.020070]  vcpu_enter_guest+0x909/0x12a0 [kvm]
  [   61.020070]  kvm_arch_vcpu_ioctl_run+0x2d8/0x3f0 [kvm]
  [   61.020070]  kvm_vcpu_ioctl+0x2a8/0x630 [kvm]
  [   61.020070]  ? dequeue_signal+0x3e/0x160
  [   61.020070]  ? do_sigtimedwait+0xbd/0x210
  [   61.020070]  ? copy_siginfo_to_user+0x12e/0x2d0
  [   61.020070]  do_vfs_ioctl+0x9b/0x5f0
  [   61.020070]  ? SyS_futex+0x71/0x150
  [   61.020070]  SyS_ioctl+0x79/0x90
  [   61.020070]  ? _copy_to_user+0x26/0x40
  [   61.020070]  do_syscall_64+0x80/0x1e0
  [   61.020070]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [   61.020070] RIP: 0033:0x7f7545f34ea7
  [   61.020070] RSP: 002b:7f753bba3bd8 EFLAGS: 0246 ORIG_RAX: 
0010
  [   61.020070] RAX: ffda RBX: 7f754bbed000 RCX: 
7f7545f34ea7
  [   61.020070] RDX:  RSI: ae80 RDI: 
000c
  [   61.020070] RBP: 55c68fd7f160 R08:  R09: 
0002
  [   61.020070] R10: 0008 R11: 0246 R12: 

  [   61.020070] R13:  R14: 7f753bba49c0 R15: 
55c68ee809a0
  [   61.020070] Code: 31 ed 45 31 f6 45 31 ff 0f 20 d0 48 89 81 e0 02 00 00 31 
c0 31 db 31 c9 31 d2 31 f6 31 ff 31 ed 5d 5a f6 05 0c c0 01 00 10 74 1b <48> 8b 
81 b8 56 00 00 48 8b 40 40 48 8b 80 08 08 00 00 f6 c4 01
  [   61.020070] RIP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] RSP: a44847a53cc0
  [   61.020070] CR2: 56b8
  [   61.020070] ---[ end trace ab52be3a09d557f5 ]---

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

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

[Kernel-packages] [Bug 1779640] Re: [Hyper-V] KVP daemon crashes at startup

2019-11-20 Thread lilideng
Try HyperV command, you will see hv-kvp-daemon service exit with KVP:
read failed; error:9 Bad file descriptor

Disable-VMIntegrationService -Name "Key-Value Pair Exchange" -VMName
$VMName -ComputerName $hvServer

Kernel version - 
11/21/2019 07:10:21 : [INFO ] Old kernel: 4.15.0-38-generic
11/21/2019 07:10:21 : [INFO ] New kernel: 5.0.0-1026-azure

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

Title:
  [Hyper-V] KVP daemon crashes at startup

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  the following issue with the KVP daemon:

  KVP daemon crashes after approximatively 2 minutes of uptime and it enters in 
a failed state. The daemon can be manually started and it enters back in active 
(running) state.
  The error messages from /var/log/syslog after the daemon enters the failed 
state are the following:

  Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with 
result 'exit-code'.
  Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon.

  Note: There was a simmilar issue discussed on this thread
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the
  fixing commit seems to be inclued in this Bionic build.

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

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


[Kernel-packages] [Bug 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip

2019-08-13 Thread lilideng
Same thing happen in HyperV, when run apt-get install -yq linux-
azure/disco, it hung in some rate. Like upgrade 3 VMs, 1 VM hung.

VM configuration - 3584 memory, 2 Virtual processors

[  485.023123] INFO: task mdadm:11824 blocked for more than 120 seconds.
[  485.029485]   Not tainted 5.0.0-15-generic #16-Ubuntu
[  485.034818] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  485.042754] mdadm   D0 11824  11818 0x
[  485.042758] Call Trace:
[  485.042768]  __schedule+0x2d0/0x840
[  485.042770]  ? __switch_to_asm+0x34/0x70
[  485.042771]  ? __switch_to_asm+0x40/0x70
[  485.042774]  schedule+0x2c/0x70
[  485.042776]  schedule_timeout+0x258/0x360
[  485.042780]  wait_for_completion+0xb7/0x140
[  485.042784]  ? wake_up_q+0x80/0x80
[  485.042790]  __floppy_read_block_0+0x138/0x190 [floppy]
[  485.042793]  ? floppy_cmos_show+0x30/0x30 [floppy]
[  485.042797]  floppy_revalidate+0xf8/0x230 [floppy]
[  485.042800]  check_disk_change+0x62/0x70
[  485.042803]  floppy_open+0x2ae/0x380 [floppy]
[  485.042805]  __blkdev_get+0xe5/0x550
[  485.042807]  ? bd_acquire+0xd0/0xd0
[  485.042809]  blkdev_get+0x10c/0x330
[  485.042811]  ? bd_acquire+0xd0/0xd0
[  485.042812]  blkdev_open+0x92/0x100
[  485.042815]  do_dentry_open+0x143/0x3a0
[  485.042818]  vfs_open+0x2d/0x30
[  485.042820]  path_openat+0x2d4/0x16d0
[  485.042825]  ? put_device+0x17/0x20
[  485.042828]  ? scsi_device_put+0x2b/0x30
[  485.042831]  do_filp_open+0x93/0x100
[  485.042835]  ? strncpy_from_user+0x56/0x1b0
[  485.042839]  ? __alloc_fd+0xb2/0x140
[  485.042841]  do_sys_open+0x177/0x280
[  485.042844]  __x64_sys_openat+0x20/0x30
[  485.042847]  do_syscall_64+0x5a/0x110
[  485.042849]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  485.042851] RIP: 0033:0x7f6cda22dcce
[  485.042856] Code: Bad RIP value.
[  485.042857] RSP: 002b:7ffedec2d0e0 EFLAGS: 0246 ORIG_RAX: 
0101
[  485.042859] RAX: ffda RBX: 4000 RCX: 7f6cda22dcce
[  485.042860] RDX: 4000 RSI: 55be36cfd870 RDI: ff9c
[  485.042861] RBP: 55be36cfd870 R08: 55be36cfd870 R09: 
[  485.042862] R10:  R11: 0246 R12: 7ffedec2d3a0
[  485.042863] R13:  R14: 0001 R15: 55be36cfcbb0
[  495.386112] kauditd_printk_skb: 1 callbacks suppressed
[  495.386114] audit: type=1400 audit(1565682010.026:62): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.lxd.activate" 
pid=15020 comm="apparmor_parser"
[  495.386659] audit: type=1400 audit(1565682010.026:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.lxd.benchmark" 
pid=15021 comm="apparmor_parser"
[  495.516297] audit: type=1400 audit(1565682010.158:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.lxd.buginfo" 
pid=15022 comm="apparmor_parser"
[  495.516773] audit: type=1400 audit(1565682010.158:65): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.lxd.check-kernel" 
pid=15023 comm="apparmor_parser"
[  495.663497] audit: type=1400 audit(1565682010.306:66): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.lxd.hook.configure" 
pid=15025 comm="apparmor_parser"
[  495.721415] audit: type=1400 audit(1565682010.362:67): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.lxd.daemon" 
pid=15024 comm="apparmor_parser"
[  495.741053] audit: type=1400 audit(1565682010.382:68): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.lxd.hook.install" 
pid=15026 comm="apparmor_parser"
[  495.847228] audit: type=1400 audit(1565682010.490:69): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.lxd.lxc" pid=15027 
comm="apparmor_parser"
[  495.859690] audit: type=1400 audit(1565682010.502:70): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.lxd.lxd" pid=15028 
comm="apparmor_parser"
[  495.924648] audit: type=1400 audit(1565682010.566:71): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="snap.lxd.migrate" 
pid=15029 comm="apparmor_parser"
[  605.855134] INFO: task mdadm:11824 blocked for more than 120 seconds.
[  605.861358]   Not tainted 5.0.0-15-generic #16-Ubuntu
[  605.866526] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  605.874078] mdadm   D0 11824  11818 0x
[  605.874082] Call Trace:
[  605.874091]  __schedule+0x2d0/0x840
[  605.874093]  ? __switch_to_asm+0x34/0x70
[  605.874094]  ? __switch_to_asm+0x40/0x70
[  605.874096]  schedule+0x2c/0x70
[  605.874098]  schedule_timeout+0x258/0x360
[  605.874101]  wait_for_completion+0xb7/0x140
[  605.874104]  ? wake_up_q+0x80/0x80
[  605.874108]  __floppy_read_block_0+0x138/0x190 [floppy]
[  605.874110]  ? floppy_cmos_show+0x30/0x30 [floppy]
[  605.874113]  floppy_revalidate+0xf8/0x230 

[Kernel-packages] [Bug 1405807] Re: linux-lts-utopic-tools-common package is empty

2015-06-22 Thread lilideng
** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

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

Title:
  linux-lts-utopic-tools-common package is empty

Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Committed

Bug description:
  Hi,

  I installed linux-lts-utopic-tools-common under Ubuntu 14.04.1 and
  hoped to find the same binaries in it as under Ubuntu utopic, but the
  package is empty.

  I guess, do_tools must be set to true somewhere, but I don't know
  exactly where.

  Under utopic, it looks like this:
  /.
  /usr
  /usr/share
  /usr/share/man
  /usr/share/man/man1
  /usr/share/man/man1/cpupower-frequency-set.1.gz
  /usr/share/man/man1/perf-inject.1.gz
  /usr/share/man/man1/cpupower-idle-info.1.gz
  /usr/share/man/man1/perf-buildid-cache.1.gz
  /usr/share/man/man1/perf-diff.1.gz
  /usr/share/man/man1/cpupower-monitor.1.gz
  /usr/share/man/man1/perf-mem.1.gz
  /usr/share/man/man1/cpupower-idle-set.1.gz
  /usr/share/man/man1/perf-report.1.gz
  /usr/share/man/man1/perf.1.gz
  /usr/share/man/man1/usbip.8.gz
  /usr/share/man/man1/perf-timechart.1.gz
  /usr/share/man/man1/perf-script-perl.1.gz
  /usr/share/man/man1/cpupower-info.1.gz
  /usr/share/man/man1/perf-help.1.gz
  /usr/share/man/man1/perf-archive.1.gz
  /usr/share/man/man1/perf-buildid-list.1.gz
  /usr/share/man/man1/perf-kmem.1.gz
  /usr/share/man/man1/perf-top.1.gz
  /usr/share/man/man1/perf-trace.1.gz
  /usr/share/man/man1/perf-stat.1.gz
  /usr/share/man/man1/usbipd.8.gz
  /usr/share/man/man1/cpupower-set.1.gz
  /usr/share/man/man1/perf-bench.1.gz
  /usr/share/man/man1/perf-sched.1.gz
  /usr/share/man/man1/perf-annotate.1.gz
  /usr/share/man/man1/perf-record.1.gz
  /usr/share/man/man1/perf-script-python.1.gz
  /usr/share/man/man1/cpupower-frequency-info.1.gz
  /usr/share/man/man1/perf-kvm.1.gz
  /usr/share/man/man1/perf-script.1.gz
  /usr/share/man/man1/perf-test.1.gz
  /usr/share/man/man1/perf-probe.1.gz
  /usr/share/man/man1/perf-lock.1.gz
  /usr/share/man/man1/perf-evlist.1.gz
  /usr/share/man/man1/cpupower.1.gz
  /usr/share/man/man1/perf-list.1.gz
  /usr/share/man/man8
  /usr/share/man/man8/x86_energy_perf_policy.8.gz
  /usr/share/man/man8/turbostat.8.gz
  /usr/share/doc
  /usr/share/doc/linux-tools-common
  /usr/share/doc/linux-tools-common/copyright
  /usr/share/doc/linux-tools-common/changelog.Debian.gz
  /usr/bin
  /usr/bin/turbostat
  /usr/bin/usbip
  /usr/bin/x86_energy_perf_policy
  /usr/bin/perf
  /usr/bin/usbipd
  /usr/bin/cpupower

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

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