From: Vivek Goyal <vgoyal@in.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: kmannth@us.ibm.com, lkml <linux-kernel@vger.kernel.org>,
andrew <akpm@osdl.org>
Subject: Re: [Bug] 2.6.18-rc4-mm2 panic in __unix_insert_socket x86_64
Date: Fri, 25 Aug 2006 11:24:28 -0400 [thread overview]
Message-ID: <20060825152428.GB8909@in.ibm.com> (raw)
In-Reply-To: <200608250829.46066.ak@suse.de>
On Fri, Aug 25, 2006 at 08:29:46AM +0200, Andi Kleen wrote:
> On Friday 25 August 2006 04:20, keith mannthey wrote:
> > On Tue, 2006-08-22 at 17:39 -0700, keith mannthey wrote:
> > > Hello all,
> > > Something from mm1 to mm2 brought this bug out. I didn't see any
> > > change in the unix socket code so I am not sure where to start. I am
> > > going to start bisecting patches. 2.6.18-rc4-mm1 was working as
> > > expected. I have already stepped around afs and smp alternatives errors
> > > but I haven't seen any errors related to this posted yet.
> >
> >
> > Ok finally finished all the rebuilds/reboots needed find the trouble
> > patch. What seems to be causing the problem is listed as
> >
> > Re-positioning the bss segment or
> > x86_64-mm-re-positioning-the-bss-segment.patch
> >
> > It seems something is getting trampled. Thoughts?
>
> Hmm, it seems to be outside _edata now. There are a couple of references,
> but I'm not sure they actually matter
>
It was outside _edata even before. So that should not make any difference.
It boots fine on my machine. Strange. I am looking into it.
Thanks
Vivek
prev parent reply other threads:[~2006-08-25 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 0:39 [Bug] 2.6.18-rc4-mm2 panic in __unix_insert_socket x86_64 keith mannthey
2006-08-25 2:20 ` keith mannthey
2006-08-25 6:29 ` Andi Kleen
2006-08-25 15:24 ` Vivek Goyal [this message]
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=20060825152428.GB8909@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=kmannth@us.ibm.com \
--cc=linux-kernel@vger.kernel.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