Damn Reboot using the shell - Page 3

wlaf · 06-17-2012, 05:18 AM

This is the output:

Code:

Rebooting in 1 second...

Restarting system.
EXT3-fs error (device mmcblk0p1): ext3_find_entry: reading directory #3213 offset 1
EXT3-fs error (device mmcblk0p1): ext3_find_entry: reading directory #3213 offset 0
Unhandled fault: external abort on non-linefetch (0x008) at 0x00020048


U-Boot 1.3.0-rc3-lab126 (Apr  6 2011 - 17:12:22)

CPU:   Freescale i.MX35 at 532 MHz
Board: MX35 Luigi [ POR]
WDOG_WCR = 0xff31
WDOG_WMCR = 0x0
Board Id: SP1B000000000000
S/N: ***
DRAM:  256 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
No ethernet found.
i.MX35 CPU board version 2.0
Net:   No ethernet found.
Hit any key to stop autoboot:  0
## Booting image at 87f40400 ...
   Image Name:   Linux-2.6.26-rt-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2168732 Bytes =  2.1 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux.......................................................................................................................... done, booting the kernel.
boot: I def:rbt:reset=user_reboot:
2.6.26-rt-lab126 #5 Wed Apr 6 17:13:11 PDT 2011 armv6l
INFO:Using default keypad setting. (not passing "kb_rev" to module)
INFO:Loaded module /lib/modules/mxc_keyb.ko  (22508 bytes)
Press [ENTER] for recovery menu...       0 /INFO:Partition table verified for /dev/mmcblk0
INFO:Checking for updates... (auto-pilot mode)
/dev/mmcblk0p4:
CHS=4/16/100167 size=3282272256 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    6410672
    CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4:
INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 8192
INFO:No update*.bin found; no update needed.
INFO:no updates found.
BOOTING DEFAULT.
  argc == 9
  argv[0]: "kinit"
  argv[1]: "console=ttymxc0,115200"
  argv[2]: "mem=256M"
  argv[3]: "panic=10"
  argv[4]: "root=/dev/mmcblk0p1"
  argv[5]: "ro"
  argv[6]: "ip=none"
  argv[7]: "quiet"
  argv[8]: "lpj=2555904"
Running ipconfig
  argc == 4
  argv[0]: "IP-Config"
  argv[1]: "-i"
  argv[2]: "Linux kinit"
  argv[3]: "ip=none"
