xfs-masters
[Top] [All Lists]

[xfs-masters] Re: notifier chain problem? (was Re: 2.6.17-rc1 did break

To: Herbert Poetzl <herbert@xxxxxxxxxxxx>
Subject: [xfs-masters] Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
From: Jes Sorensen <jes@xxxxxxx>
Date: 13 Apr 2006 04:40:54 -0400
Cc: Linux Kernel ML <linux-kernel@xxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx, xfs-masters@xxxxxxxxxxx, stern@xxxxxxxxxxxxxxxxxxx, sekharan@xxxxxxxxxx, akpm@xxxxxxxx, David Chinner <dgc@xxxxxxx>
In-reply-to: <20060413072325.GF2732@xxxxxxxxxxxxxxxxx>
References: <20060413052145.GA31435@xxxxxxxxxxxxxxxxx> <20060413072325.GF2732@xxxxxxxxxxxxxxxxx>
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4
>>>>> "David" == David Chinner <dgc@xxxxxxx> 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



<Prev in Thread] Current Thread [Next in Thread>