#10991 NORM 1.75-fi: XO-1.75 A3 boot panic, no filesystem could mount root, tried: ext3 ext2 ext4 cramfs vfat msdos (was: XO-1.75 A3 #44 - Fails to boot - USB port erroneously reported in use)

[Zarro Boogs per Child]

#10991: XO-1.75 A3 boot panic, no filesystem could mount root, tried: ext3 ext2
ext4 cramfs vfat msdos
---------------------------------------+------------------------------------
           Reporter:  martin.langhoff  |       Owner:  Quozl        
               Type:  defect           |      Status:  assigned     
           Priority:  normal           |   Milestone:  1.75-firmware
          Component:  hardware         |     Version:  1.75-A3      
         Resolution:                   |    Keywords:               
        Next_action:  never set        |    Verified:  0            
Deployment_affected:                   |   Blockedby:               
           Blocking:                   |  
---------------------------------------+------------------------------------

Old description:

> OFW: Q4A13K
> OS: os9.
>
> Under OFW, test-all reports that "USB 2.0 port 0 is in use". There is
> nothing plugged into any port. (Not sure how the port enumeration works.)
>
> Under Linux, system fails to boot with log attached -- which also
> complains loudly about USB.
>
> Wad reports that this unit installed fw/sw and booted at 1CC. The USB
> port may have gotten damaged through use -- OFW, EC and OS were updated
> via USB.

New description:

 Problem Description: XO-1.75 A3 boards at Quanta, fail to boot, showing a
 kernel panic, message ''no filesystem could mount root, tried: ext3 ext2
 ext4 cramfs vfat msdos'', regardless of repeated {{{fs-update}}}, only
 with os9 and os10, but not os4, with eMMC or external SD.

 Original problem description below.

 --

 OFW: Q4A13K
 OS: os9.

 Under OFW, test-all reports that "USB 2.0 port 0 is in use". There is
 nothing plugged into any port. (Not sure how the port enumeration works.)

 Under Linux, system fails to boot with log attached -- which also
 complains loudly about USB.

 Wad reports that this unit installed fw/sw and booted at 1CC. The USB port
 may have gotten damaged through use -- OFW, EC and OS were updated via
 USB.

--

Comment(by Quozl):

 Chia-Hsiu reports that mixing the os4 kernel with the os10 or os9
 filesystem results in a successful boot.  From this we can conclude that
 the os9 or os10 kernel, in conjunction with the affected laptops, is a
 cause of the problem.

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