IP-Config: no devices to configure
kinit: do_mounts
kinit: name_to_dev_t(/dev/mmcblk0p1) = dev(179,1)
kinit: root_dev = dev(179,1)
kinit: /dev/root appears to be a ext3 filesystem
kinit: trying to mount /dev/root on /root with type ext3
kinit: Mounted root (ext3 filesystem) readonly.
Checking for init: /sbin/init
Checking for init: /bin/init
Checking for init: /etc/init
Checking for init: /sbin/init.sysvinit
INIT: version 2.86 booting
system: I rcS:def:starting /etc/rcS.d/S02kdb
system: I S02kdb:def:Setting boot device to mmcblk0
kdb set: 'system/driver/filesystem/DEV_ROOT'
system: I rcS:def:starting /etc/rcS.d/S03udev
system: I S03udev:def:setting up virtual fs for hotplug event handling
system: I S03udev:def:starting the hotplug events dispatcher
system: I S03udev:def:synthesizing initial hotplug events
lipc-send-event[380]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
lipc-send-event[380]: C def:dbusi::Failed to init dbus
lipc-send-event[380]: E def:open::Failed to open LIPC
lipc-send-event[380]: E def:fail:source=com.lab126.hal, event=usbPlugIn:Sending event failed
lipc-send-event[476]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
lipc-send-event[476]: C def:dbusi::Failed to init dbus
lipc-send-event[476]: E def:open::Failed to open LIPC
lipc-send-event[476]: E def:fail:source=com.lab126.hal, event=audioHS:Sending event failed
system: I rcS:def:starting /etc/rcS.d/S04rootfsresize
system: I S04rootfsresize:def:No rootfs on /dev/mmcblk0p1 resizing needed
system: I rcS:def:starting /etc/rcS.d/S10filesystems
system: I rcS:def:starting /etc/rcS.d/S10hostname
system: I rcS:def:starting /etc/rcS.d/S10network
system: I S10filesystems:def:mounting filesystems
system: I S10hostname:def:setting device hostname
system: I S10network:def:initializing network configuration
system: I S10network:def:Installed Firewall
system: I rcS:def:starting /etc/rcS.d/S11chpriority
system: I rcS:def:starting /etc/rcS.d/S11video
Unknown HZ value! (90) Assume 100.
system: W S11chpriority:def:Cannot set priority for IRQ-7
system: I S11video:def:initializing eInk HAL for system use
system: I S11video:def:eink_debug=0
system: I S11video:def:Controller set to broads
system: I rcS:def:starting /etc/rcS.d/S20syslog-ng
system: I S20syslog-ng:def:starting syslog-ng
system: I rcS:def:starting /etc/rcS.d/S21init_time
system: I S21init_time:initboot:time=16070:boot time after init in milliseconds
system: I rcS:def:starting /etc/rcS.d/S45modules
system: I S45modules:def:loading module mwan
system: I S45modules:def:loading module g_file_storage
system: I S45modules:def:loading module fuse
system: I S45modules:def:loading module uinput
system: I S45modules:def:loading module mxc_keyb
system: I S45modules:def:loading module fiveway
system: I S45modules:def:loading module volume
system: I rcS:def:starting /etc/rcS.d/S50system
mount: mount point /proc/bus/usb does not exist
system: I rcS:def:starting /etc/rcS.d/S55scroll
system: I S55scroll:def:skipping; no luigi-based work to do here
system: I rcS:def:starting /etc/rcS.d/S70ethernet
system: I rcS:def:starting /etc/rcS.d/S70userstore
system: I S70ethernet:def:not enet
system: I S70ethernet:def:not usbnet
system: I S70userstore:def:Found SHUTDOWN flag file
system: I rcS:def:starting /etc/rcS.d/S90video
system: I S90video:def:initializing eInk HAL for rootfs use
INIT: Entering runlevel: 2
system: I lifeguard:def:starting eInk HAL lifeguard
system: I S40diags:def:not starting Diagnostic Services
system: I S40diags:def:/mnt/base-us/ENABLE_DIAGS does not exist, forcing diagnostic disable
system: I S50battcheck:def:running
Sat Jul 31 00:27:23 2010  INFO:battery voltage: 4036 mV
Sat Jul 31 00:27:23 2010  INFO:battery charge: 94%
system: I S50battcheck:def:current voltage = 4044mV
Sat Jul 31 00:27:23 2010  INFO:battery charge: 94%
Sat Jul 31 00:27:23 2010  INFO:battery voltage: 4036 mV
Sat Jul 31 00:27:23 2010  INFO:battery current: -246 mA
system: I S50battcheck:def:gasgauge capacity=94% volts=4036 mV current=-246 mA
system: I S50battcheck:def:Waiting for 3460mV or 4%
system: I S50battcheck:def:battery sufficient, booting to normal runlevel
INIT: Switching to runlevel: 5
INIT: Sending processes the TERM signal
system: I wifi:def:WiFi Device mac = 28:EF:01:4F:27:8B
Platform set to SHASTA_NATIVEMMC-SDIO
Platform Setup Script is: /opt/ar6k/host/support/platformscripts/plat_SHASTA_NATIVEMMC-SDIO.sh
Image path: /sbin
No debug record limit set
Load Board Data from /opt/ar6k/target/AR6002/hw2.0/bin/lab126_15dBm_nodiv_WWR_CTL.bin
Updating MAC address
BMI Set App Start (address: 0x913950)
BMI Bit-Wise (OR) modify Register (address: 0x500410, orig:0x8, new: 0x9,  mask:0x1)
BMI Write compressed Memory (address: 0x502070, filename: /opt/ar6k/target/AR6002/hw2.0/bin/athwlan.bin.z77)
BMI Write Memory (address: 0x52d6d0, filename: /opt/ar6k/target/AR6002/hw2.0/bin/data.patch.hw2_0.bin)
BMI Write Memory (address: 0x500418, value: 0x52d6d0)
BMI Done
system: I wifi:def:loadAR6000=finished, args=():
system: I wpa_supplicant:def:wpa supplicant started
system: I S30network:def:initializing network configuration
system: I S30network:def:Installed Firewall
system: I S60dbus:def:starting system message bus
Failed to start message bus: Could not get UID and GID for username "messagebus"
Starting Process Monitoring Daemon: Retrieved 127 keys for system/daemon/pmond/
Starting Power Management Daemon: com.lab126.pmond failed to open lipc for start event
system: I S70cmd:def:starting CMD daemon
com.lab126.pmond failed to open lipc for start event
system: I S70wifid:def:starting wifid
com.lab126.pmond failed to open lipc for start event
system: I S75phd:def:Starting Phone-Home Daemon
com.lab126.pmond failed to open lipc for start event
system: I S76mcsd:def:starting MCS server
com.lab126.pmond failed to open lipc for start event
system: I S80volumd:def:starting Volume daemon
com.lab126.pmond failed to open lipc for start event
system: I S82usbnet:def:usbnet is disabled
system: I S85audio:def:initializing audio driver defaults
No state is present for card mx35luigi
system: I S85audio:def:starting audio server
com.lab126.pmond failed to open lipc for start event
system: I S87ttsd:def:starting TTS daemon
com.lab126.pmond failed to open lipc for start event
system: I S90cron:def:starting crond
Battery Level: 94%
Sat Jul 31 00:27:34 2010  INFO:battery charge: 94%
Starting lipc-daemon: system: I S90tmd:def:Starting Transfer Manager Daemon
com.lab126.pmond failed to open lipc for start event
system: I S94browserd:def:Starting Browser Daemon
com.lab126.pmond failed to open lipc for start event
system: I S95framework:def:starting booklet framework
INIT: Sending processes the TERM signal
system: I K04framework:def:stopping booklet framework
com.lab126.powerd failed to open lipc for state event
system: I K06browserd:def:Stopping Browser Daemon
com.lab126.pmond failed to open lipc for stop event
killall: browserd: no process killed
system: I K09usbnet:def:couldn't stop usbnet
system: I K10cron:def:stopping crond
start-stop-daemon: lseek: Invalid argument
Stopping lipc-daemon: system: I K10tmd:def:Stopping Transfer Manager Daemon
com.lab126.pmond failed to open lipc for stop event
system: I K15audio:def:stopping audio server
com.lab126.pmond failed to open lipc for stop event
system: I K17ttsd:def:stopping TTS daemon
com.lab126.pmond failed to open lipc for stop event
Failed to open LIPC
com.lab126.hal failed to send event usbUnconfigured
com.lab126.volumd failed to open lipc for driveModeState event
sh: 0: unknown operand
system: I K19userstore:def:Found BOOTUP flag file
system: I K25phd:def:Stopping Phone-Home Daemon
com.lab126.pmond failed to open lipc for stop event
Stopping Power Management Daemon: com.lab126.pmond failed to open lipc for stop event
stopped /usr/bin/wpa_supplicant (pid 2019)
system: W wpa_supplicant:def:wpa supplicant stopped
system: I wifi:def:WiFi Device mac = 28:EF:01:4F:27:8B
Platform set to SHASTA_NATIVEMMC-SDIO
Platform Setup Script is: /opt/ar6k/host/support/platformscripts/plat_SHASTA_NATIVEMMC-SDIO.sh
Image path: /sbin
..unloading all
killall: recEvent: no process killed
system: I wifi:def:loadAR6000=finished, args=(unloadall):
Stopping Process Monitoring Daemon: system: I K85dbus:def:stopping system message bus
system: I K90video:def:stopping eInk HAL lifeguard
system: I K99syslog-ng:def:stopping syslog-ng
system: I tinyrot:def::Rotating file /var/log/messages with max size 256
cat: can't open '/var/local/log/nexttosendfile': No such file or directory
/usr/sbin/tinyrot : Signaling syslog
killall: syslog-ng: no process killed
system: W tinyrot:def:Failed to HUP syslog
killall: syslog-ng: no process killed
pmond[2299]: C def:ipc::Failed to init IPC

/usr/sbin/tinyrot : Calculating total size /var/local/log/messages_*.gz
/usr/sbin/tinyrot : Total size of /var/local/log/messages_*.gz is 165kb
system: I tinyrot:def::Rotating file /var/log/odotlite with max size 4048
system: I tinyrot:def::No file to rotate: /var/log/odotlite

Halting in 1 second...

Power down.
EXT3-fs error (device mmcblk0p1): ext3_find_entry: reading directory #3213 offset 0
EXT3-fs error (device mmcblk0p1): ext3_find_entry: reading directory #3213 offset 1

wlaf · 06-17-2012, 05:30 AM

And I could be able to get to the Recovery menu: (I just pressed I)

Code:

Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose:   8 \

INFO:Loading original MBR from MMC0 (/dev/mmcblk0) ...
INFO:partition 2, start sector is 1338944
INFO:partition 3, start sector is 1388096
INFO:partition 4, start sector is 1404480
INFO:maximizing partition 6410688 sectors
/dev/mmcblk0:
CHS=4/16/122112 size=4001366016 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x80 0x83      24072 <large>          7688    1331256
    CHS: 376/0/9 - <large>
Partition p2:
0x00 0x83 <large>    <large>       1338944      49152
    CHS: <large>
 - <large>
Partition p3:
0x00 0x83 <large>    <large>       1388096      16384
    CHS: <large>
 - <large>
