LKML Archive on lore.kernel.org
 help / color / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Bob Tracy <rct@frus.com>,
	mcree@orcon.net.nz, linux-kernel@vger.kernel.org, rjw@sisk.pl,
	rth@twiddle.net, ink@jurassic.park.msu.ru,
	linux-scsi@vger.kernel.org, kay.sievers@vrfy.org, greg@kroah.com
Subject: Re: [BUG] 2.6.23-rc3 can't see sd partitions on Alpha
Date: Fri, 7 Dec 2007 12:37:34 +0100
Message-ID: <20071207113734.GA14598@elte.hu> (raw)
In-Reply-To: <20071207022646.373c92f5.akpm@linux-foundation.org>


* Andrew Morton <akpm@linux-foundation.org> wrote:

> > then the test of whether I bisected correctly is as simple as 
> > applying the commit and seeing if things break, because I'm running 
> > on the kernel corresponding to 
> > 2f1f53bdc6531696934f6ee7bbdfa2ab4f4f62a3 right now.  Let me give 
> > that a try and I'll report back.  Worst case, I'll have to start 
> > over and write off the past four days...
> 
> Gad.  I trust the second time will be faster.
> 
> git-bisect _is_ very error prone.  I find one of the problems is that 
> each step is so far apart in time that you forget what you were doing.  
> Did I remember to test that iteration?  Did I install the right 
> kernel?  etc.

i have a fully automated bootup-hang bisection script. It is based on 
"git-bisect run". I run the script, it builds and boots kernels fully 
automatically, and when the bootup fails (the script notices that via 
the serial log, which it continuously watches - or via a timeout, if the 
system does not come up within 10 minutes it's a "bad" kernel), the 
script raises my attention via a beep and i power cycle the test box. 
(yeah, i should make use of a managed power outlet to 100% automate it) 

So i dont have to a single manual decision anytime during the bisection. 
But the scripts are very much tied to my ad-hoc test environment so it 
would not be of much general use.

	Ingo

  reply index

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-18  5:20 rct
2007-11-25  6:38 ` Andrew Morton
2007-11-25 12:15   ` Rafael J. Wysocki
2007-11-26 13:48   ` rct
2007-11-30 22:30     ` Michael Cree
2007-11-30 22:42       ` Andrew Morton
2007-11-30 23:26         ` Rafael J. Wysocki
2007-12-02 20:53         ` Michael Cree
2007-12-03  1:17           ` rct
2007-12-04 12:16             ` Ingo Molnar
2007-12-04 15:36               ` rct
2007-12-05 17:30               ` rct
2007-12-07  0:16               ` rct
2007-12-07  0:33                 ` Andrew Morton
2007-12-07  5:07                   ` rct
2007-12-07 10:26                     ` Andrew Morton
2007-12-07 11:37                       ` Ingo Molnar [this message]
2007-12-07 13:39                       ` rct
2007-12-07 14:55                       ` rct
2007-12-07 15:05                         ` Ingo Molnar
2007-12-07 16:59                           ` rct
2007-12-07 18:06                             ` Ingo Molnar
2007-12-07 18:19                               ` Kay Sievers
2007-12-07 19:36                                 ` rct
2007-12-07 20:43                         ` Michael Cree
2007-12-07 21:19                           ` Kay Sievers
2007-12-07 22:39                             ` rct
2007-12-08  4:53                             ` rct
2007-12-08  5:05                             ` rct
2007-12-08 15:48                               ` Kay Sievers
2007-12-09  0:51                                 ` Michael Cree
2007-12-09  4:19                                   ` rct
2007-12-09 18:07                                     ` Ivan Kokshaysky
2007-12-10 15:08                                       ` rct
2007-12-10 23:12                                         ` Ivan Kokshaysky
2007-12-10 15:05                                 ` rct
2007-12-07 11:40                     ` Ingo Molnar
2007-12-07  5:42                   ` rct
2007-12-07  9:33                   ` Ingo Molnar
2007-12-07  0:44                 ` Rafael J. Wysocki

Reply instructions:

You may reply publically 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=20071207113734.GA14598@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mcree@orcon.net.nz \
    --cc=rct@frus.com \
    --cc=rjw@sisk.pl \
    --cc=rth@twiddle.net \
    /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

LKML Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git
	git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git
	git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git
	git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git
	git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git
	git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git
	git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git
	git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git
	git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \
		linux-kernel@vger.kernel.org
	public-inbox-index lkml

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git