git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Git Mailing List <git@vger.kernel.org>, Junio C Hamano <junkio@cox.net>
Subject: Re: 2.6.21-rc1: known regressions (part 2)
Date: Mon, 5 Mar 2007 15:04:59 +0100	[thread overview]
Message-ID: <20070305140459.GA8464@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0703020824580.3953@woody.linux-foundation.org>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Fri, 2 Mar 2007, Ingo Molnar wrote:
> > 
> > but the conclusion is clear: if multiple bugs are present in the 
> > search area then it gets quite difficult to sort it out via 
> > git-bisect - but it's not impossible either. The following 
> > git-bisect enhancement could have made things easier for me:
> > 
> >    git-bisect mark-must-have <tree>
> 
> It's not quite that easy.
> 
> In _your_ case, you always just wanted to try to apply a particular 
> patch if it applied cleanly.

ok, agreed.

Suspend/resume bugs are a bit special anyway because so much stuff 
happens in an 'invisible' way during suspend/resume that any 
problem/hang during that 'looks like' the same bug symtpom: a hung 
resume.

so i'll put more effort into providing more suspend/resume debugging 
facilities - we have way too few tools of directly debugging them.

	Ingo

  reply	other threads:[~2007-03-05 14:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070227102109.GG6745@elf.ucw.cz>
     [not found] ` <20070227103021.GA2250@kernel.dk>
     [not found]   ` <20070227103407.GA17819@elte.hu>
     [not found]     ` <20070227105922.GD2250@kernel.dk>
     [not found]       ` <20070227111515.GA4271@kernel.dk>
     [not found]         ` <20070301093450.GA8508@elte.hu>
     [not found]           ` <20070301104117.GA22788@elte.hu>
     [not found]             ` <20070301145204.GA25304@elte.hu>
     [not found]               ` <Pine.LNX.4.64.0703011536450.12485@woody.linux-foundation.org>
     [not found]                 ` <20070302072100.GB30634@elte.hu>
2007-03-02  8:04                   ` 2.6.21-rc1: known regressions (part 2) Ingo Molnar
2007-03-02 10:20                     ` Ingo Molnar
2007-03-02 10:22                       ` [patch] KVM: T60 resume fix Ingo Molnar
2007-03-02 11:39                         ` Michael S. Tsirkin
2007-03-03  8:22                           ` Avi Kivity
2007-03-03  8:21                         ` Avi Kivity
2007-03-03 11:57                           ` Andrew Morton
2007-03-05  8:22                           ` Ingo Molnar
2007-03-05 10:23                         ` Michael S. Tsirkin
2007-03-05 10:29                           ` Ingo Molnar
2007-03-02 16:36                       ` 2.6.21-rc1: known regressions (part 2) Linus Torvalds
2007-03-05 14:04                         ` Ingo Molnar [this message]
2007-03-05 15:44                     ` Michael S. Tsirkin
2007-03-05 16:14                     ` Michael S. Tsirkin
2007-03-05 16:41                       ` Ingo Molnar
2007-03-05 18:16                       ` Jens Axboe

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=20070305140459.GA8464@elte.hu \
    --to=mingo@elte.hu \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).