All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sven Joachim <svenjoac@gmx.de>, Ingo Molnar <mingo@kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel panic after suspend/resume
Date: Wed, 18 Apr 2012 00:13:30 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1204180013180.2542@ionos> (raw)
In-Reply-To: <CA+55aFychSQgAG8raDq9rvXm3Lq7GFdByCd3-NZERieyTdAc2g@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 793 bytes --]


On Tue, 17 Apr 2012, Linus Torvalds wrote:

> On Tue, Apr 17, 2012 at 11:12 AM, Sven Joachim <svenjoac@gmx.de> wrote:
> >
> > So far, it has repeated itself every time I suspended with 3.4-rc3,
> > i.e. three times.  That's a small sample, so the bisection might not be
> > reliable (especially since the crashes happened with delay), but I can
> > try.
> >
> >>  - how sure are you that rc2 is fine?
> >
> > Reasonably sure, I had been running rc2 for the whole last week and
> > suspended about 20 times without any problems whatsoever.
> 
> Ok, that sounds very hopeful for bisection. If it has happened three
> out of three times, it doesn't sound like it's some subtle timing
> race.

Sven, can you please provide the output of /proc/timer_list befor you
suspend ?

Thanks,

        tglx

  reply	other threads:[~2012-04-17 22:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16  1:49 Linux 3.4-rc3 Linus Torvalds
2012-04-17 15:24 ` kernel panic after suspend/resume (was: Linux 3.4-rc3) Sven Joachim
2012-04-17 16:00   ` Linus Torvalds
2012-04-17 18:12     ` kernel panic after suspend/resume Sven Joachim
2012-04-17 19:50       ` Linus Torvalds
2012-04-17 22:13         ` Thomas Gleixner [this message]
2012-04-18  5:27           ` Sven Joachim
2012-04-17 21:21     ` kernel panic after suspend/resume (was: Linux 3.4-rc3) Rafael J. Wysocki
2012-04-18  8:22       ` kernel panic after suspend/resume Sven Joachim
2012-04-18  9:36         ` Rafael J. Wysocki
2012-04-18 10:08         ` Thomas Gleixner
2012-04-18 11:03           ` Sven Joachim
2012-04-18 12:07           ` [tip:timers/urgent] tick: Fix oneshot broadcast setup really tip-bot for Thomas Gleixner
2012-04-18 13:19             ` Shilimkar, Santosh
2012-04-18 14:18               ` Santosh Shilimkar
2012-04-18 15:31                 ` Thomas Gleixner
2012-04-18 15:51                   ` Santosh Shilimkar
2012-04-19  2:27                   ` Suresh Siddha
2012-04-19  8:29                     ` Thomas Gleixner
2012-04-19 10:14                       ` Santosh Shilimkar
2012-04-19 10:37                       ` Sven Joachim
2012-04-19 19:38                     ` [tip:timers/urgent] tick: Fix the spurious broadcast timer ticks after resume tip-bot for Suresh Siddha
2012-04-19 19:37                   ` [tip:timers/urgent] tick: Ensure that the broadcast device is initialized tip-bot for Thomas Gleixner

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=alpine.LFD.2.02.1204180013180.2542@ionos \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rjw@sisk.pl \
    --cc=svenjoac@gmx.de \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.