#10041 NORM Opportu: init segfaults when booting from USB
Zarro Boogs per Child
bugtracker at laptop.org
Thu Jun 10 01:37:44 EDT 2010
#10041: init segfaults when booting from USB
------------------------------------+---------------------------------------
Reporter: pgf | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Opportunity
Component: not assigned | Version: not specified
Resolution: | Keywords:
Next_action: never set | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
------------------------------------+---------------------------------------
Changes (by Quozl):
* milestone: Not Triaged => Opportunity
Old description:
> installed os110 to a 4G USB stick, using:
>
> {{{
> tar --to-stdout -xzvf os110.disk.img.tar.gz >/dev/sdc
> }}}
>
> the contents of the stick seem reasonable:
> {{{
> # fdisk -l /dev/sdc
> Disk /dev/sdc: 4001 MB, 4001366016 bytes
> 32 heads, 32 sectors/track, 7632 cylinders
> Units = cylinders of 1024 * 512 = 524288 bytes
> Disk identifier: 0x00000000
>
> Device Boot Start End Blocks Id System
> /dev/sdc1 * 9 136 65536 83 Linux
> /dev/sdc2 137 7561 3801600 83 Linux
>
> }}}
>
> the filesystem contents look reasonable as well.
>
> booting from this stick yields a panic, due to init segfaulting:
> {{{
> init[1]: segfault at 48bf34bd ip 003f932a sp aff376cc error 4 in
> ld-2.10.2.so[3ee000+1f000]
> }}}
>
> this was repeated after two attempts, first with the 4G image, and then
> with the 2G image (in case the image was too big). the same stick was
> used in both cases. i'll try another stick.
New description:
installed os110 to a 4G USB stick, using:
{{{
tar --to-stdout -xzvf os110.disk.img.tar.gz >/dev/sdc
}}}
the contents of the stick seem reasonable:
{{{
# fdisk -l /dev/sdc
Disk /dev/sdc: 4001 MB, 4001366016 bytes
32 heads, 32 sectors/track, 7632 cylinders
Units = cylinders of 1024 * 512 = 524288 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdc1 * 9 136 65536 83 Linux
/dev/sdc2 137 7561 3801600 83 Linux
}}}
the filesystem contents look reasonable as well.
booting from this stick yields a panic, due to init segfaulting:
{{{
init[1]: segfault at 48bf34bd ip 003f932a sp aff376cc error 4 in
ld-2.10.2.so[3ee000+1f000]
}}}
this was repeated after two attempts, first with the 4G image, and then
with the 2G image (in case the image was too big). the same stick was
used in both cases. i'll try another stick.
--
--
Ticket URL: <http://dev.laptop.org/ticket/10041#comment:2>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list