From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: Kernel uncompression error
Date: Thu, 15 Nov 2012 12:22:39 +0100 [thread overview]
Message-ID: <87mwyjw1og.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <20121115093233.GM3290@n2100.arm.linux.org.uk> (Russell King's message of "Thu, 15 Nov 2012 09:32:33 +0000")
Russell King - ARM Linux <linux@arm.linux.org.uk> writes:
> On Thu, Nov 15, 2012 at 01:56:47PM +0800, woody wrote:
>> On 11/15/2012 1:34 AM, Russell King - ARM Linux wrote:
>>> On Wed, Nov 14, 2012 at 10:23:55PM +0800, woody wrote:
>>>> I just built a 3.2.x ARM kernel and tried to have it boot by a boot
>>>> loader (vivi) on my s3c2410a ARM board. The kernel was built with
>>>> default configuration s3c2410.
>>>
>>> I reported that S3C2410 is totally dead with 3.x kernels about a month
>>> ago and got no response what so ever from anyone. I guess S3C2410 is
>>> just not cared for anymore.
>>>
>>> When I get sufficient motivation, I'll try and track down what's going
>>> wrong, but it means taking the old mailing list server (and now list
>>> archive) offline for a while.
>>>
>>> I don't think it's cache related; different image sizes seem to behave
>>> differently - and when they _do_ successfully decompress, they don't
>>> boot at all.
>>
>> Now I switched from 3.2.x kernel to the latest stable 3.6.6. And, I did
>> a lot of configuration to make the zImage size smaller, now it is 1.5M.
>> After download it to the board, I got another error:
>>
>> "Uncompressing Linux... done, booting the kernel."
>>
>> Then the kernel halted.
>>
>> I noticed, the dots (...) in the kernel log seems very short, is this a
>> clue or just normal?
>
> You've not told me anything I don't already know... As I said, it needs
> investigation as to what's going on. I was rather hoping that the Samsung
> people would look at it, but alas there seems to be zero interest from
> them.
I guess that a lot of people don't care anymore about 2410 or can't
help. For instance, the only serial port available on my h1940 is the IR
one and I don't have a device to receive the ir data anymore so this
won't help. I won't even talk about gta01, which has no support in
mainline. It may also be the usual -ENOTIME error.
Arnaud
next prev parent reply other threads:[~2012-11-15 11:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 14:23 Kernel uncompression error woody
2012-11-14 17:34 ` Russell King - ARM Linux
2012-11-14 23:40 ` Woody Wu
2012-11-15 5:56 ` woody
2012-11-15 9:32 ` Russell King - ARM Linux
2012-11-15 11:22 ` Arnaud Patard (Rtp) [this message]
2012-11-15 11:32 ` Vasily Khoruzhick
[not found] ` <CAAsE_ufdjZN31BXWTcq5XyRhx5YcoECRJVvARcNh8qT-AP1_jw@mail.gmail.com>
2012-11-15 9:33 ` Russell King - ARM Linux
2012-11-15 17:25 ` Woody Wu
2012-11-21 1:34 ` Woody Wu
2012-11-15 11:29 ` Vasily Khoruzhick
2012-11-15 11:31 ` Russell King - ARM Linux
2012-11-21 0:43 ` [PATCH] S3C24XX: Fix console baud rate guessing Domenico Andreoli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mwyjw1og.fsf@lebrac.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).