| Re: Tazlito with Kernel from latest cooking |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/slitaz Archives
]
- To: slitaz@xxxxxxxxxxxxxxxxxxx
- Subject: Re: Tazlito with Kernel from latest cooking
- From: Allan Pinto <allan316@xxxxxxxxx>
- Date: Sat, 24 Oct 2009 04:05:53 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=5lavRu0pEH9WO9aFMuwXTqAlvdlcog5cTvk04nXsXLw=; b=weJNkPqElif/8LeOEYUdCYELc3Tzj9RtfuE798kdylTEArH7Qgdq4OaEoZNnkZvCAt PKbjNw0Lpk8N4T5I23ffB0/hfVZgodCzKsViSaLoxzdBv2EPUPQULa0TB6II/9TXlLTn PDJbajvu6umnQQza/H3RXqHLWxcH40rL8ANQQ=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=lTol8TXtpWnCcAl1w6JkGrfKc9GrmOWGSgtwehIfqr9kJZYtxhAIn1/n+VmsQRqRM1 vWVNHuDMZ4vMhNTeK7v9jRN31werefbdeHPY5/UkT1Iana0jxt6nbq3/T7z+9eeqrawR fC1dXndx8J22+FtuU8MoFijg6X10DQXSZusY4=
i think its best that i try to reproduce the error too, wll revert soon.
On Fri, Oct 23, 2009 at 3:32 PM, Harald Klimach <klimach@xxxxxxx> wrote:
> Hi,
>
>> what is the error it gives you when it fails?
> the kernel aborts with some messages about threads and helpers,
> I fear I'm not really confident with that kernel stuff, here
> are the last lines, that are shown on the screen:
>
> [<c016080c>] ? alloc_vmap_area+0x168/0x197
> [<c0114df4>] bad_area_nosemaphore+0xd/0x10
> [<c011500a>] do_page_fault+0xe1/0x1de
> [<c0114f29>] ? do_page_fault+0x0/0x1de
> [<c0423b4d>] error_code+0x6d/0x74
> [<c05v9342>] ? unlzma+x0xcfa/0xe8e
> [<c0101546>] ? fill_buffer+0x0/0xa9
> [<c05a2cf2>] unpack_to_rootfs+0x1ee/0x303
> [<c05a2830>] ? cpio_flush_buffer+0x0/0x8a
> [<c05a2659>] ? error+0x0/0x13
> [<c05a2e07>] ? populate_rootfs+0x0/0x229
> [<c05a2e5e>] populate_rootfs+0x57/0x229
> [<c05c8067>] ? af_unix_init+0x0/0x47
> [<c019a4a2>] ? proc_net_fops_create+0x1a/0x1f
> [<c03e9645>] ? unix_net_init+0x31/0x4b
> [<c039c6fa>] ? register_pernet_operations+0x13/0x15
> [<c039c7d3>] ? register_pernet_subsys+0x28/0x2d
> [<c0101139>] do_one_initcall+0x4c/0x13a
> [<c05a12db>] kernel_init+0x106/0x157
> [<c05a11d5>] ? kernel_init+0x0/0x157
> [<c01038e7>] kernel_thread_helper+0x7/0x10
>
>
> In the meantime I found something else: on an old box with
> only a single core there doesn't seem to be that issue!
> However I can reproduce the error on at least two different
> dual-core systems.
>
> So maybe it is related to the multicores and threads interfering
> with each other?
>
> In any case this seems to be very strange.
>
> Thanks a lot for your reply!
> Harald
>
>
>> On Fri, Oct 23, 2009 at 12:27 PM, Harald Klimach <klimach@xxxxxxx> wrote:
>> > Hi again,
>> >
>> >> A pure core flavor seems also to work with the newest kernel. Maybe there is
>> >> a limit to the ramfs size or something in the new one? I am trying to track
>> >> this down right now.
>> > I can't really put a finger on this. It indeed seems to be related to the
>> > size. For example something like this already fails:
>> >
>> > tazlito get-flavor core
>> > echo vim-7.2 >> distro-packages.list
>> > tazlito clean-distro
>> > tazlito gen-distro
>> > tazlito gen-flavor core
>> >
>> > This is not fixed to vim, but also happens with other packages of sufficient
>> > size. Anybody experiencing something like that with cooking?
>
> ---
> SliTaz GNU/Linux Mailing list - http://www.slitaz.org/
>
>
--
Thanx and regd's.
Allan.
http://www.in2dwok.com
---
SliTaz GNU/Linux Mailing list - http://www.slitaz.org/