mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Glauber Costa" <glommer@gmail.com>
To: "Hugh Dickins" <hugh@veritas.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	"Glauber Costa" <gcosta@redhat.com>,
	"Ingo Molnar" <mingo@elte.hu>,
	"Carlos R. Mafra" <crmafra2@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Possible regression? 2.6.26-rc1: T61s failure after suspend/resume
Date: Fri, 9 May 2008 13:26:23 -0300	[thread overview]
Message-ID: <5d6222a80805090926v5baeb9ebw6b4dda98548a2933@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805091706390.11688@blonde.site>

On Fri, May 9, 2008 at 1:21 PM, Hugh Dickins <hugh@veritas.com> wrote:
> On Fri, 9 May 2008, Glauber Costa wrote:
>  >
>  > I can't reproduce it neither, and looking at the code over and over
>  > again, see no obvious point for the breakage. I'll try to reproduce it
>  > myself,
>  > to see if I can spot something. But correct me if I'm wrong, this is
>  > all 64-bit machines, right?
>  >
>  > I'm stuck with mostly 32-bit hardware, but will give it a try anyway.
>
>  The machine is 64-bit capable (Core2 Duo), but the kernels I'm running
>  for this are 32-bit, so I doubt that the 64-bitability is relevant.
>  I'd love to see what happens with a 64-bit kernel, but I never get
>  back from suspend with it (and that's not a recent regression).
>  Carlos is also seeing this with a 32-bit kernel (on P4 Xeon with HT).
>
>  Please don't take my git bisection result too seriously: that's where
>  it led when I fudged things around enough, and treated blank screens
>  as manifestations of the problem, which very likely they're not
>  (there's some other bug which makes it very variable how quickly
>  I resume).  And also, I wasn't checking how many cpus came up each
>  time: I wouldn't be surprised if at some points in your series only
>  one would come up, which would then look like a "good" point to me.
>
This is very unlikely. Exactly because I knew problems were likely to
arise in such a delicate thing, I was
extremely careful to make it not an issue. But yeah, ultimately, it can happen.


-- 
Glauber Costa.
"Free as in Freedom"
http://glommer.net

"The less confident you are, the more serious you have to act."

  reply	other threads:[~2008-05-09 16:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08 19:53 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
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 [this message]
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=5d6222a80805090926v5baeb9ebw6b4dda98548a2933@mail.gmail.com \
    --to=glommer@gmail.com \
    --cc=crmafra2@gmail.com \
    --cc=gcosta@redhat.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tytso@mit.edu \
    /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

all inboxes | Powered by JetHome®