Failed test: consumer-poison-page-stat

20261028T035110Z · daily · aarch64

Reason: Poison statistics must report a nonzero count after poisoning

GitHub Actions run · All run evidence

What this evidence shows

The test expected rasdaemon to emit its poison-page statistics warning after the injected page was poisoned. That warning is absent in the captured daemon output. The memory_failure_event log is present. This older run did not capture /proc/meminfo or an independent kernel trace, so it cannot establish the exact timing or directly prove the race.

Failure evidence

Failure interpretation

The test expected rasdaemon to emit its poison-page statistics warning after the injected page was poisoned. That warning is absent in the captured daemon output. The memory_failure_event log is present. This older run did not capture /proc/meminfo or an independent kernel trace, so it cannot establish the exact timing or directly prove the race.

Threshold

0 (set by the poison-page-stat test in this historical run)

Expected warning

Poison page statistics exceeded threshold:

Warning observed

No

Hardware corrupted

Not captured by this run

Kernel event observed

Yes

Kernel trace

Not captured by this run

Rasdaemon output

rasdaemon: Read 11 config vars from /var/tmp/rasdaemon-qemu/memory-failure.env.
rasdaemon: Can't find a x86 CPU at /proc/cpuinfo. Disabling MCE handler.
rasdaemon: Can't register mce handler
rasdaemon: module x86-mce-erst init failed: -2
rasdaemon: Cpu fault isolation is disabled
rasdaemon: Page offline choice on Corrected Errors is off
rasdaemon: Row offline choice on Corrected Errors is off
rasdaemon: Enabling DB backend: sqlite3
rasdaemon: block:block_rq_error event enabled
rasdaemon: Enabled event block:block_rq_error
rasdaemon: cxl:cxl_aer_correctable_error event enabled
rasdaemon: Enabled event cxl:cxl_aer_correctable_error
rasdaemon: cxl:cxl_aer_uncorrectable_error event enabled
rasdaemon: Enabled event cxl:cxl_aer_uncorrectable_error
rasdaemon: cxl:cxl_dram event enabled
rasdaemon: Enabled event cxl:cxl_dram
rasdaemon: cxl:cxl_general_media event enabled
rasdaemon: Enabled event cxl:cxl_general_media
rasdaemon: cxl:cxl_generic_event event enabled
rasdaemon: Enabled event cxl:cxl_generic_event
rasdaemon: cxl:cxl_memory_module event enabled
rasdaemon: Enabled event cxl:cxl_memory_module
rasdaemon: cxl:cxl_memory_sparing event enabled
rasdaemon: Enabled event cxl:cxl_memory_sparing
rasdaemon: cxl:cxl_overflow event enabled
rasdaemon: Enabled event cxl:cxl_overflow
rasdaemon: cxl:cxl_poison event enabled
rasdaemon: Enabled event cxl:cxl_poison
rasdaemon: Can't find a x86 CPU at /proc/cpuinfo. Disabling MCE handler.
rasdaemon: net:net_dev_xmit_timeout event enabled
rasdaemon: Enabled event net:net_dev_xmit_timeout
rasdaemon: ras:aer_event event enabled
rasdaemon: Enabled event ras:aer_event
rasdaemon: 	 no AER_CE_TRIGGER (0xfffff25c7f5e)
rasdaemon: ras:arm_event event enabled
rasdaemon: Enabled event ras:arm_event
rasdaemon: ras:extlog_mem_event event not exist
rasdaemon: Can't get traces from ras:extlog_mem_event
rasdaemon: ras:mc_event event enabled
rasdaemon: Enabled event ras:mc_event
rasdaemon: ras:memory_failure_event event enabled
rasdaemon: Enabled event ras:memory_failure_event
rasdaemon: Setup memory_fail_event trigger `/var/tmp/rasdaemon-qemu/memory-failure.db.trigger`
rasdaemon: ras:non_standard_event event enabled
rasdaemon: Enabled event ras:non_standard_event
rasdaemon: ras:reri_event event not exist
rasdaemon: Can't get traces from ras:reri_event
rasdaemon: signal:signal_generate event enabled
rasdaemon: Enabled event signal:signal_generate
rasdaemon: devlink:devlink_health_report event enabled
rasdaemon: Enabled event devlink:devlink_health_report
rasdaemon: Recording aer_event events
rasdaemon: Recording arm_event events
rasdaemon: Recording cxl_poison_event events
rasdaemon: Recording cxl_aer_ue_event events
rasdaemon: Recording cxl_aer_ce_event events
rasdaemon: Recording cxl_overflow_event events
rasdaemon: Recording cxl_generic_event events
rasdaemon: Recording cxl_general_media_event events
rasdaemon: Recording cxl_dram_event events
rasdaemon: Recording cxl_memory_module_event events
rasdaemon: Recording cxl_memory_sparing_event events
rasdaemon: Recording devlink_event events
rasdaemon: Recording disk_errors events
rasdaemon: Recording extlog_event events
rasdaemon: Recording mc_event events
rasdaemon: Recording memory_failure_event events
rasdaemon: Recording non_standard_event events
rasdaemon: Recording reri_event events
rasdaemon: Recording signal_event events
rasdaemon: Recording mce_record events
rasdaemon: Recording amp_payload0_event events
rasdaemon: Recording amp_payload1_event events
rasdaemon: Recording amp_payload2_event events
rasdaemon: Recording amp_payload3_event events
rasdaemon: Recording ampereone_payload0_event events
rasdaemon: Recording ampereone_payload1_event events
rasdaemon: Recording ampereone_payload2_event events
rasdaemon: Recording ampereone_payload3_event events
rasdaemon: Recording ampereone_payload4_event events
rasdaemon: Recording ampereone_payload5_event events
rasdaemon: Recording ampereone_payload6_event events
rasdaemon: Recording hip08_oem_type1_event_v2 events
rasdaemon: Recording hip08_oem_type2_event_v2 events
rasdaemon: Recording hip08_pcie_local_event_v2 events
rasdaemon: Recording hisi_common_section_v2 events
rasdaemon: Recording jm_payload0_event events
rasdaemon: Recording nvidia_ns_event events
rasdaemon: Recording nvidia_vera_ns_event events
rasdaemon: Recording yitian_ddr_reg_dump_event events
rasdaemon: Database backend started: sqlite3.
rasdaemon: Listening to events for cpus 0 to 1
rasdaemon: memory_failure_event store: 0xaaaae7de3d68
rasdaemon: register inserted at db
           <...>-295   [000] .....     0.000010 memory_failure_event [ALERT] 2026-10-28 03:54:03 +0000 pfn=0x4e620 page_type=dirty LRU page action_result=Recovered 
