From: Con Kolivas <kernel@kolivas.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Herbert Poetzl <herbert@13thfloor.at>, Jes Sorensen <jes@sgi.com>,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
linux-xfs@oss.sgi.com, xfs-masters@oss.sgi.com,
stern@rowland.harvard.edu, sekharan@us.ibm.com, akpm@osdl.org,
David Chinner <dgc@sgi.com>
Subject: Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
Date: Fri, 14 Apr 2006 00:32:10 +1000 [thread overview]
Message-ID: <200604140032.12086.kernel@kolivas.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0604131618350.17374@yvahk01.tjqt.qr>
On Friday 14 April 2006 00:21, Jan Engelhardt wrote:
> >> Looks strange, the faulting address is in the same region as the
> >> eip. I am not that strong on x86 layouts, so I am not sure whether
> >> 0x78xxxxxx is the kernel's mapping or it's module space. Almost looks
> >> like something else had registered a notifier and then gone away
> >> without unregistering it.
> >
> >sorry, the essential data I didn't provide here is
> >probably that I configured the 2G/2G split, which for
> >unknown reasons actually is a 2.125/1.875 split and
> >starts at 0x78000000 (instead of 0x80000000)
>
> That's how it is coded in arch/i386/Kconfig. It says 78 rather than 80.
> Maybe Con has an idea?
Follow this thread backwards from this point:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113690295909937&w=2
--
-ck
next prev parent reply other threads:[~2006-04-13 14:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 5:21 2.6.17-rc1 did break XFS Herbert Poetzl
2006-04-13 5:35 ` Nathan Scott
2006-04-13 9:23 ` Keith Owens
2006-04-13 14:17 ` Jan Engelhardt
2006-04-13 9:36 ` Keith Owens
2006-04-13 15:12 ` Alan Stern
2006-04-13 7:23 ` notifier chain problem? (was Re: 2.6.17-rc1 did break XFS) David Chinner
2006-04-13 8:40 ` Jes Sorensen
2006-04-13 13:50 ` Herbert Poetzl
2006-04-13 14:10 ` Jes Sorensen
2006-04-13 14:21 ` Jan Engelhardt
2006-04-13 14:32 ` Con Kolivas [this message]
2006-04-13 17:53 ` Herbert Poetzl
2006-04-13 18:38 ` Chandra Seetharaman
2006-04-14 1:39 ` Herbert Poetzl
2006-04-13 18:52 ` Jan Engelhardt
2006-04-14 1:30 ` Herbert Poetzl
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=200604140032.12086.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=dgc@sgi.com \
--cc=herbert@13thfloor.at \
--cc=jengelh@linux01.gwdg.de \
--cc=jes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=sekharan@us.ibm.com \
--cc=stern@rowland.harvard.edu \
--cc=xfs-masters@oss.sgi.com \
/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