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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>> 
>> 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?


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

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux