Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)

On Thu, 2006-04-13 at 19:53 +0200, Herbert Poetzl wrote:
On Thu, Apr 13, 2006 at 04:21:18PM +0200, 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?

here is the same oops with 3/1 split and the bootup log


Hi Herbert,

Looks to be the same stack as earlier, Is there any modules compiled in
that were removed before you tried to mount the XFS filesystem ?

Can you send me the .config file.

chandra

<snip>

--

----------------------------------------------------------------------
Chandra Seetharaman | Be careful what you choose....
- sekharan@xxxxxxxxxx | .......you may get it.
----------------------------------------------------------------------


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