On 12-07-16, 14:24, Rafael J. Wysocki wrote: > On Monday, July 11, 2016 03:46:01 PM Viresh Kumar wrote: > > Yeah and I am not sure how should I go ahead about this issue now :) > > FWIW, I think the reason why the "synchronous printk" works is because after > disabling the non-boot CPU, the only remaining one disables local interrupts > and won't do any async work any more until resume.
Right. After disabling interrupts, the other printk messages gets printed only after the system resumes. I am not that worried about printk not working after that point, but on how does asynchronous printing affect the system to crash or come to a complete hang? Any clues on why that can happen ? > But you started to talk about suspend/resume and such at one point and that > message should have been CCed to linux-pm. > > And the reason why is because problems you see during suspend/resume may very > well be suspend-specific and not visible otherwise. In which case you'll > likely need input from the people on linux-pm. Yeah, I *should* have cc'd the PM list then. Thanks for helping out Rafael :) -- viresh
