From: Jes Sorensen <jes@sgi.com>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: 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: 13 Apr 2006 04:40:54 -0400 [thread overview]
Message-ID: <yq0k69tuauh.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <20060413072325.GF2732@melbourne.sgi.com>
>>>>> "David" == David Chinner <dgc@sgi.com> writes:
David> On Thu, Apr 13, 2006 at 07:21:45AM +0200, Herbert Poetzl wrote:
David> It looks like we landed on top of a a notifier call chain
David> implementation change in -rc1. However, this should not matter
David> to XFS because the interface to register_cpu_notifier() did not
David> change and XFS is completely abstracted away from the notifier
David> chain implementation. We do:
Dave,
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.
Herbert, any chance you can make the complete boot log up to the point
where it crashes, as well as a System.map and your .config available?
(probably not posted to all the lists :)
Cheers,
Jes
next prev parent reply other threads:[~2006-04-13 8:40 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 [this message]
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
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=yq0k69tuauh.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--cc=akpm@osdl.org \
--cc=dgc@sgi.com \
--cc=herbert@13thfloor.at \
--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
all inboxes | Powered by JetHome®