• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 [2]
Author Topic: [HELP] Guruplug bricked after kernel upgrade  (Read 9345 times)
radael
Jr. Member
**

Karma: 1
Posts: 57


View Profile
« Reply #15 on: January 13, 2011, 01:17:31 AM »

I read the forums for 4 days.  Tried four different ways to fix my kernel.  We are not the only ones.
Logged

pacolm
Full Member
***

Karma: 1
Posts: 102


View Profile
« Reply #16 on: January 13, 2011, 11:05:18 AM »

Hi,

 Here is the bootlog right now, any clue?

Code:
U-Boot 2010.03-01161-gd91b0a9 (Apr 22 2010 - 03:24:41)
Marvell-GuruPlug

SoC:   Kirkwood 88F6281_A0
DRAM:  512 MB
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0, egiga1
88E1121 Initialized on egiga0
88E1121 Initialized on egiga1
Hit any key to stop autoboot:  3  2  1  0
*** ERROR: `ipaddr' not set
ping failed; host 192.168.2.1 is not alive
No link on egiga1
*** ERROR: `ipaddr' not set
ping failed; host 192.168.2.1 is not alive
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... Device NOT ready
   Request Sense returned 02 3A 00
1 Storage Device(s) found

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 06400000 ...
   Image Name:   Linux-2.6.33.2-00003-g4b82fc0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2688524 Bytes =  2.6 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.33.2-00003-g4b82fc0 (root@msi-linux-build.marvell.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33.fa1)) #1 PREEMPT Thu Apr 22 03:29:35 PDT 2010
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell GuruPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB = 512MB total
Memory: 513536KB available (4808K code, 862K data, 140K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:114
Console: colour dummy device 80x30
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A0, TCLK=200000000.
Feroceon L2: Cache support initialised.
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: 00
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4014, nTxLock = 32113
msgmni has been set to 1003
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 3556 at 0x00001bc80000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "root"
UBI: MTD device size:            507 MiB
UBI: number of good PEBs:        4055
UBI: number of bad PEBs:         1
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             4011
UBI: total number of reserved PEBs: 44
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 2/1
UBI: image sequence number: 0
UBI: background thread "ubi_bgt0d" started, PID 448
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:50:43:67:64:06
net eth1: port 0 with MAC address 00:50:43:67:64:07
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mice: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: guruplug:red:health
Registered led device: guruplug:green:health
Registered led device: guruplug:red:wmode
Registered led device: guruplug:green:wmode
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mmc0: new high speed SDIO card at address 0001
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
rtc-mv rtc-mv: setting system clock to 2011-01-13 18:03:29 UTC (1294941809)
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs", error -19
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            1024 mtdblock0 (driver?)
1f01            4096 mtdblock1 (driver?)
1f02          519168 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[<c003062c>] (unwind_backtrace+0x0/0xd4) from [<c003da9c>] (panic+0x48/0x13c)
[<c003da9c>] (panic+0x48/0x13c) from [<c0008f3c>] (mount_block_root+0x1c4/0x20c)
[<c0008f3c>] (mount_block_root+0x1c4/0x20c) from [<c0009114>] (prepare_namespace+0x8c/0x1cc)
[<c0009114>] (prepare_namespace+0x8c/0x1cc) from [<c000875c>] (kernel_init+0xe0/0x11c)
[<c000875c>] (kernel_init+0xe0/0x11c) from [<c002c3f0>] (kernel_thread_exit+0x0/0x8)

 Seems that is not able to find any OS, isn't it?. Is there any reliable way of having a guruplug exactly as a new guruplug?

PacoLM
Logged

radael
Jr. Member
**

Karma: 1
Posts: 57


View Profile
« Reply #17 on: January 13, 2011, 12:38:42 PM »

Looks like the root file system has a problem.

http://plugcomputer.org/plugwiki/index.php/Reflashing_images_on_the_GuruPlug

"Burn the Rootfs image"
Logged

pacolm
Full Member
***

Karma: 1
Posts: 102


View Profile
« Reply #18 on: January 13, 2011, 12:49:18 PM »

Yes, in this step I got an error starting the tftp but I thought that something was wrong in my uboot.
Logged

richard
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #19 on: January 13, 2011, 03:05:27 PM »

I've had this error message in the past

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

what it was for me was that I had not selected the following option in menuconfig during the build;

File Systems --> Miscellaneous File Systems -->  UBIFS file system support

Make sure it is built into the Kernel (i.e. showing
  • and not [M]) as the kernel needs it to read the file system

Regards

Rich
Logged

pacolm
Full Member
***

Karma: 1
Posts: 102


View Profile
« Reply #20 on: January 13, 2011, 03:20:11 PM »

I've had this error message in the past

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

what it was for me was that I had not selected the following option in menuconfig during the build;

File Systems --> Miscellaneous File Systems -->  UBIFS file system support

Make sure it is built into the Kernel (i.e. showing
  • and not [M]) as the kernel needs it to read the file system

Regards

Rich

Could you tell me where are this options?  Regards.
Logged

richard
Newbie
*

Karma: 0
Posts: 12


View Profile
« Reply #21 on: January 13, 2011, 03:43:22 PM »

When you prepare the kernel for the build using

make ARCH=arm menuconfig

Follow one of the building kernel wikis

Rich
Logged

radael
Jr. Member
**

Karma: 1
Posts: 57


View Profile
« Reply #22 on: January 13, 2011, 05:02:55 PM »

I had the same errors when booting from an external hard disk, before using rootwait in the bootargs.  But, since you are trying to boot from flash, this should not be a problem.

If you have not compiled your own kernel, then the one you are using should already support ubifs.  Your U-boot variables support it:

     x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
Logged

pacolm
Full Member
***

Karma: 1
Posts: 102


View Profile
« Reply #23 on: January 15, 2011, 02:17:24 AM »

Hi,

 Have it fixed. I will post the process, I don't have time right now!. Thanks to all the people who helped documenting different processes to return zombie plugs back to life!

PacoLM
Logged

pacolm
Full Member
***

Karma: 1
Posts: 102


View Profile
« Reply #24 on: January 19, 2011, 12:32:26 AM »

Hi,

 Finally, I was able to get my guruplug working again. I was having an error tftf'ing the rootfs file, but it was due to the incorrect tftp version installed on the server. As it's a big file, the standard tftp failed, so I had to install another tftp server application, as read somewhere in the forum.
 After reinstalling the system, some modules of a newer kernel were needed, so I scp'ed them. Now it boots the newer kernel (Linux guruplug-debian 2.6.33.7), and the best of all is that Zoneminder now is working much better, with cpu loads less than half. I do not know what's the cause of it, but each zmc process was dragging about 23% of cpu before the 'accidental kernel upgrade', and now is consistently ~6%. The load in the ZM console is ~0.1%!!!!!

 I want to thank all the users that pointed me to the correct path to get my guruplug back to life (specially radael & richard).

 I have also written a process to get Zoneminder working from scratch, so if anyone is interested, ask for it using PM.

 Thanks again,

PacoLM
Logged

radael
Jr. Member
**

Karma: 1
Posts: 57


View Profile
« Reply #25 on: January 19, 2011, 06:39:20 PM »

Again, you are too kind, PacoLM.  Mostly we only encourage.

It might help others if you were to make a wiki page about Zoneminder.

Just go to page   http://plugcomputer.org/plugwiki/index.php/ZoneMinder, and use the "create" button at the top of the page.  Just be sure to add these lines to the bottom of the page:

[[Category:HowTo]]
[[Category:GuruPlug]]
Logged

pacolm
Full Member
***

Karma: 1
Posts: 102


View Profile
« Reply #26 on: January 26, 2011, 03:44:54 AM »

Wiki page created

http://plugcomputer.org/plugwiki/index.php/ZoneMinder

but still working on it.
Logged

Pages: 1 [2]
Print
Jump to: