Page 4 of 5

Re: Bricking and Unbricking device

Posted: Tue Jan 12, 2010 7:41 am
by aquadran
kang1 wrote:I've stopped at this point (after that reboot)

Code: Select all


 >> ONBOOT :: 0x59a50219 0x12821282
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(139,6)


 >> ONBOOT :: 0x59a50219 0x12821282


U-Boot 1.1.6 (Dec 12 2008 - 15:55:34)

DRAM:  128 MB
**************** device info  *******************
nPgsPerSLCBlk = 128
nPgsPerMLCBlk = 256
nSctsPerPg = 8
nNumOfUsBlks = 994
OneNAND[booting] mode / clk = S / 50Mhz
*************************************************
TinyBML[0] open success
env_relocate_spec
Success loading partition
Environment Data loading success!!
No ethernet found.
In:    serial
Out:   serial
Err:   serial
Net:   RTL8139#0
Hit any key to stop autoboot:  0

===============================
===============================
     BOOTROM DEBUG SESSION
===============================
1. ENVIRONMENT SETUP

2. SHOW PARTITION

===============================
0. JUMP TO UBOOT PROMPT
r. REBOOT
===============================
===============================
SELECT COMMAND: 0

LEONID # setenv ipaddr 192.168.1.104;setenv gatewayip 192.168.1.142;setenv serve
rip 192.168.1.113;setenv bootargs root=/dev/nfs rw nfsroot=192.168.1.142:/home/k
ang/test/squash/,nolock ethaddr=00:16:ce:32:10:34 ip=::::::dhcp console=ttyS1;tf
tp;bootm
Using RTL8139#0 device
TFTP from server 192.168.1.113; our IP address is 192.168.1.104
Filename 'uImage'.
Load address: 0x61000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######################################################
done
Bytes transferred = 3271568 (31eb90 hex)
## Booting image at 61000000 ...
   Image Name:   Linux-2.6.18_SELP-ARM
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3271504 Bytes =  3.1 MB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
OK

Starting kernel ...

CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv6TEJ), cr=00c5387f
Machine: Samsung-SDP83 Eval. Board(64bit 512MB)
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIPT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 2 zonelists.  Total pages: 76032
Kernel command line: root=/dev/nfs rw nfsroot=192.168.1.142:/home/kang/test/squa
sh/,nolock ethaddr=00:16:ce:32:10:34 ip=::::::dhcp console=ttyS1
WARNING: experimental RCU implementation.
PID hash table entries: 2048 (order: 11, 8192 bytes)
Samsung DTV Linux System timer initialize
sdp83 clock control (c) 2008 Samsung Electronics
SDP83 Core Clock: 600.0Mhz
SDP83 DDR2 Clock: 399.937Mhz
SDP83 AHB Clock: 140.62Mhz
SDP83 APB Clock: 140.62Mhz
Samsung DTV Linux Calcurate Timer Clock 0.199 us per tick
        Reset Value 0x0000c365