rasdaemon: Received signal Terminated. Stopping rasdaemon.

Comparison with a passing run

Passing result from 20261027T033459Z: open the successful report · GitHub Actions run

Passing check: Poison statistics must report a nonzero count after poisoning

Evidence difference (passing → failed)

--- passing 20261027T033459Z
+++ failed 20261028T035110Z
@@ -1,6 +1,6 @@
 Threshold: 0 (set by the poison-page-stat test in this historical run) kB
 Expected warning: Poison page statistics exceeded threshold:
-Warning observed: Yes
+Warning observed: No
 Hardware corrupted: Not captured by this run
 Hardware corrupted pages: not recorded
 Threshold exceeded: No
@@ -10,6 +10,5 @@
   rasdaemon: ras:memory_failure_event event enabled
   rasdaemon: Enabled event ras:memory_failure_event
   rasdaemon: Recording memory_failure_event events
-  rasdaemon: Poison page statistics exceeded threshold: 4 kB (threshold: 0 kB)
-  rasdaemon: memory_failure_event store: 0xaaaad3052d68
-  <...>-294   [000] .....     0.000011 memory_failure_event [ALERT] 2026-10-27 03:37:53 +0000 pfn=0x4e0f0 page_type=dirty LRU page action_result=Recovered
+  rasdaemon: memory_failure_event store: 0xaaaae7de3d68
+  <...>-295   [000] .....     0.000010 memory_failure_event [ALERT] 2026-10-28 03:54:03 +0000 pfn=0x4e620 page_type=dirty LRU page action_result=Recovered