From: Chris Rankin <rankincj@yahoo.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>, Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] Linux 2.6.20.2 - unable to handle kernel paging request - still accessing freed memory
Date: Fri, 16 Mar 2007 08:31:42 +0000 (GMT) [thread overview]
Message-ID: <30938.71164.qm@web52909.mail.yahoo.com> (raw)
In-Reply-To: <84144f020703160023l61ef82a4yd3d64d2f4fe9f1a0@mail.gmail.com>
--- Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On 3/16/07, Greg KH <gregkh@suse.de> wrote:
> > Is there any way you can use 'git bisect' to try to track down the root
> > cause of this?
>
> Chris, If 2.6.19 works for you, could you please do a git bisect for
> this bug? See the following URL for details:
>
> http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
That would take ages - the only reason I kept on plugging away with winecfg last night was because
I was fairly certain the kernel was going to "oops" eventually (which it did). But when exactly
would I be able to declare a kernel "good" during a "git bisect"?
Cheers,
Chris
___________________________________________________________
What kind of emailer are you? Find out today - get a free analysis of your email personality. Take the quiz at the Yahoo! Mail Championship.
http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk
next prev parent reply other threads:[~2007-03-16 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 14:09 [BUG] Linux 2.6.20.2 - unable to handle kernel paging request - still accessing freed memory Chris Rankin
2007-03-14 11:18 ` Pekka Enberg
2007-03-14 11:23 ` Pekka Enberg
2007-03-15 22:27 ` Greg KH
2007-03-16 7:23 ` Pekka Enberg
2007-03-16 8:31 ` Chris Rankin [this message]
2007-03-16 10:25 ` Pekka Enberg
2007-03-16 11:30 ` Chris Rankin
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=30938.71164.qm@web52909.mail.yahoo.com \
--to=rankincj@yahoo.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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