From: Bongani Hlope <bonganilinux@mweb.co.za>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Shutdown and Reboot Regression 2.6.25-rc[78]
Date: Sat, 12 Apr 2008 09:04:11 +0200 [thread overview]
Message-ID: <200804120904.11423.bonganilinux@mweb.co.za> (raw)
In-Reply-To: <alpine.LFD.1.00.0804111605390.3143@woody.linux-foundation.org>
On Saturday 12 April 2008 01:12:37 Linus Torvalds wrote:
> On Fri, 11 Apr 2008, Bongani Hlope wrote:
> > After about 4 restarts and 4 reboots, 2.6.25-rc9 seems to work fine with
> > and without the revert. I'll do some more testing. The assembly output
> > files for kernel/printk.c don't seem that different between rc9 and rc7.
> > I'll see what else I can test.
>
> Ok, I suspect it may be timing-dependent and slightly random.
>
Nope it happens all the time with rc7 and rc8....
> Sadly, that is absolutely the case where "git bisect" works the worst. The
> end result of bisection will basically be _totally_ random if even one of
> the "git bisect bad/good" choises were wrong - doing a binary search is
> a very efficient way to find the buggy commit, but it also means that a
> single wrong turn will efficiently find a commit that is somewhere totally
> different.
>
git revert 266c2e0abeca649fa6667a1a427ad1da507c6375 on rc8 makes rc8 work
again.
next prev parent reply other threads:[~2008-04-12 7:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 20:41 Bongani Hlope
2008-04-11 20:58 ` Linus Torvalds
2008-04-11 21:42 ` Bongani Hlope
2008-04-11 23:12 ` Linus Torvalds
2008-04-12 7:04 ` Bongani Hlope [this message]
2008-04-11 21:42 ` Alexey Dobriyan
2008-04-12 7:05 ` Bongani Hlope
2008-04-14 15:08 ` Linus Torvalds
2008-04-14 15:09 ` Linus Torvalds
2008-04-15 19:50 ` Bongani Hlope
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=200804120904.11423.bonganilinux@mweb.co.za \
--to=bonganilinux@mweb.co.za \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--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
all inboxes | Powered by JetHome®