From: Greg KH <greg@kroah.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc1 kernel init oops
Date: Sun, 29 Jan 2006 20:44:36 -0800 [thread overview]
Message-ID: <20060130044436.GA13244@kroah.com> (raw)
In-Reply-To: <20060129165732.03446fc3.rdunlap@xenotime.net>
On Sun, Jan 29, 2006 at 04:57:32PM -0800, Randy.Dunlap wrote:
> furthermore, this happens on 2.6.16-rc1 and 2.6.16-rc1-git4,
> but <platform_notify> is not at the same memory address in
> my builds, so it smells more like a bad ptr reference
> somewhere than like bad memory IMO.
Hm, can you do a git bisect from 2.6.15 to 2.6.16-rc1 to see if you can
find this?
thanks,
greg k-h
next prev parent reply other threads:[~2006-01-30 4:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 1:18 2.6.16-rc1 kernel init oops Randy.Dunlap
2006-01-29 1:55 ` Randy.Dunlap
2006-01-29 19:00 ` Greg KH
2006-01-29 19:19 ` Randy.Dunlap
2006-01-29 20:19 ` Greg KH
2006-01-29 21:08 ` Randy.Dunlap
2006-01-29 23:07 ` Randy.Dunlap
2006-01-30 0:57 ` Randy.Dunlap
2006-01-30 4:44 ` Greg KH [this message]
2006-02-02 5:31 ` Randy.Dunlap
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=20060130044436.GA13244@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.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
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