Hi Huang, The original system needs to ship to our customer ASAP. Disabling ghes is sufficient for the time being for that. As such, I have set up an identical system as a temporary master for another cluster to continue this testing. I have applied your patch. Here is the output of dmesg | grep GHES so far: [ 9.272198] GHES: gar mapped: 0, 0xbf7b5ff0 [ 9.280782] GHES: gar mapped: 0, 0xbf7b6200 [ 9.285102] [Firmware Warn]: GHES: Poll interval is 0 for generic hardware error source: 1, disabled. I have the serial console activated and stress tests started back up. I'll reply with the output once I get another panic. Thanks! Rick > Hi, Rick, > > It appears that panic occurs in acpi_atomic_read. I think the most > likely cause is that the acpi_generic_address is not pre-mapped. Can > you try the patch attached? > > It will print registers mapped and accessed. To use it, run the > following command line before workload. > > dmesg | grep GHES > > Then try to find something like > > GHES: gar accessed: x, xxxx > > in kernel log when panic occurs. > > Best Regards, > Huang Ying > > -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
