From: Pavel Machek <pavel@ucw.cz>
To: "Wouter M. Koolen" <W.M.Koolen-Wijkstra@cwi.nl>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
len.brown@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] NULL deref in swapin_readahead
Date: Sat, 12 Nov 2011 00:55:02 +0100 [thread overview]
Message-ID: <20111111235502.GA29116@elf.ucw.cz> (raw)
In-Reply-To: <4EBD14B4.5000201@cwi.nl>
Hi!
> >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.
It should be possible to configure machine for Wake-on-lan on
wake-on-rtc, then run s2ram in a loop...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2011-11-11 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 11:30 [BUG] NULL deref in swapin_readahead Wouter M. Koolen
2011-11-11 12:07 ` Rafael J. Wysocki
2011-11-11 12:27 ` Wouter M. Koolen
2011-11-11 23:55 ` Pavel Machek [this message]
2011-11-17 1:57 ` Hugh Dickins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111111235502.GA29116@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=W.M.Koolen-Wijkstra@cwi.nl \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox