Bug 1111221 - WARNING: CPU: 0 PID: 130 at drivers/hv/hv_balloon.c:1269 balloon_up+0x34a/0x360 [hv_balloon]
WARNING: CPU: 0 PID: 130 at drivers/hv/hv_balloon.c:1269 balloon_up+0x34a/0x3...
Status: RESOLVED UPSTREAM
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kernel
Current
x86-64 Other
: P5 - None : Normal (vote)
: ---
Assigned To: E-mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-10-09 12:39 UTC by Cristian Rodríguez
Modified: 2018-12-13 10:40 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cristian Rodríguez 2018-10-09 12:39:33 UTC
From time to time.. mostly when the hyper-v host resumes from suspend.. (host in this case is a laptop) I get this

[ 1930.965057] WARNING: CPU: 0 PID: 130 at drivers/hv/hv_balloon.c:1269 balloon_up+0x34a/0x360 [hv_balloon]
[ 1930.965059] Modules linked in: tun ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables bpfilter xt_conntrack x_tables nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc msr overlay af_packet crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper pcspkr i2c_piix4 hyperv_fb hv_utils ptp hv_netvsc pps_core hv_balloon joydev button sch_fq_codel sr_mod cdrom ata_generic hid_generic hv_storvsc hid_hyperv scsi_transport_fc hyperv_keyboard ata_piix serio_raw hv_vmbus sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua
[ 1930.965106] CPU: 0 PID: 130 Comm: kworker/0:2 Not tainted 4.18.12-2.ga880bd8-default #1 openSUSE Tumbleweed (unreleased)
[ 1930.965107] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007  06/02/2017
[ 1930.965113] Workqueue: events balloon_up [hv_balloon]
[ 1930.965115] RIP: 0010:balloon_up+0x34a/0x360 [hv_balloon]
[ 1930.965116] Code: 5b 5d 41 5c 41 5d 41 5e 41 5f c3 8b 0d 4f 28 00 00 8b 54 24 04 48 c7 c6 d0 e3 1e c0 48 c7 c7 90 f3 1e c0 e8 18 ec 27 f1 eb b8 <0f> 0b e9 d7 fc ff ff e9 d1 08 00 00 66 2e 0f 1f 84 00 00 00 00 00 
[ 1930.965138] RSP: 0018:ffffa7ca810afe48 EFLAGS: 00010206
[ 1930.965139] RAX: 0000000000001459 RBX: ffffffffc01ef8e8 RCX: ffff90903a622aa0
[ 1930.965140] RDX: 0000000000000001 RSI: ffff908f8fc0f2b0 RDI: ffffffffc01ef8e8
[ 1930.965140] RBP: ffff90903a622a80 R08: 0000000000000000 R09: 000073746e657665
[ 1930.965141] R10: 8080808080808080 R11: 000001c1966c5d00 R12: ffff90903a628600
[ 1930.965142] R13: 0000000000000000 R14: ffff908f8e8a9240 R15: 0ffff90903a62860
[ 1930.965143] FS:  0000000000000000(0000) GS:ffff90903a600000(0000) knlGS:0000000000000000
[ 1930.965144] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1930.965145] CR2: 00007f510c4eec78 CR3: 00000000b820a004 CR4: 00000000003606f0
[ 1930.965147] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 1930.965148] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 1930.965149] Call Trace:
[ 1930.965158]  process_one_work+0x1fd/0x3e0
[ 1930.965161]  worker_thread+0x2d/0x3d0
[ 1930.965163]  ? rescuer_thread+0x340/0x340
[ 1930.965165]  kthread+0x112/0x130
[ 1930.965167]  ? kthread_create_worker_on_cpu+0x40/0x40
[ 1930.965171]  ret_from_fork+0x24/0x50
[ 1930.965175] ---[ end trace 1eb2e9621e2c0436 ]---


Does not matter what kernel version, it has been going on for while, other than the warning I have not seen any additional misbehaviour that can be attributed to this warning.
Comment 1 Olaf Hering 2018-10-10 12:48:03 UTC
Since we have no special hyperv related patches in Factory, I suggest to report this upstream to the hyperv maintainers - given that this happens already since a while.
Comment 2 Olaf Hering 2018-12-13 10:40:05 UTC
supposed to be fixed upstream.