Re: 2.6.29-rc2 dies on startup

[Ferenc Wagner]

Ferenc Wagner <wferi@xxxxxxx> writes:

> Arve HjÃnnevÃg <arve@xxxxxxxxxxx> writes:
>
>> On Sun, Jan 25, 2009 at 10:46 PM, Andrew Morton
>> <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
>>
>>> At a guess I'd say that drivers/staging/android/ram_console.c is calling
>>> the reed-solomon code earlier than it's expecting.  But that might be
>>> totally wrong.
>>
>> Yes, but it also is trying to use a zero sized buffer at virtual
>> address 0 so it will not work much better if you turn off ecc.
>
> This sounds understandable given that the defaults are
>
> CONFIG_ANDROID_RAM_CONSOLE_EARLY_ADDR=0x0
> CONFIG_ANDROID_RAM_CONSOLE_EARLY_SIZE=0x0
>
>> This patch (to the android kernel tree) add some validation:
>
> Compiling it now (on the vanilla tree).

Fine, this patch helps.  Instead of

[    0.000000] Detected 1536.828 MHz processor.
[    0.004000] Console: colour VGA+ 80x25
[    0.004000] console [ttyS0] enabled
[    0.004000] BUG: unable to handle kernel paging request at f000e816
[    0.004000] IP: [<c0190b5c>] kmem_cache_alloc+0x2d/0x95
[...]

now I get

[    0.000000] Detected 1537.027 MHz processor.
[    0.004000] Console: colour VGA+ 80x25
[    0.004000] console [tty0] enabled
[    0.004000] ram_console: buffer (null), invalid size 0, datasize -12
[    0.004000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[...]
-- 
Thanks,
Feri.
--
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/