• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Hardware and U-Boot firmware / Hardware / Re: Flashing LEDs meaning? on: April 08, 2011, 11:02:59 PM
Mine's one of the older models. Certainly > 1 year old. I hope they've improved, as I've recommended the 'plug to a friend as the platform for a product...

Rony
2  Hardware and U-Boot firmware / Hardware / Re: Flashing LEDs meaning? on: April 06, 2011, 01:11:58 PM
Thanks hanker, that's exactly what I needed! Cool My sheeva plug is back from the dead, and my junk box now has some free space, previously taken up by an unused 5V power supply.

Cheers,

  Rony
3  Hardware and U-Boot firmware / Hardware / Re: Flashing LEDs meaning? on: April 06, 2011, 02:17:47 AM
That's what I was afraid of  Sad

Thanks for the quick reply. Guess it's time to crack my sheeva open and connect a spare 5V power supply to it directly. Anyone done this before?

Rony
4  Hardware and U-Boot firmware / Hardware / Flashing LEDs meaning? on: April 05, 2011, 11:28:48 PM
Greetings,

After disconnecting and reconnecting my SheevaPlug from the mains, I see both  the NIC's LEDs and the green LDE (but not the adjacent bue one) flashing at about 2 Hz. Other than that, the device shows no sign of life via USB/console or NIC. Recycling power and the reset button have no effect.

Is this what a dying power supply looks like, or is this something else?

Thanks,

  Rony
5  Hardware and U-Boot firmware / Hardware / Re: Suspect bad RAM - how to test? on: March 03, 2010, 10:02:46 PM
Hi,

I think you're seeing an issue with the NAND, which is the built-in flash memory.

I'm having problems with the RAM, which is separate. In any case, I've just received an RMA for the device, and am shipping it back to Globalscale Technologies for repair.

Rony
6  Hardware and U-Boot firmware / Hardware / Suspect bad RAM - how to test? on: February 18, 2010, 05:39:38 AM
Hi,

I'm getting crashes whenever I do some non-trivial i/o (apt-get safe-upgrade, for example, or just copying files from one FS to another. This happens when booting of a USB drive, NFS or SD card. (I can't manage to boot of nand, which may or may not be related).

Finally, the U-Boot 'mtest function freezes as follows:
Quote
U-Boot 1.1.4 (Dec 23 2009 - 13:32:43) Marvell version: 3.4.27

Marvell>> mtest
Pattern 00000000  Writing...

Any idea how I can run more diagnostics?

I'm attaching the output of the serial port illustrating such a crash.
The system was in the middle of apt-get install rsync:

# apt-get install rsync
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following NEW packages will be installed:
  rsync
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 340kB of archives. After unpacking 672kB will be used.
Writing extended state information... Done
Get:1 http://ftp.uk.debian.org lenny/main rsync 3.0.3-2 [340kB]
Fetched 340kB in 3s (97.2kB/s)
Timeout, server not responding.

