public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Hugh Dickins <hugh@veritas.com>,
	Glauber Costa <gcosta@redhat.com>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Venki Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: Possible regression?  2.6.26-rc1: T61s failure after suspend/resume
Date: Fri, 9 May 2008 09:53:50 -0400	[thread overview]
Message-ID: <20080509135350.GA9681@mit.edu> (raw)
In-Reply-To: <1210333785.13978.247.camel@twins>

On Fri, May 09, 2008 at 01:49:45PM +0200, Peter Zijlstra wrote:
> > > But I'm failing to see how IRQs get enabled between
> > > sched_clock_idle_sleep_event() and sched_clock_idle_wakeup_event() in
> > > acpi_idle_enter_simple().
> > 
> > If this point in Ted's bisection was without your idle irq fixes
> > (that patch that added trace_hardirqs_on to __sti_mwait, amongst
> > other things), would that account for it?
> 
> Ah, that might, I'll do a checkout of his specific revision to verify.
> 

I wouldn't worry about it too much, it's not there in 2.6.26-rc1 as
far as I can tell.  And it may or may not have anything to do with the
fact that my system locked up about 60 seconds afterwards, before I
had a chance to login via X and do a suspend/resume cycle (since
that's the most reliable way to reproduce my regression).  I'm
travelling this week, but when I have time, I'll try disabling X,
doing a suspend/resume cycle, and then doing a kerenl build -j3 and
see if I can provoke your symptoms.

					- Ted

  reply	other threads:[~2008-05-09 13:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08 19:53 Possible regression? 2.6.26-rc1: T61s failure after suspend/resume Theodore Ts'o
2008-05-08 21:48 ` Hugh Dickins
2008-05-09  2:59   ` Theodore Tso
2008-05-09  7:31     ` Hugh Dickins
2008-05-09 11:16     ` Peter Zijlstra
2008-05-09 11:36       ` Hugh Dickins
2008-05-09 11:49         ` Peter Zijlstra
2008-05-09 13:53           ` Theodore Tso [this message]
2008-05-09 14:18   ` Carlos R. Mafra
2008-05-09 15:28   ` Glauber Costa
2008-05-09 16:21     ` Hugh Dickins
2008-05-09 16:26       ` Glauber Costa
2008-05-09 16:47       ` Adrian Bunk
2008-05-08 21:52 ` Rafael J. Wysocki
2008-05-09  2:44   ` Possible regression? 2.6.26-rc1: X61s " Theodore Tso
2008-05-09  9:49     ` Ingo Molnar
2008-05-12  2:03       ` Theodore Tso
2008-05-12 11:35         ` Theodore Tso
2008-05-12 12:28         ` Theodore Tso

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=20080509135350.GA9681@mit.edu \
    --to=tytso@mit.edu \
    --cc=gcosta@redhat.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=venkatesh.pallipadi@intel.com \
    /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