Hi here are the config file the *-defconfig boot, the *-debian crash just at first second. jeanseb Le Wed, 07 Apr 2010 11:52:36 +0200, Michal Suchanek <michal.suchanek@ruk.cuni.cz> a écrit : > > On 04/07/2010 05:22 AM, Ben Hutchings wrote: > > On Tue, 2010-04-06 at 17:58 +0100, Ben Hutchings wrote: > > > >> On Tue, Apr 06, 2010 at 07:14:15PM +0200, Michal Suchanek wrote: > >> > >>> On 04/03/2010 09:32 PM, Ben Hutchings wrote: > >>> > >>>> Please report this upstream at<https://bugzilla.kernel.org> > >>>> under product 'Platform Specific/Hardware', component 'i386'. > >>>> Let us know the bug number so we can track it. > >>>> > >>>> > >>>> > >>> AFAICT this is not an upstream issue. Running make menuconfig and > >>> just saving the config in a fresh 2.6.32.11 kernel results in the > >>> values of these options that work for me. > >>> > >> Ah, so your previous config diff was reversed. I understand now. > >> > > Alright, I'm thoroughly confused. The Debian config, the Kconfig > > default and the defconfig all agree that > > CONFIG_PHYSICAL_ALIGN=0x1000000. CONFIG_MMAP_MIN_ADDR is > > irrelevant as it only restricts virtual addresses. Whatever the > > problem is, it's nothing to do with these settings. You need to > > send us real config files instead of speculating. > > > > > I can, of course, send verbatim config files. > > However, the change that breaks the kernel for me is in these > options, there is no other difference. > > The physical align number in the Debian config in current kernels > which fails for me is > > 0x1 000 000 > > while the one I get by configuring clean 2.6.32.11 source is > > 0x100 000 > > which is what I have in the running kernel. > > Thanks > > Michal
Attachment:
config-2.6.33.1-debian
Description: Binary data
Attachment:
config-2.6.33.1-defconfig
Description: Binary data