Partition p4:
0x00 0x0b <large>    <large>       1404480    6410688
    CHS: <large>
 - <large>
INFO:Writing out partition table to MMC0 (/dev/mmcblk0)
INFO:Wrote MBR to /dev/mmcblk0
INFO:Nuked first cylinder(32768 bytes) of filesystem in partition 1(+3936256) on /dev/mmcblk0
INFO:Nuked first cylinder(32768 bytes) of filesystem in partition 2(+685539328) on /dev/mmcblk0
INFO:Nuked first cylinder(32768 bytes) of filesystem in partition 4(+719093760) on /dev/mmcblk0
Rereading partition information ...
INFO:Formatting userstore
INFO:Loading original MBR from /dev/mmcblk0p4 ...
INFO:maximizing partition 6403000 sectors
/dev/mmcblk0p4:
CHS=4/16/100167 size=3282272256 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b      24072 <large>          7688    6403000
    CHS: 376/0/9 - <large>
Partition p2:
Partition p3:
Partition p4:
INFO:Writing out partition table to /dev/mmcblk0p4
INFO:Wrote MBR to /dev/mmcblk0p4
/dev/mmcblk0p4:
CHS=4/16/100167 size=3282272256 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b      24072 <large>          7688    6403000
    CHS: 376/0/9 - <large>
Partition p2:
Partition p3:
Partition p4:
INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 3936256
INFO:executing: /bin/mkdosfs -F 32 -s 16 -n Kindle -v /dev/loop0
mkdosfs 2.11-lab126-klibc (28 Apr 2008)
Loop device does not match a floppy size, using default hd params
/dev/loop0 has 64 heads and 32 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 6403000 sectors;
file system has 2 32-bit FATs and 16 sectors per cluster.
FAT size is 3124 sectors, and provides 399795 clusters.
Volume ID is 4c5370cb, volume label Kindle     .