Console: colour dummy device 80x30
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 196MB 101MB = 297MB total
Memory: 297472KB available (2528K code, 1035K data, 104K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
sdp83 clock control (c) 2008 Samsung Electronics
SDP83 Core Clock: 600.0Mhz
SDP83 DDR2 Clock: 399.937Mhz
SDP83 AHB Clock: 140.62Mhz
SDP83 APB Clock: 140.62Mhz
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (double precision)
squashfs: version 3.1 (2006/08/19) Phillip Lougher
NTFS driver 2.1.29 [Flags: R/O].
Initializing Cryptographic API
io scheduler noop registered (default)
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
SDP I2C 0 port initialize base is 0xd3000100
SDP I2C 1 port initialize base is 0xd3000120
SDP I2C 2 port initialize base is 0xd3000140
SDP I2C 3 port initialize base is 0xd3000160
Samsung SDP I2c ver 0.7 access driver
Serial: S5H2X driver $Revision : 1.01 $
enter serial_request_port
s5h2x-uart: ttyS0 at MMIO map 0x30090a00 mem 0xf8090a00 (irq = 19) is a S5H2X
enter serial_request_port
s5h2x-uart: ttySD0 at MMIO map 0x30090a00 mem 0xf8090a00 (irq = 19) is a S5H2X
enter serial_request_port
s5h2x-uart: ttyS1 at MMIO map 0x30090a40 mem 0xf8090a40 (irq = 20) is a S5H2X
enter serial_request_port
s5h2x-uart: ttySD1 at MMIO map 0x30090a40 mem 0xf8090a40 (irq = 20) is a S5H2X
enter serial_request_port
s5h2x-uart: ttyS2 at MMIO map 0x30090a80 mem 0xf8090a80 (irq = 21) is a S5H2X
enter serial_request_port
s5h2x-uart: ttySD2 at MMIO map 0x30090a80 mem 0xf8090a80 (irq = 21) is a S5H2X
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
8139too Fast Ethernet driver 0.9.27
eth0: RealTek RTL8139 at 0x6000, 00:12:fb:b9:72:a0, IRQ 12
[BIF:IN ] ++FSR_BML_Init(nFlag: 0x0)
LinuStoreIII_TERR: bml_blkdev_create[355] No such device or address, 1(0x9002000
0)
FSR: Registered TinyFSR Driver.
ehci-s5h2x ehci-s5h2x.0: initializing S5H2XXX-SOC USB Controller
ehci-s5h2x ehci-s5h2x.0: S5H2X On-chip EHCI Host controller
ehci-s5h2x ehci-s5h2x.0: new USB bus registered, assigned bus number 1
ehci-s5h2x ehci-s5h2x.0: s5h2x_ehci_setup success
ehci-s5h2x ehci-s5h2x.0: irq 15, io mem 0x30070000
ehci-s5h2x ehci-s5h2x.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ehci-s5h2x ehci-s5h2x.0: ehci-s5h2x probing completed.
ehci-s5h2x ehci-s5h2x.1: initializing S5H2XXX-SOC USB Controller
ehci-s5h2x ehci-s5h2x.1: S5H2X On-chip EHCI Host controller
ehci-s5h2x ehci-s5h2x.1: new USB bus registered, assigned bus number 2
ehci-s5h2x ehci-s5h2x.1: s5h2x_ehci_setup success
ehci-s5h2x ehci-s5h2x.1: irq 17, io mem 0x30080000
ehci-s5h2x ehci-s5h2x.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
ehci-s5h2x ehci-s5h2x.1: ehci-s5h2x probing completed.
ohci-s5h2x ohci-s5h2x.0: S5H2X On-chip OHCI Host controller
ohci-s5h2x ohci-s5h2x.0: new USB bus registered, assigned bus number 3
ohci-s5h2x ohci-s5h2x.0: irq 14, io mem 0x30078000
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 1 port detected
ohci-s5h2x ohci-s5h2x.1: S5H2X On-chip OHCI Host controller
ohci-s5h2x ohci-s5h2x.1: new USB bus registered, assigned bus number 4
ohci-s5h2x ohci-s5h2x.1: irq 16, io mem 0x30088000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 192.168.1.1, my address is 192.168.1.104
IP-Config: Complete:
      device=eth0, addr=192.168.1.104, mask=255.255.255.0, gw=192.168.1.1,
     host=kang, domain=, nis-domain=(none),
     bootserver=192.168.1.1, rootserver=192.168.1.142, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.142
Looking up port of RPC 100005/1 on 192.168.1.142
VFS: Mounted root (nfs filesystem).
Freeing init memory: 104K
[SERIAL INPUT MANAGE] Managed tty_struct(.name:ttyS1) Setup!!!
[SERIAL INPUT MANAGE] disable_serial : ~~bye(len:5)
[SERIAL INPUT MANAGE] enable_serial : debug(len: 5)

[27_64_512] Linux version 2.6.18_SELP-ARM (aquadran@server) (gcc version 4.2.0 2
0070514 (GPL2)) #79 PREEMPT Mon Jan 4 22:47:02 CET 2010

================================================================================

 SAMSUNG: v2.6.18_SELP_3.X_GA_bayhill+/A1(P24)
         (Detailed Information: /sys/selp/vd/lspinfo/summary)

================================================================================


>> ONBOOT :: 0x59a50219 0x12821282
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(139,6
Some problems with NFS server? I've started tftp and NFS at different pcs.
">> ONBOOT :: 0x59a50219 0x12821282
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(139,6[/code]
"
your nfs server is fine, tv rebooted.
I wonder why it reboot. Do you have watchdog turn off ?
look what you have in /etc/rcS
if you not have watchdog turn off put MicomCtrl 23 into /etc/rcS

Re: Bricking and Unbricking device

Posted: Tue Jan 12, 2010 7:49 am
by aquadran
btw, this kernel should also boot from usb drive.

Re: Bricking and Unbricking device

Posted: Tue Jan 12, 2010 11:47 am
by aquadran
kang1 wrote:Watchdog is turned on...
I've tried to stop it by putting /mtd_boot/MicomCtrl 23 into /etc/rcS .
Should I put only MicomCtrl 23 command ? It will be recognized without directory ?
full directory would be best.
"/mtd_boot/" really ? check where you have MicomCtrl

Re: Bricking and Unbricking device

Posted: Tue Jan 12, 2010 9:16 pm
by aquadran
it looks like dtvlog logging thing crash. hmm maybe some mount is missing.
make sure you have it:
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dtv type tmpfs (rw)
devpts on /dev/pts type devpts (rw)

try this:
mount proc /proc -t proc
mount sysfs /sys -t sysfs
mount -t devpts devpts /dev/pts
mount -t tmpfs none /dtv -o size=10M,mode=1777