From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp)) Date: Thu, 15 Nov 2012 12:22:39 +0100 Subject: Kernel uncompression error In-Reply-To: <20121115093233.GM3290@n2100.arm.linux.org.uk> (Russell King's message of "Thu, 15 Nov 2012 09:32:33 +0000") References: <20121114173453.GJ3290@n2100.arm.linux.org.uk> <50A4841F.9070507@gmail.com> <20121115093233.GM3290@n2100.arm.linux.org.uk> Message-ID: <87mwyjw1og.fsf@lebrac.rtp-net.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Russell King - ARM Linux 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