Syncing ...
Charge: 94% [########################################################::]

What shoud I do?

wlaf · 06-17-2012, 05:37 AM

And at last, kernel panic. :-((

Code:

U-Boot 1.3.0-rc3-lab126 (Apr  6 2011 - 17:12:22)

CPU:   Freescale i.MX35 at 532 MHz
Board: MX35 Luigi [ POR]
WDOG_WCR = 0xff31
WDOG_WMCR = 0x0
Board Id: SP1B000000000000
S/N: ***
DRAM:  256 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
No ethernet found.
i.MX35 CPU board version 2.0
Net:   No ethernet found.
Hit any key to stop autoboot:  0
## Booting image at 87f40400 ...
   Image Name:   Linux-2.6.26-rt-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2168732 Bytes =  2.1 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux.......................................................................................................................... done, booting the kernel.
boot: I def:rbt:reset=user_reboot:
2.6.26-rt-lab126 #5 Wed Apr 6 17:13:11 PDT 2011 armv6l
INFO:Using default keypad setting. (not passing "kb_rev" to module)
INFO:Loaded module /lib/modules/mxc_keyb.ko  (22508 bytes)
Press [ENTER] for recovery menu...       0 /INFO:Partition table verified for /dev/mmcblk0
INFO:Loaded module /lib/modules/eink_fb_hal.ko  (73284 bytes)
INFO:Loaded module /lib/modules/eink_fb_hal_broads.ko bs_orientation=0 bs_bpp=4 (124904 bytes)
INFO:Loaded module /lib/modules/eink_fb_shim.ko  (128984 bytes)
INFO:eink initialized... (483328 bytes)
INFO:Loaded module /lib/modules/arcotg_udc.ko  (56288 bytes)
INFO:Loaded module /lib/modules/g_file_storage.ko  (40764 bytes)
Charge: 97% [#########################################################:]


Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose:   1 -
Menu timeout
BOOTING DEFAULT.
  argc == 9
  argv[0]: "kinit"
  argv[1]: "console=ttymxc0,115200"
  argv[2]: "mem=256M"
  argv[3]: "panic=10"
  argv[4]: "root=/dev/mmcblk0p1"
  argv[5]: "ro"
  argv[6]: "ip=none"
  argv[7]: "quiet"


U-Boot 1.3.0-rc3-lab126 (Apr  6 2011 - 17:12:22)

CPU:   Freescale i.MX35 at 532 MHz
Board: MX35 Luigi [ POR]
WDOG_WCR = 0xff31
WDOG_WMCR = 0x0
Board Id: SP1B000000000000
S/N: ***
DRAM:  256 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
No ethernet found.
i.MX35 CPU board version 2.0
Net:   No ethernet found.
Hit any key to stop autoboot:  0
## Booting image at 87f40400 ...
   Image Name:   Linux-2.6.26-rt-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2168732 Bytes =  2.1 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux.......................................................................................................................... done, booting the kernel.
boot: C def:bcut:batterycut=1:
last sysfs file:$/sys/dهvéces/virüual/net/ىo/flaçs<4>Modules lioked*in: [ىcst unloaded: هink_nb_hal]
2.6.26-rt-lab126 #5 Wed Apr 6 17:13:11 PDT 2011 armv6l
INFO:Using default keypad setting. (not passing "kb_rev" to module)
INFO:Loaded module /lib/modules/mxc_keyb.ko  (22508 bytes)
Press [ENTER] for recovery menu...       0 /INFO:Partition table verified for /dev/mmcblk0
INFO:Checking for updates... (auto-pilot mode)
/dev/mmcblk0p4:
CHS=4/16/100167 size=3282272256 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b      24072 <large>          7688    6403000
    CHS: 376/0/9 - <large>
Partition p2:
Partition p3:
Partition p4:
INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 3936256
INFO:No update*.bin found; no update needed.
INFO:no updates found.
BOOTING DEFAULT.
  argc == 9
  argv[0]: "kinit"
  argv[1]: "console=ttymxc0,115200"
  argv[2]: "mem=256M"
  argv[3]: "panic=10"
  argv[4]: "root=/dev/mmcblk0p1"
  argv[5]: "ro"
  argv[6]: "ip=none"
  argv[7]: "quiet"
  argv[8]: "lpj=2555904"
Running ipconfig
  argc == 4
  argv[0]: "IP-Config"
  argv[1]: "-i"
  argv[2]: "Linux kinit"
  argv[3]: "ip=none"
IP-Config: no devices to configure
kinit: do_mounts
kinit: name_to_dev_t(/dev/mmcblk0p1) = dev(179,1)
kinit: root_dev = dev(179,1)
kinit: failed to identify filesystem /dev/root, trying all
kinit: trying to mount /dev/root on /root with type ext3
kinit: trying to mount /dev/root on /root with type ext2
kinit: trying to mount /dev/root on /root with type cramfs
kinit: trying to mount /dev/root on /root with type msdos
kinit: trying to mount /dev/root on /root with type vfat
kinit: Unable to mount root fs on device dev(179,1)
Checking for init: /sbin/init
Checking for init: /bin/init
Checking for init: /etc/init
Checking for init: /sbin/init.sysvinit
Checking for init: /bin/sh
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = cfab0000
[00000000] *pgd=8fa63031, *pte=00000000, *ppte=00000000
Internal error: Oops: 817 [#1]
last sysfs file: /sys/devices/virtual/net/lo/flags
Modules linked in: [last unloaded: mxc_keyb]
CPU: 0    Not tainted  (2.6.26-rt-lab126 #5)
PC is at panic+0x6c/0x12c
LR is at 0x0
pc : [<c00ce8d0>]    lr : [<00000000>]    psr: 60000013
sp : cf81ff58  ip : 00000000  fp : cf81ff6c
r10: 00000001  r9 : cf81e000  r8 : c00a3c28
r7 : 00000001  r6 : 00000200  r5 : cf814c40  r4 : 00000000
r3 : 00000000  r2 : c03bef3c  r1 : 00000000  r0 : 00000000
Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 00c5387d  Table: 8fab0008  DAC: 00000015
Process kinit (pid: 1, stack limit = 0xcf81e260)
Stack: (0xcf81ff58 to 0xcf820000)
ff40:                                                       cf8ecb60 cf81ff74
ff60: cf81ff94 cf81ff80 c00d1a80 c00ce874 c0358cc0 cf814c40 c03a40b4 c03a40b4
ff80: cf81e000 00000000 cf81ffa4 cf81ff98 c00d2110 c00d1a28 00000000 cf81ffa8
ffa0: c00a3a80 c00d2104 00000001 bef99fd9 00000002 00005409 00000001 01835910
ffc0: 00000001 bef99fd9 bef99f34 00000001 00000000 00000000 00000000 00000000
ffe0: 00000000 bef99f20 018211ac 01820efc 60000010 00000002 ffffffff ffffffff
Backtrace:
[<c00ce864>] (panic+0x0/0x12c) from [<c00d1a80>] (do_exit+0x64/0x614)
 r3:c03a40b4 r2:c03a40b4 r1:cf814c40 r0:c0358cc0
[<c00d1a1c>] (do_exit+0x0/0x614) from [<c00d2110>] (complete_and_exit+0x0/0x24)
[<c00d20f8>] (sys_exit+0x0/0x18) from [<c00a3a80>] (ret_fast_syscall+0x0/0x2c)
Code: eb006136 e59f20b0 e3a04000 e5923000 (e5844000)
---[ end trace a073d9a2bbc086a9 ]---
Fixing recursive fault but reboot is needed!

wlaf · 06-17-2012, 06:20 AM

I pressed 3, and it asks me the password. It seems that the password is the root password for the system, in which I've changed and now I don't remember! :-(

Code:

Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose:    9 3


PASSWORD: fiona828b
INFO:invalid password!
Charge: 100% [##########################################################]


Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose:    9 -


PASSWORD: fiona3a76
INFO:invalid password!
Charge: 100% [##########################################################]

Is there a solution?

knc1 · 06-17-2012, 07:11 AM

Quote:

Originally Posted by wlaf

I pressed 3, and it asks me the password. It seems that the password is the root password for the system, in which I've changed and now I don't remember! :-(

Code:

Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose:    9 3


PASSWORD: fiona828b
INFO:invalid password!
Charge: 100% [##########################################################]


Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose:    9 -


PASSWORD: fiona3a76
INFO:invalid password!
Charge: 100% [##########################################################]

Is there a solution?

Reset the root password (of the system running this application) to something you know.

The password you entered looks a lot like a Kindle password, not the one of the system that is running this application.

If you would share the details of the system you are running this on, someone could give you a better answer than "fix it".

wlaf · 06-17-2012, 07:54 AM

Quote:

Originally Posted by knc1

Reset the root password (of the system running this application) to something you know.

The password you entered looks a lot like a Kindle password, not the one of the system that is running this application.

If you would share the details of the system you are running this on, someone could give you a better answer than "fix it".

I'm using windows with putty, but I have access to linux (ubuntu and centos) and I know my root password on the system. But I don't know the root password for kindle! I thouthght it is fiona828b or fiona3a76, but none woked for me.
Btw, now I'm now connected to serial via putty and I'm trying to find password from serial number:

http://members.ping.de/~sven/kindle.html

But It seems that it doesn't work! :-(

knc1 · 06-17-2012, 07:58 AM

Quote:

Originally Posted by wlaf

I'm using windows with putty, but I have access to linux (ubuntu and centos) and I know my root password on the system. But I don't know the root password for kindle! I thouthght it is fiona828b or fiona3a76, but none woked for me.
Btw, now I'm now connected to serial via putty and I'm trying to find password from serial number:

http://members.ping.de/~sven/kindle.html

But It seems that it doesn't work! :-(

My apologies, I thought we where in the Fastboot GUI thread or at least using the "Fastboot GUI" tool.

I have seen the answer here recently, but I don't dare say where without a bit more sleep.

wlaf · 06-17-2012, 09:28 AM

supermagically, I came to uboot! Maybe I've been pressing Enter at the right time.
now I have this commands:

Code:

?       - alias for 'help'
autoscr - run script from memory
base    - print or set address offset
bdinfo  - print Board Info structure
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootm   - boot application image from memory
bootp - boot image via network using BootP/TFTP protocol
cmp     - memory compare
coninfo - print console devices and information
cp      - memory copy
crc32   - checksum calculation
dhcp  - invoke DHCP client to obtain IP/boot params
echo    - echo args to console
go      - start application at address 'addr'
help    - print online help
iminfo  - print header information for application image
itest - return true/false on integer compare
loadb   - load binary file over serial line (kermit mode)
loads   - load S-Record file over serial line
loady   - load binary file over serial line (ymodem mode)
loop    - infinite loop on address range
md      - memory display
mii     - MII utility commands
mm      - memory modify (auto-incrementing)
mtest   - simple RAM test
mw      - memory write (fill)
nfs   - boot image via network using NFS protocol
nm      - memory modify (constant address)
ping  - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
rarpboot- boot image via network using RARP/TFTP protocol
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
setenv  - set environment variables
sleep   - delay execution for some time
tftpboot- boot image via network using TFTP protocol
version - print monitor version

geekmaster · 06-17-2012, 01:11 PM

Quote:

Originally Posted by wlaf

I'm using windows with putty, but I have access to linux (ubuntu and centos) and I know my root password on the system. But I don't know the root password for kindle! I thouthght it is fiona828b or fiona3a76, but none woked for me.
Btw, now I'm now connected to serial via putty and I'm trying to find password from serial number:

http://members.ping.de/~sven/kindle.html

But It seems that it doesn't work! :-(

Default root passwords only have 3 hex digits (8 characters total). Because they are DES hashes, you can type extra characters if you want to and they just get ignored.

If you use the passwd command to change the password, then it gets stored as a salted MD5 hash, which uses all the characters you types (even if you changed it back to a fiona password).

Did you also try the mario password? Some computers need that instead...

hawhill · 06-18-2012, 10:17 AM

OK, I think it looks bad here. But first go and try what geekmaster suggested, i.e. trying out a few variations of the password.

If that doesn't work, I don't see a lot of options - especially none that have been tried out before. In fact, I'm learning for the first time (well, or my memory isn't too well, also possible) that the uboot menu is accessible.

uboot doesn't seem to be able to write to flash memory (and I'm somewhat puzzled that I don't see indications for reading flash memory either). So using the serial console, the option is probably to load (loadb/loady) a kernel with included initramfs (containing enough software to provide a basic rescue system) via the serial line and start it. Note that you would need to hand-tailor such a kernel (plus initramfs payload) yourself.

Another option is the Advanced Toolkit and the USB loader mode -- however, this way hasn't been gone before, either. And it's not quite clear what this mode is able to do, but in theory it could provide a backup/restore path like the one for the K4/K5.

knc1 · 06-18-2012, 10:36 AM

Quote:

Originally Posted by hawhill

Another option is the Advanced Toolkit and the USB loader mode -- however, this way hasn't been gone before, either. And it's not quite clear what this mode is able to do, but in theory it could provide a backup/restore path like the one for the K4/K5.

Different processor/SoC; K4/K5 is i.MX5*, others are i.MX3*
I seem to recall reading (on Freescale.com) that Advanced Toolkit does not support the i.MX3* series.
BIG NOTE: My memory may be playing tricks on me.

hawhill · 06-18-2012, 02:06 PM

Might be a special version of ATK for those boards, but there is one. I ran it - and failed. But I only gave it a short one-off try and didn't bother to look deeper, since I didn't have to ... I was just curious.

knc1 · 06-18-2012, 02:23 PM

Quote:

Originally Posted by hawhill

Might be a special version of ATK for those boards, but there is one. I ran it - and failed. But I only gave it a short one-off try and didn't bother to look deeper, since I didn't have to ... I was just curious.

I haven't bricked my K3 yet either.
May know more once forced into learning by a bricked K3.

geekmaster · 06-18-2012, 03:00 PM

I was able to get ATK communicating with my K3, but I did not go very far with it.

wlaf · 06-18-2012, 08:32 PM

Quote:

Originally Posted by geekmaster

Default root passwords only have 3 hex digits (8 characters total). Because they are DES hashes, you can type extra characters if you want to and they just get ignored.

If you use the passwd command to change the password, then it gets stored as a salted MD5 hash, which uses all the characters you types (even if you changed it back to a fiona password).

Did you also try the mario password? Some computers need that instead...

Yes, I tried mario, but without success. :-(
I've seen the de-bricking video several times, but could someone please tell me more about the process? After entering password, what is exactly exported, and at the next stage, how it is used to de-brick the device? I couldn't understand the way the guy "dd"s the file on the file system device.
Even a good link to read is appreciated. :-)

Also, I don't know much about the root file system hierarchy of a Kindle 3 device. How's the file system organised? And is there a readonly file system or all of the filesystem is writeable? I think it's great to have the output of these commands:

Code:

mount
cat /etc/fstab

Quote:

uboot doesn't seem to be able to write to flash memory (and I'm somewhat puzzled that I don't see indications for reading flash memory either). So using the serial console, the option is probably to load (loadb/loady) a kernel with included initramfs (containing enough software to provide a basic rescue system) via the serial line and start it. Note that you would need to hand-tailor such a kernel (plus initramfs payload) yourself.

Seems similar to this:
http://yifan.lu/2011/04/02/recoverin...rupt-kindle-2/
but it's for kindle 2.

Another question: when I attach kindle via usb, I see an unformatted device with about 3GB storage, is it the root file system? the link above says that pressing "1" recreates partitions, but as you know, this is not visible in the recovery menu, so is it ok?

Quote:

Another option is the Advanced Toolkit and the USB loader mode -- however, this way hasn't been gone before, either. And it's not quite clear what this mode is able to do, but in theory it could provide a backup/restore path like the one for the K4/K5.

Are you talking about this:
http://www.freescale.com/webapp/sps/..._TOOL_STD_1_67
Which port I should use and to which port I should connect? Normal serial and USB?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Damn you Amazon...	apastuszak	Amazon Kindle	37	05-03-2012 07:42 PM
What's with all the damn vampires?	Jack Silkstone	General Discussions	99	11-23-2011 10:23 AM
PRS-600 well...damn.	Zerhackermann	Sony Reader	11	01-23-2010 08:50 AM

06-18-2012, 10:17 AM	#40
hawhill Wizard Posts: 1,379 Karma: 2155307 Join Date: Nov 2010 Location: Goettingen, Germany Device: Kindle Paperwhite, Kobo Mini	OK, I think it looks bad here. But first go and try what geekmaster suggested, i.e. trying out a few variations of the password. If that doesn't work, I don't see a lot of options - especially none that have been tried out before. In fact, I'm learning for the first time (well, or my memory isn't too well, also possible) that the uboot menu is accessible. uboot doesn't seem to be able to write to flash memory (and I'm somewhat puzzled that I don't see indications for reading flash memory either). So using the serial console, the option is probably to load (loadb/loady) a kernel with included initramfs (containing enough software to provide a basic rescue system) via the serial line and start it. Note that you would need to hand-tailor such a kernel (plus initramfs payload) yourself. Another option is the Advanced Toolkit and the USB loader mode -- however, this way hasn't been gone before, either. And it's not quite clear what this mode is able to do, but in theory it could provide a backup/restore path like the one for the K4/K5.

06-18-2012, 02:06 PM	#42
hawhill Wizard Posts: 1,379 Karma: 2155307 Join Date: Nov 2010 Location: Goettingen, Germany Device: Kindle Paperwhite, Kobo Mini	Might be a special version of ATK for those boards, but there is one. I ran it - and failed. But I only gave it a short one-off try and didn't bother to look deeper, since I didn't have to ... I was just curious.

06-18-2012, 03:00 PM	#44
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773668 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	I was able to get ATK communicating with my K3, but I did not go very far with it.

Advert

Advert