#11257 HIGH 1.75-so: corruption in late stages of XO-1.75 build process

[Zarro Boogs per Child]

#11257: corruption in late stages of XO-1.75 build process
------------------------------------+---------------------------------------
           Reporter:  Quozl         |       Owner:  dsd                              
               Type:  defect        |      Status:  new                              
           Priority:  high          |   Milestone:  1.75-software                    
          Component:  build-system  |     Version:  Development build as of this date
         Resolution:                |    Keywords:                                   
        Next_action:  diagnose      |    Verified:  0                                
Deployment_affected:                |   Blockedby:                                   
           Blocking:                |  
------------------------------------+---------------------------------------

Old description:

> {{{
> # olpc-contents-verify \
> /versions/pristine/5/etc/passwd \
> /versions/pristine/5/etc/group \
> 85d9a6a379a1cc73a2519bdfd960534745c6c02f3e235b8cbcc5186a54f6d8cc \
> /versions/contents/5 \
> /versions/pristine/5
> Contents manifest failure at line 204
> Last file examined: 20-unhint-small-dejavu-lgc-sans-mono.conf
> #
> }}}
>
> There are two such names on the filesystem, a symlink at
> /etc/fonts/conf.d and a file at /usr/share/contconfig/conf.avail, with
> the symlink pointing to the file.
>
> Both are owned by dejavu-lgc-sans-mono-fonts-2.32-1.fc14.noarch yet this
> has not changed.
>
> The file has the same md5sum as the corresponding file on os36.
>
> Therefore this seems to be a failure of olpc-contents, bitfrost verify or
> hashing functions.
>
> The failure is reproduced before or after starting the X server.
>
> (I was not able to find an olpc-contents git repository that matches the
> files provided by the olpc-contents package.)
>
> Impact: prevents manufacturing runin fscheck test.

New description:

 {{{
 # olpc-contents-verify \
 /versions/pristine/5/etc/passwd \
 /versions/pristine/5/etc/group \
 85d9a6a379a1cc73a2519bdfd960534745c6c02f3e235b8cbcc5186a54f6d8cc \
 /versions/contents/5 \
 /versions/pristine/5
 Contents manifest failure at line 204
 Last file examined: 20-unhint-small-dejavu-lgc-sans-mono.conf
 #
 }}}

 There are two such names on the filesystem, a symlink at /etc/fonts/conf.d
 and a file at /usr/share/contconfig/conf.avail, with the symlink pointing
 to the file.

 Both are owned by dejavu-lgc-sans-mono-fonts-2.32-1.fc14.noarch yet this
 has not changed.

 The file has the same md5sum as the corresponding file on os36.

 Therefore this seems to be a failure of olpc-contents, bitfrost verify or
 hashing functions.

 The failure is reproduced before or after starting the X server.

 (I was not able to find an olpc-contents git repository that matches the
 files provided by the olpc-contents package.)

 Impact: prevents manufacturing runin fscheck test.

--

Comment(by Quozl):

 Eye opener ... after installing os6, X would not start, found a Python
 process consuming 95% of CPU, an strace showed access syscalls wandering
 through a symlink recursive loop on /etc/fonts/conf.d.  After removing the
 broken symlinks, X did start.  Reproduced on a second B1.

-- 
Ticket URL: <http://dev.laptop.org/ticket/11257#comment:2>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system