public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Wouter M. Koolen" <W.M.Koolen-Wijkstra@cwi.nl>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: len.brown@intel.com, pavel@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: [BUG] NULL deref in swapin_readahead
Date: Fri, 11 Nov 2011 12:27:32 +0000	[thread overview]
Message-ID: <4EBD14B4.5000201@cwi.nl> (raw)
In-Reply-To: <201111111307.02203.rjw@sisk.pl>


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



  reply	other threads:[~2011-11-11 12:27 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 [this message]
2011-11-11 23:55     ` Pavel Machek
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=4EBD14B4.5000201@cwi.nl \
    --to=w.m.koolen-wijkstra@cwi.nl \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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