ci2 starts bisection 2026-10-08 10:50:16.937389865 +0000 UTC m=+25557.501259710 bisecting fixing commit since dc5c83b7f5f83ea99aea5c771b1ec77458263a15 building syzkaller on 492bab153dea5e0e414bd0bbf60c3871267255ed ensuring issue is reproducible on original commit dc5c83b7f5f83ea99aea5c771b1ec77458263a15 testing commit dc5c83b7f5f83ea99aea5c771b1ec77458263a15 gcc compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 kernel signature: e8233d3d4500a42d67f556f20b5e056e2963a6038654e7bbea4b7f878208813e run #0: infra problem: failed to create instance: googleapi: Error 503: Internal error. Please try again or contact Google Support. (Code: '65D52330BDFD6.934F5F4.3B2F0758'), backendError run #1: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32794088a730 0x32794088a820 0x32794088a8c0] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} run #2: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32793aeabd60 0x32793aeabe50 0x327940914000] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} run #3: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32793aa60410 0x32793aa60500 0x32793aa605a0] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} run #4: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32793aa60690 0x32793aa60780 0x32793aa60820] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} run #5: crashed: lost connection to test machine run #6: crashed: BUG: unable to handle kernel paging request in dummy_udc_start run #7: crashed: BUG: unable to handle kernel paging request in dummy_udc_start run #8: crashed: BUG: unable to handle kernel paging request in dummy_udc_start run #9: crashed: BUG: unable to handle kernel paging request in dummy_udc_start run #10: crashed: BUG: unable to handle kernel paging request in dummy_udc_start run #11: crashed: BUG: unable to handle kernel paging request in dummy_udc_start run #12: crashed: BUG: unable to handle kernel paging request in dummy_udc_start run #13: crashed: BUG: unable to handle kernel paging request in dummy_udc_start run #14: crashed: BUG: unable to handle kernel paging request in dummy_udc_start run #15: crashed: BUG: unable to handle kernel paging request in dummy_udc_start run #16: crashed: BUG: unable to handle kernel paging request in dummy_udc_start run #17: crashed: BUG: unable to handle kernel paging request in dummy_udc_start run #18: crashed: BUG: unable to handle kernel paging request in dummy_udc_start run #19: crashed: BUG: unable to handle kernel paging request in dummy_udc_start representative crash: BUG: unable to handle kernel paging request in dummy_udc_start, types: [MEMORY_SAFETY_BUG] check whether we can drop unnecessary instrumentation disabling configs for [atomic_sleep hang memleak ubsan kasan locking], they are not needed testing commit dc5c83b7f5f83ea99aea5c771b1ec77458263a15 gcc compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 kernel signature: a79151b2da4c85e1574b6bdeb2267e7aee2a82a84e78e1f7aabdba5a38a6a92f run #0: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32793ab84230 0x32793ab84320 0x32793ab843c0] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} run #1: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32793fcebd60 0x32793fcebe50 0x32793aa600f0] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} run #2: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32793f2aaff0 0x32793f2ab0e0 0x32793f2ab180] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} run #3: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32793aa60410 0x32793aa60500 0x32793aa605a0] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} run #4: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32793ab844b0 0x32793ab845a0 0x32793ab84640] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} run #5: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32793f2ab270 0x32793f2ab360 0x32793f2ab400] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} run #6: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32793ab84780 0x32793ab84870 0x32793ab84910] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} run #7: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32793ab84a00 0x32793ab84af0 0x32793ab84b90] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} run #8: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32793ab84c30 0x32793ab84d20 0x32793ab84dc0] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} run #9: infra problem: &{Code:ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS ErrorDetails:[0x32793ab84f00 0x32793ab85040 0x32793ab850e0] Location: Message:The zone 'projects/syzkaller/zones/us-central1-b' does not have enough resources available to fulfill the request. '(resource type:compute)'. ForceSendFields:[] NullFields:[]} revisions tested: 2, total time: 36m57.415655286s (build: 16m24.872205204s, test: 17m42.559473864s) error: config minimization failed: unable to determine the verdict because of infra errors