[Bug 567] New: I/O errors on flash and frozen fs

bugzilla-daemon at bugzilla.openmoko.org bugzilla-daemon at bugzilla.openmoko.org
Fri May 18 22:50:42 CEST 2007


http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=567

           Summary: I/O errors on flash and frozen fs
           Product: OpenMoko
           Version: unspecified
          Platform: Neo1973
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: kernel
        AssignedTo: laforge at openmoko.org
        ReportedBy: elrond+bugzilla.openmoko.org at samba-tng.org
                CC: buglog at lists.openmoko.org


Hardware: GTA01Bv03 (phase 0)
Kernel: Linux version 2.6.20.2-moko8 (stefan at fairlight) (gcc version 4.1.1) #56
PREEMPT Sun Apr 8 13:58:03 CEST 2007
u-boot: I think 1.2.0-moko7 (getting to the u-boot prompt isn't stricly easy)

The whole thing started, when I downloaded openmoko-theme-standard.ipk to tmpfs
and tried to install it using ipkg install *.ipk. I got a few Input/Output
errors on files and the ipkg command hung.

Logging in via ssh still worked. And all commands, which were still in RAM,
worked fine. But any access to jffs2 locked up that command.
I could grab dmesg output, which contains a kernel-oops. (will be attached to
this bug as write-oops.dmesg)

As /sbin/halt.sysvinit (for "halt -p -d -i -p") was not in RAM (and I copied a
fresh one via scp to tmpfs) and some other needed stuff was not available, I had
to hard power off the machine (remove battery, half minute pressing power-button
did not work).

The next day, the machine seemed to boot fine. Until the fs gave me again I/O
errors (this time I did not try to write to it explicitly). This time I have a
bigger dmesg, which goes back to the boot. (will be attached to this bug as
boot_and_jffs2notices.dmesg).
Again I had to remove the battery, as I still haven't found the node in /sys,
that will shut down the phone IMMEDIATELY when echoing something into it.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




More information about the buglog mailing list