Am 09.11.2016 um 07:34 schrieb Dennis Luehring:
im using cross-linux-from-scratch manual/script for building the non-x86_64
platforms
fyi
after using the crosscompilers from the gcc-5-crossports packages
(http://packages.ubuntu.com/source/xenial/gcc-5-cross-ports)
alpha-linux-gnu-gcc-5
spa
Am 07.11.2016 um 18:21 schrieb Laszlo Ersek:
its not alpha related same error happens with ppc64,sparc64,mips64...
so i tried to reproduce the errors also on x86_64 in qemu
building a tiny linux kernel 4.8.6 (~1MB) and a simple init (~1MB) based on
http://mgalgs.github.io/2015/05/16/how-to-bu
On 11/07/16 17:11, Dennis Luehring wrote:
> Am 07.11.2016 um 16:56 schrieb Laszlo Ersek:
>>> >so the second one couldn't be a problem with running out of memory -
>>> and
>>> >its not alpha related same error happens with ppc64,sparc64,mips64...
>> The second one*is* related to running out of memo
Am 07.11.2016 um 16:56 schrieb Laszlo Ersek:
>so the second one couldn't be a problem with running out of memory - and
>its not alpha related same error happens with ppc64,sparc64,mips64...
The second one*is* related to running out of memory. Initrd
decompression takes unintuitive amounts of me
On 11/07/16 15:38, Dennis Luehring wrote:
> Am 07.11.2016 um 15:12 schrieb Laszlo Ersek:
>> The second error message is incorrect in its own right (it's just
>> another symptom of running out of memory;
> there a two cpios
>
> big(~370MB) initrd.cpio + 1GB ram gives only this message: "Initramfs
>
Am 07.11.2016 um 15:15 schrieb Laszlo Ersek:
On 11/07/16 08:35, Dennis Luehring wrote:
> Am 04.11.2016 um 20:40 schrieb Laszlo Ersek:
>> I guess it is "possible to design a system which can recover from
>> this", except noone seems to have bothered, since 2009. (Ditto for the
>> proposed "panic-l
Am 07.11.2016 um 15:12 schrieb Laszlo Ersek:
The second error message is incorrect in its own right (it's just
another symptom of running out of memory;
there a two cpios
big(~370MB) initrd.cpio + 1GB ram gives only this message: "Initramfs
unpacking failed: write error"
small(~14MB) initrd.cp
On 11/07/16 15:15, Laszlo Ersek wrote:
> On 11/07/16 08:35, Dennis Luehring wrote:
>> Am 04.11.2016 um 20:40 schrieb Laszlo Ersek:
>>> I guess it is "possible to design a system which can recover from
>>> this", except noone seems to have bothered, since 2009. (Ditto for the
>>> proposed "panic-lev
On 11/07/16 08:35, Dennis Luehring wrote:
> Am 04.11.2016 um 20:40 schrieb Laszlo Ersek:
>> I guess it is "possible to design a system which can recover from
>> this", except noone seems to have bothered, since 2009. (Ditto for the
>> proposed "panic-level=X" alternative.)
>>
>> I've now briefly co
On 11/07/16 08:37, Dennis Luehring wrote:
> Am 04.11.2016 um 22:08 schrieb Richard Henderson:
>> No, it was less specific than that. Something like "unpacking failed:
>> error".
>>
>>> >And, apparently, it used to be handled with a panic() call, but then
>>> that
>>> >was deemed "policy", and down
Am 04.11.2016 um 22:08 schrieb Richard Henderson:
No, it was less specific than that. Something like "unpacking failed: error".
>And, apparently, it used to be handled with a panic() call, but then that
>was deemed "policy", and downgraded to a KERN_EMERG message:
Ouch. A silly decision, but
Am 04.11.2016 um 20:40 schrieb Laszlo Ersek:
I guess it is "possible to design a system which can recover from this", except noone
seems to have bothered, since 2009. (Ditto for the proposed "panic-level=X" alternative.)
I've now briefly considered posting a trivial kernel patch for this, but h
On 11/04/2016 01:40 PM, Laszlo Ersek wrote:
For the 4.7 kernel, we had enough ram to unpack the (large) initrd; with
the 4.8 kernel, we ran out. The 4.8 kernel did in fact print an
(obscure) error message to that effect, which had not been noticed.
Was it
Unpacking initramfs...
Initramfs
On 11/04/16 17:37, Richard Henderson wrote:
> On 11/04/2016 05:08 AM, Stefan Hajnoczi wrote:
>> On Thu, Oct 20, 2016 at 12:45:37PM +0200, Dennis Luehring wrote:
>>> qemu: 2.7.x (git head)
>>> platform: Alpha (Clipper)
>>
>> Two options:
>>
>> 1. Not many people use Alpha. You may need to debug thi
On 11/04/2016 05:08 AM, Stefan Hajnoczi wrote:
On Thu, Oct 20, 2016 at 12:45:37PM +0200, Dennis Luehring wrote:
qemu: 2.7.x (git head)
platform: Alpha (Clipper)
Two options:
1. Not many people use Alpha. You may need to debug this yourself by
learning about the Linux alpha boot protocol (
On Thu, Oct 20, 2016 at 12:45:37PM +0200, Dennis Luehring wrote:
> qemu: 2.7.x (git head)
> platform: Alpha (Clipper)
Two options:
1. Not many people use Alpha. You may need to debug this yourself by
learning about the Linux alpha boot protocol (where the initramfs is
loaded and how big th
qemu: 2.7.x (git head)
platform: Alpha (Clipper)
kernel: 4.7.0
gcc: 6.1
i don't know if its an qemu oder linux kernel problem
i've got an ~360MB big_initrd.cpio and it sometimes happen(seems so) that
there are files missing after the kernel loaded the initrd
this does not happen with the same pr
17 matches
Mail list logo
