Re: [BUG] NULL deref in swapin_readahead

[Wouter M. Koolen]

On 11/11/2011 12:07 PM, Rafael J. Wysocki wrote:
> Well, the trace doesn't indicate how the problem is related to the
> suspend/resume code paths.
>
> Is this a regression for you?
>
> Thanks,
> Rafael
Hi Rafael,

This problem manifests itself when resuming from RAM, but only very 
infrequently. This is the third occurrence since I started using this 
machine three months ago. I suspend it to RAM at least twice a day. The 
previous two occurrences were on 3.0. So not a clear regression in that 
sense. (Note this is from memory, I didn't record those other two oopses)

However, since it happens immediately upon resume, I suspected it was 
related. Would you have any tips for stress testing resumes? If I can 
increase the reproducibility then I could try to bisect it.

Or do you think it better, judging from the back trace, to forward this 
to some other subsystem maintainer? Please do then, I obviously don't 
know how to read backtraces.

Thanks,

Wouter


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/