On 1/6/21 5:38 PM, Kai Huang wrote: >> Could we dump out the *actual* error code with a WARN(), please? If we >> see a warning, I'd rather not have to disassemble the instructions and >> check against register values to see whether the error code was sane. > Sure. But WARN_ONCE() should be used, right, instead of WARN()? Whatever will let you get a printf-format string out and only happens once.