Bug#572488: linux-image-2.6.33: fails to boot

To: Michal Suchanek <michal.suchanek@ruk.cuni.cz>
Cc: 572488@bugs.debian.org
Subject: Bug#572488: linux-image-2.6.33: fails to boot
From: Jonathan Nieder <jrnieder@gmail.com>
Date: Thu, 25 Aug 2011 22:00:50 -0500
Message-id: <[🔎] 20110826030050.GA3479@elie.gateway.2wire.net>
Reply-to: Jonathan Nieder <jrnieder@gmail.com>, 572488@bugs.debian.org
In-reply-to: <1270857830.2176.44.camel@localhost>
References: <20100307150854.GA8156@stro.at> <4BA3AF67.7080200@ruk.cuni.cz> <20100319175744.GE4424@stro.at> <4BA644F5.8060309@ruk.cuni.cz> <1270323138.12516.347.camel@localhost> <4BBB6BE7.5000108@ruk.cuni.cz> <20100406165829.GS16821@decadent.org.uk> <1270610559.2178.21.camel@localhost> <4BBC55E4.5090401@ruk.cuni.cz> <1270857830.2176.44.camel@localhost>

Hi Michal,

Ben Hutchings wrote:

> My clean 2.6.32.11 source disagrees with you:
>
> $ git checkout v2.6.32.11
> ...
> $ make ARCH=i386 defconfig
> ...
> $ grep CONFIG_PHYSICAL_ALIGN .config
> CONFIG_PHYSICAL_ALIGN=0x1000000
> $ make ARCH=x86_64 defconfig
> ...
> $ grep CONFIG_PHYSICAL_ALIGN .config
> CONFIG_PHYSICAL_ALIGN=0x1000000
>
> So, you should report a bug upstream that the default does not work for
> your system.

Now I am in suspense: did you end up tracking down this boot failure?
Did it get reported upstream or resolved some other way?  Does this
mac boot nowadays?

Reply to:

Follow-Ups:
- Bug#572488: linux-image-2.6.33: fails to boot
  - From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

Prev by Date: Bug#571761: linux-image-2.6.32-2-686: 2.6.32 required noapic on Acer Travelmate 430 where earlier kernels did not
Next by Date: Bug#576077: linux-image-2.6.32-trunk-amd64: btrfs allocation failed while accessing from fslint
Previous by thread: Bug#571761: linux-image-2.6.32-2-686: 2.6.32 required noapic on Acer Travelmate 430 where earlier kernels did not
Next by thread: Bug#572488: linux-image-2.6.33: fails to boot
Index(es):
- Date
- Thread