lkml.org 
[lkml]   [2006]   [Apr]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
From
Date
>>>>> "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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-04-13 10:43    [W:0.104 / U:1.704 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site