The dump starts with:
[ 1569.690000] Unable to handle kernel paging request at virtual address 00c90068
[ 1569.700000] Unable to handle kernel paging request at virtual address 0b97ffb0
[ 1569.700000] pgd = df054000
[ 1569.700000] [0b97ffb0] *pgd=00000000
[ 1569.700000] Internal error: Oops: 805 [#1]

Any ideas?

Rony


Rony
7  Hardware and U-Boot firmware / U-Boot stuff / Re: nandwrite to /dev/mtd2 crashes kernel on: February 15, 2010, 10:08:32 PM
Yeah, I thought so too, at first, so I added some swap:
Quote
# free
              total         used         free       shared      buffers
  Mem:       515728         9764       505964            0          552
 Swap:        80316            0        80316
Total:       596044         9764       586280

This is a recovery process - I'm trying to rewrite the fs that came on the device with that supplied on the cdrom, no reason why this should run out of memory.

Rony

8  Hardware and U-Boot firmware / U-Boot stuff / nandwrite to /dev/mtd2 crashes kernel on: February 15, 2010, 02:04:04 PM
Hi,

Trying to recover from a munged filesystem, I keep crashing on
nandwrite p  /dev/mtd2  ubuntu-9.0.5.Release.jffs2

I suspect it may be related to three bad blocks that are skipped:
Quote
Code:
ubuntu-9.0.5.Release.jffs2
Writing data to block 0
Writing data to block 20000
Writing data to block 40000
[...]
Writing data to block 2660000
Writing data to block 2680000
Bad block at 2680000, 1 block(s) from 2680000 will be skipped
Writing data to block 26a0000
Bad block at 26a0000, 1 block(s) from 26a0000 will be skipped
Writing data to block 26c0000
Writing data to block 26e0000
[...]
Writing data to block 7960000
Unable to handle kernel paging request at virtual address 8bf512cc
pgd = dfae0000
[8bf512cc] *pgd=00000000
Internal error: Oops: 5 [#1]
Modules linked in:
CPU: 0    Not tainted  (2.6.22.18 #1)
PC is at dnotify_parent+0x28/0x88
LR is at vfs_write+0x104/0x148
pc : [<c0195bec>]    lr : [<c0166178>]    psr: 20000013
sp : dfd59f40  ip : dfd59f58  fp : dfd59f54
r10: 00000000  r9 : dfd58000  r8 : c002c5a8
r7 : 00000800  r6 : c0012198  r5 : dff2d758  r4 : dfc93d38
r3 : 8bf511d8  r2 : 00000006  r1 : 00000002  r0 : dff2d758
Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  Segment user
Control: 0005397f  Table: 1fae0000  DAC: 00000015
Process nandwrite (pid: 307, stack limit = 0xdfd58268)
Stack: (0xdfd59f40 to 0xdfd5a000)
9f40: dfd58000 00000002 dfd59f7c dfd59f58 c0166178 c0195bd4 dfd90820 00000800
9f60: 00013500 dfd908c0 00000800 000000b5 dfd59fa4 dfd59f80 c01667f8 c0166084
9f80: dfd59fac 00000000 00000800 0797a000 00000000 00013500 00000000 dfd59fa8
9fa0: c002c400 c01667ac 0797a800 00000000 00000003 00013500 00000800 00000000
9fc0: 0797a000 00000000 00013500 000000b5 00000003 00013494 00000000 be896bc4
9fe0: 40156000 be896ba0 00009204 400de788 60000010 00000003 00000000 00000000
Backtrace:
[<c0195bc4>] (dnotify_parent+0x0/0x88) from [<c0166178>] (vfs_write+0x104/0x148)
 r4:00000002
[<c0166074>] (vfs_write+0x0/0x148) from [<c01667f8>] (sys_pwrite64+0x5c/0x80)
 r7:000000b5 r6:00000800 r5:dfd908c0 r4:00013500
[<c016679c>] (sys_pwrite64+0x0/0x80) from [<c002c400>] (ret_fast_syscall+0x0/0x2c)
 r6:00013500 r5:00000000 r4:0797a000
Code: e3530000 099da810 e5904014 e5943008 (e59330f4)
Unable to handle kernel paging request at virtual address 4ffedfbd
pgd = dfae0000
[4ffedfbd] *pgd=00000000
Internal error: Oops: 801 [#2]
Modules linked in:
CPU: 0    Not tainted  (2.6.22.18 #1)
PC is at __mutex_lock_slowpath+0x3c/0x8c
LR is at mutex_lock+0x20/0x28
pc : [<c00329dc>]    lr : [<c00328b8>]    psr: a0000013
sp : dfd59c50  ip : dfd59c80  fp : dfd59c7c
r10: c102acd4  r9 : c102accc  r8 : 0000000b
r7 : 00000002  r6 : ffffffff  r5 : dfde0580  r4 : c102acd4
r3 : c102acd8  r2 : dfd59c54  r1 : 4ffedfbd  r0 : c102acd4
Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  Segment user
Control: 0005397f  Table: 1fae0000  DAC: 00000015
Process nandwrite (pid: 307, stack limit = 0xdfd58268)
Stack: (0xdfd59c50 to 0xdfd5a000)
9c40:                                     00000000 c102acd8 dfde0580 c080d400
9c60: c102abd0 c102abd0 00000010 c0022040 dfd59c8c dfd59c80 c00328b8 c00329b0
9c80: dfd59cd4 dfd59c90 c018fa4c c00328a8 c0012a38 c0012a38 dfd59cbc 00000000
9ca0: 00000000 00000010 dfd59cd4 c09250c0 c102abd0 00000010 c0022040 0000000b
9cc0: c0887220 dfc93538 dfd59d0c dfd59cd8 c0166a78 c018fa20 00000000 00000000
9ce0: be882000 dfa02e90 dfa02f98 dfa02e90 c0022040 0000000b 8bf512cc c0022040
9d00: dfd59d1c dfd59d10 c0166bbc c0166a14 dfd59d34 dfd59d20 c0155af4 c0166b98
9d20: dfd59d44 00000000 dfd59d64 dfd59d38 c0155bf0 c0155ac4 dfd59d40 00000000
9d40: 00000021 c03fa95c c0022040 c0022074 dfde0580 00000001 dfd59d7c dfd59d68
9d60: c0120f84 c0155b20 c0139430 c0022040 dfd59d9c dfd59d80 c01246d4 c0120f50
9d80: 00000001 dfde0580 dfd58000 dfd59ef8 dfd59dbc dfd59da0 c0125d88 c0124614
9da0: dfd59dbc dfd59db0 c0122b2c 00000000 dfd59dcc dfd59dc0 c00f2a34 c0125bac
9dc0: dfd59dec dfd59dd0 c00f52c4 c00f28a0 ffffffec 00000005 dfde0580 dfa02d30
9de0: dfd59e34 dfd59df0 c00f54e0 c00f5268 c02c9320 c02c7cec dfd59e1c dfd59e08
9e00: dfd59ef8 00000005 dff47000 c03da278 00000005 8bf512cc dfd59ef8 c002c5a8
9e20: 60000013 00000000 dfd59e4c dfd59e38 c00f55a0 c00f52e4 c03da278 00000005
9e40: dfd59ef4 dfd59e50 c0027238 c00f5598 dfd59e74 dfd59e60 c02c8fd0 c011ecfc
9e60: 00000000 00000000 dfd59eac dfd59e78 c02c9b14 c02c8f98 dfca7798 00000000
9e80: a0000013 0797a000 00000000 1fd00000 00000800 dfcf7860 dfd59fa8 00013500
9ea0: dfd59edc dfd59eb0 c02c224c c02c9a70 00000800 dfd59f24 dff47000 dff47000
9ec0: 00000800 00000800 dff47000 00000000 dfd59f54 dfd59ee0 ffffffff dfd59f2c
9ee0: c0012198 00000800 dfd59f54 dfd59ef8 c002be2c c002720c dff2d758 00000002
9f00: 00000006 8bf511d8 dfc93d38 dff2d758 c0012198 00000800 c002c5a8 dfd58000
9f20: 00000000 dfd59f54 dfd59f58 dfd59f40 c0166178 c0195bec 20000013 ffffffff
9f40: dfd58000 00000002 dfd59f7c dfd59f58 c0166178 c0195bd4 dfd90820 00000800
9f60: 00013500 dfd908c0 00000800 000000b5 dfd59fa4 dfd59f80 c01667f8 c0166084
9f80: dfd59fac 00000000 00000800 0797a000 00000000 00013500 00000000 dfd59fa8
9fa0: c002c400 c01667ac 0797a800 00000000 00000003 00013500 00000800 00000000
9fc0: 0797a000 00000000 00013500 000000b5 00000003 00013494 00000000 be896bc4
9fe0: 40156000 be896ba0 00009204 400de788 60000010 00000003 00000000 00000000
Backtrace:
[<c00329a0>] (__mutex_lock_slowpath+0x0/0x8c) from [<c00328b8>] (mutex_lock+0x20/0x28)
 r7:c0022040 r6:00000010 r5:c102abd0 r4:c102abd0
[<c0032898>] (mutex_lock+0x0/0x28) from [<c018fa4c>] (inotify_inode_queue_event+0x3c/0xdc)
[<c018fa10>] (inotify_inode_queue_event+0x0/0xdc) from [<c0166a78>] (__fput+0x74/0x184)
[<c0166a04>] (__fput+0x0/0x184) from [<c0166bbc>] (fput+0x34/0x38)
[<c0166b88>] (fput+0x0/0x38) from [<c0155af4>] (remove_vma+0x40/0x5c)
[<c0155ab4>] (remove_vma+0x0/0x5c) from [<c0155bf0>] (exit_mmap+0xe0/0x11c)
 r5:00000000 r4:dfd59d44
[<c0155b10>] (exit_mmap+0x0/0x11c) from [<c0120f84>] (mmput+0x44/0xc4)
 r7:00000001 r6:dfde0580 r5:c0022074 r4:c0022040
[<c0120f40>] (mmput+0x0/0xc4) from [<c01246d4>] (exit_mm+0xd0/0xdc)
 r4:c0022040
[<c0124604>] (exit_mm+0x0/0xdc) from [<c0125d88>] (do_exit+0x1ec/0x7c4)
 r6:dfd59ef8 r5:dfd58000 r4:dfde0580
[<c0125b9c>] (do_exit+0x0/0x7c4) from [<c00f2a34>] (die+0x1a4/0x1f4)
[<c00f2890>] (die+0x0/0x1f4) from [<c00f52c4>] (__do_kernel_fault+0x6c/0x7c)
[<c00f5258>] (__do_kernel_fault+0x0/0x7c) from [<c00f54e0>] (do_page_fault+0x20c/0x224)
 r7:dfa02d30 r6:dfde0580 r5:00000005 r4:ffffffec
[<c00f52d4>] (do_page_fault+0x0/0x224) from [<c00f55a0>] (do_translation_fault+0x18/0x88)
[<c00f5588>] (do_translation_fault+0x0/0x88) from [<c0027238>] (do_DataAbort+0x3c/0x9c)
 r5:00000005 r4:c03da278
[<c00271fc>] (do_DataAbort+0x0/0x9c) from [<c002be2c>] (__dabt_svc+0x4c/0x60)
Exception stack(0xdfd59ef8 to 0xdfd59f40)
9ee0:                                                       dff2d758 00000002
9f00: 00000006 8bf511d8 dfc93d38 dff2d758 c0012198 00000800 c002c5a8 dfd58000
9f20: 00000000 dfd59f54 dfd59f58 dfd59f40 c0166178 c0195bec 20000013 ffffffff
 r7:00000800 r6:c0012198 r5:dfd59f2c r4:ffffffff
[<c0195bc4>] (dnotify_parent+0x0/0x88) from [<c0166178>] (vfs_write+0x104/0x148)
 r4:00000002
[<c0166074>] (vfs_write+0x0/0x148) from [<c01667f8>] (sys_pwrite64+0x5c/0x80)
 r7:000000b5 r6:00000800 r5:dfd908c0 r4:00013500
[<c016679c>] (sys_pwrite64+0x0/0x80) from [<c002c400>] (ret_fast_syscall+0x0/0x2c)
 r6:00013500 r5:00000000 r4:0797a000
Code: e1a04000 e50b3028 e3e06000 e3a07002 (e5812000)
Fixing recursive fault but reboot is needed!
[..]

Any suggestions?

Rony
9  Hardware and U-Boot firmware / U-Boot stuff / ext2fs doesn't support tripple indirect blocks on: February 14, 2010, 01:47:01 PM
Hi,

Trying to recover via USB flash, I get the above after a few minutes of
.........................
.........................
.........................
.........................

Updating the U-Boot image to 3.4.27 had no effect.

Can't get the plug to boot via NFS either. I'm beginning to run out of options...

Any ideas/suggestions/howtos/hints welcome.

Rony
10  Hardware and U-Boot firmware / U-Boot stuff / Boot from NFS fails: no init found on: February 12, 2010, 11:56:08 PM
Hi,

Trying to recover from a bad update (which is the topic of another post), I'm booting from tftp/NFS as
described in the note from Marvell (Writing Jaunty Filesystem an the NAND flash rev 1.2).

All goes well (tftp download, boot, nfs mount) until the kernel starts running. Here are the last few lines
on the console:
Code:
VFS: mounted root (nfs filesystem).
Freeing init memory: 124k
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found. Try passing init= option to kernel.


Any solutions/ideas/suggestions welcome!

Thanks,

  Rony
Pages: [1]