On Fri, 19 Mar 2010, Michal Suchanek wrote: > > I found the config change which breaks the kernel. A kernel which > differs from the official one only in this does boot, the official > one does not. I am quite sure there are no messages to see, this > only affects very early stages of boot as the build log after > applying the change shows only very few objects dealing with > realmore are rebuilt. > > Thanks > > Michal
thanks for tracking that down, had guessed it was PCIEASPM, which it wasn't. this may well be a bios issue, please check cat /sys/devices/virtual/dmi/id/bios_version or cat /sys/devices/virtual/dmi/id/bios_date and cat /sys/devices/virtual/dmi/id/board_name and see if there is a bios update available? > --- boot/config-2.6.33-686 2010-03-19 17:34:53.000000000 +0100 > +++ boot/config-2.6.33-686 2010-03-19 15:46:19.000000000 +0100 > @@ -1,7 +1,7 @@ > # > # Automatically generated make config: don't edit > # Linux kernel version: 2.6.33-686 > -# Fri Mar 19 17:34:53 2010 > +# Fri Mar 19 15:46:19 2010 > # > # CONFIG_64BIT is not set > CONFIG_X86_32=y > @@ -381,7 +381,7 @@ > CONFIG_VIRT_TO_BUS=y > CONFIG_MMU_NOTIFIER=y > CONFIG_KSM=y > -CONFIG_DEFAULT_MMAP_MIN_ADDR=65536 > +CONFIG_DEFAULT_MMAP_MIN_ADDR=4096 > CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y > CONFIG_MEMORY_FAILURE=y > CONFIG_HWPOISON_INJECT=m > @@ -410,7 +410,7 @@ > CONFIG_PHYSICAL_START=0x1000000 > CONFIG_RELOCATABLE=y > CONFIG_X86_NEED_RELOCS=y > -CONFIG_PHYSICAL_ALIGN=0x1000000 > +CONFIG_PHYSICAL_ALIGN=0x100000 > CONFIG_HOTPLUG_CPU=y > # CONFIG_COMPAT_VDSO is not set > # CONFIG_CMDLINE_BOOL is not set > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
