VDX6740 Booting Problem

Nukhet_Aslan1 — Thu, 09 Aug 2018 18:19:00 GMT

I have a BR-VDX6740T and while it is booting gives the error below . What could e the source of problem?

Thank you

INIT: version 2.78 booting

e2fsck 1.41.12 (17-May-2010)

/dev/sda1: clean, 15806/122160 files, 183016/488281 blocks

e2fsck 1.41.12 (17-May-2010)

/dev/sda2: recovering journal

/dev/sda2: clean, 6976/122160 files, 124698/488192 blocks

Firmware Integrity Check is default off

Bypassing firmware validation.

mount: sysfs already mounted or /sys busy

mount: according to mtab, none is already mounted on /sys

mknod: /dev/fsl-hv: File exists

Hostname is VDX-10

INIT: Entering runlevel: 3

FIPS-mode test application

1. Non-Approved cryptographic operation test...

a. Excluded algorithm (MD5)...successful

b. Included algorithm (D-H)...successful

2. Automatic power-up self test...successful

3. AES-128,192,256 CBC encryption/decryption...successful

4. RSA key generation and encryption/decryption...successful

4.1. RSA 2048 with 'SHA256' testing...successful

5. TDES-CBC encryption/decryption...successful

6a. SHA-1 hash...successful

6b. SHA-256 hash...successful

6c. SHA-512 hash...successful

6d. HMAC-SHA-1 hash...successful

6e. HMAC-SHA-224 hash...successful

6f. HMAC-SHA-256 hash...successful

6g. HMAC-SHA-384 hash...successful

6h. HMAC-SHA-512 hash...successful

7. Non-Approved cryptographic operation test...

a. Excluded algorithm (MD5)...Not executed

b. Included algorithm (D-H)...successful as expected

8. Zero-ization...Successful

9. TLS KDF...successful

10. SSH KDF...successful

All tests completed with 0 errors

Waiting to starting configuration management service

Starting configuration management service

[wmd_init]: chunk_size = 0xa00000

[wmd_init]: Checksum does not match. current_cksum = 0x16c0388f stored_cksum = 0x8fd5a6c1

[wmd_init]: FPGA version = 0x70007445

[wmd_init]: reset_reason = 0x1

[wmd_init]: updated reset_reason = 0x0

Reset reason = 0x1

wmem: b0004000:247439360

tbuf: 8ff00000:536854528

Found 1(threshold 5) abnormal reboots within 3000 seconds window(threshold)

KernelSpace rastrace_register

SWBD module launch ... Thu Aug 9 17:19:56 EEST 2018

Castor: PCIe Err handler init plat_pci_init[636]

bhpc_irq_init: Using default device map. Size 10

pcie_event_isr: ###### virq 174 core 1 MCSR 0x0 MSR 0x10021002 count 1

plat_pcie_error:Last addresses 0x0 0x0 0x0 0x0

0x0 0x0 0x0 0x0

0x0 0x0

CPLD INIT DONE

PCIe Event [unknown] slot 0 Source Bus 0 Dev 0 MM Parent Bus 0 Dev 0 Events: 1

AQ1402: Loaded Platform 137

MDIO Driver: Name [Freescale P4080DS MDIO Bus], Address [8acaa220]

GPIO CCSR phys addr = 0xffe130000, virt addr = 0xd830a000

cbr_rev_init: pci config word 0xc0220008 for Castors

cbr_rev_init: prs_reg[0].ctrl=0x00000102

cbr_rev_init: chip_rev detected=2

Cobra rev B found

Found Castor-T Type board Blade ID 145

Info: panic dump has been initialized!

Creating L3-L2 fifo Thu Aug 9 17:20:07 EEST 2018 ...

Starting HASM ... Thu Aug 9 17:20:07 EEST 2018

Exisitng reboot reason fsize = 5 rb=

usb 1-1: device descriptor read/64, error -110

usb 1-1: device descriptor read/64, error -110

usb 1-1: device descriptor read/64, error -110

usb 1-1: device descriptor read/64, error -110

usb 1-1: device descriptor read/8, error -110

usb 1-1: device descriptor read/8, error -110

usb 1-1: device descriptor read/8, error -110

usb 1-1: device descriptor read/8, error -110

end_request: I/O error, dev sda, sector 65609

EXT4-fs error (device sda1): ext4_find_entry: reading directory #7044 offset 0

Aborting journal on device sda1-8.

EXT4-fs (sda1): delayed block allocation failed for inode 7022 at logical offset 0 with max blocks 1 with error -30

This should not happen!! Data will be lost

EXT4-fs error (device sda1) in ext4_da_writepages: Journal has aborted

EXT4-fs (sda1): previous I/O error to superblock detected

EXT4-fs error (device sda1) in ext4_new_inode: Journal has aborted

EXT4-fs error (device sda1) in ext4_reserve_inode_write: Journal has aborted

EXT4-fs error (device sda1) in ext4_reserve_inode_write: Journal has aborted

/etc/rc.d/rc3.d/S99sshd: /usr/sbin/sshd: Input/output error

EXT4-fs error (device sda1) in ext4_da_write_begin: IO failure

EXT4-fs error (device sda1): ext4_journal_start_sb: Detected aborted journal

EXT4-fs (sda1): Remounting filesystem read-only

EXT4-fs (sda1): ext4_da_writepages: jbd2_start: 1024 pages, ino 7022; err -30

INIT: cannot execute "/sbin/getty"

EXT4-fs (sda1): I/O error while writing superblock

INIT: cannot execute "/sbin/getty"

JBD2: I/O error detected when updating journal superblock for sda1-8.

journal commit I/O error

[store_cksum]: /var/wmd_cksum does not exists.

Unable to handle kernel paging request for data at address 0xfffffff2

Faulting instruction address: 0xc1502630

Oops taken on: 2018-08-09 at 14:22:06

Oops: Kernel access of bad area, sig: 11 [#1]

PREEMPT SMP NR_CPUS=4 LTT NESTING LEVEL : 0

SILKWORM PB HV

NIP: c1502630 LR: c15026f8 CTR: 40577514

REGS: 8520fc70 TRAP: 0300 Tainted: P (2.6.34.6)

MSR: 10029002 CR: 28000428 XER: 20000000

DEAR: fffffff2, ESR: 00000000

TASK = 881809a0[1781] 'hasmd' THREAD: 8520c000

Last syscall: -1 CPU: 0

GPR00: c15026f8 8520fd20 881809a0 ffffffe2 4079d9c0 4075ed40 ffffffff ffffffe0

GPR08: c1503bb4 000001dd 00000063 8520fd20 28000484 100609c0 10082354 0ffc5438

GPR16: 00000000 ffff9008 00000089 00000000 3f842b77 0000006e 3fffffff c1503934

GPR24: c1503bb4 c15046c0 8f601fe0 c15044c4 8f4ffd80 00000002

EXT4-fs error (device sda1): ext4_find_entry: ffffffe2 8520fd20

NIP [c1502630] wm_dumper_fops_ioctl+0x2dc/0x3c8 [wmdumper_module]

LR [c15026f8] wm_dumper_fops_ioctl+0x3a4/0x3c8 [wmdumper_module]

Call Trace:

STACK MAGIC 0x57ac6e9d

[8520fd20] [c15026f8] wm_dumper_fops_ioctl+0x3a4/0x3c8 [wmdumper_module] (unreliable)

[8520fe70] [4011f4c0] vfs_ioctl+0xbc/0xec

[8520fe90] [4011f6f8] do_vfs_ioctl+0x94/0x774

[8520ff00] [4011fe98] sys_ioctl+0xc0/0x12c

[8520ff40] [40011e64] ret_from_syscall+0x0/0x3c

Instruction dump:

9002024c 3b093bb4 7f03c378 38800002 38a00000 4800121d 3800f000 7f830040

7c7e1b78 419d00b4 2f9e0000 419e0090 <813e0010> 8009000c 2f800000 419e0074

last sysfs file: /sys/bus/usb/drivers/hub/unbind

PowerPC Book-E Watchdog Shutdown soft timer

panic_dump_notifier nb=c1554aa4 a=1

[wm_dump_write]: WMD METADATA SECTION IS CORRUPTED. FAILING WRITE

[wm_dump_write]: Stored cksum = 0x16c0388f calculated cksum = 0x8fd5a6c1

[wm_dump_write]: WMD METADATA SECTION IS CORRUPTED. FAILING WRITE

[wm_dump_write]: Stored cksum = 0x16c0388f calculated cksum = 0x8fd5a6c1

PD Start

[flash_or_ata_open_wrapper]: Dumper is writable

[panic_dump_save]: DOOPEN succeeded

PowerPC Book-E Watchdog Shutdown soft timer

panic_dump_save: Saving DIE...

[panic_dump_save]: collecting panicdump

[wm_dump_write]: WMD METADATA SECTION IS CORRUPTED. FAILING WRITE

[wm_dump_write]: Stored cksum = 0x16c0388f calculated cksum = 0x8fd5a6c1

[flash_or_ata_write_wrapper]: write rc = -1

flash_dump_write()=-1, buf=8520fae0, size=0x64

[panic_dump_meta_header]: Dumping meta header failed.

panic_dump_save: Dumping OOM_DUMP...

OOM_DUMP

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Filler write failed.

[panic_dump_write_block]: Header write failed.

panic_dump_save: Dumping reboot_reason...

reboot_reason

set_reboot_reason reason=Software Fault:Kernel Panic

flush reboot_reason reason=Software Fault:Kernel Panic

panic_dump_save: Dumping PLATFORM...

PLATFORM

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Header write failed.

panic_dump_save: Dumping MLT...

MLT

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Filler write failed.

[panic_dump_write_block]: Header write failed.

panic_dump_save: Dumping PD_MISC...

PD_MISC

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Header write failed.

panic_dump_save: Dumping CONSOLE_LOG...

CONSOLE_LOG

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Filler write failed.

[panic_dump_write_block]: Header write failed.

panic_dump_save: Dumping KERNEL_STACK_DUMP...

KERNEL_STACK_DUMP

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Header write failed.

panic_dump_save: Dumping PDTRACE...

PDTRACE

Start WM tracedump

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Header write failed.

End WM tracedump

panic_dump_save: Dumping PANIC_DUMP_LOG...

PANIC_DUMP_LOG

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Header write failed.

[panic_dump_write_block]: Buffer write failed.

[panic_dump_write_block]: Filler write failed.

[panic_dump_write_block]: Header write failed.

[panic_dump_save]: dump the trailer

[panic_dump_write_block]: Header write failed.

panic_dump_save: Panic dump completed

Dump Started at: 00000000e7639896

Dump Ended at: 00000000e78c2210

Dump Time Taken (in 100MHz) = 000000000028897a

[panic_dump_save]: Panic dump completed

hv restart

[0] restart_guest_remap: self is calling remap_restart_unc due to: hcall_partition_restart_ha.

[0] loading binary image from 0x79fff000 to 0x3000000

[0] Loading uImage from 0x78000000 to 0

[0] branching to guest p1-linux, 2 cpus

HV> this is quiet!

end of DRAM 4294967296 memstart_addr0 total_lowmem 4294967296

SLUB: dfree enabled

PRIMING SLUB: main caches

SLUB: export __kmalloc at 0x401068c0 changed to 0x40106c80

SLUB: export vmalloc at 0x400f55a8 changed to 0x400f535c

SLUB: export vfree at 0x400f4748 changed to 0x400f4678

network namespace NR (VRF) started

mdio_bus mdio: /devices/fman0/mdio@f1000/p4080ds-xmdio1 has invalid PHY address

mmod_sysctl_inited: 1

Fman microcode 51 45 46

FMAN microcode UC size 0x1b64

default MII is 0xc10a8000 for tsec0

default MII is 0xc10b0000 for tsec0

CastorT i2c unlock, ret=-2

Uboot wdt counter value: 0

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

[1] restart_guest_remap: self is calling remap_restart_unc due to: hcall_partition_restart_ha.

[0] loading binary image from 0x79fff000 to 0x3000000

[0] Loading uImage from 0x78000000 to 0

[0] branching to guest p1-linux, 2 cpus

HV> this is quiet!

end of DRAM 4294967296 memstart_addr0 total_lowmem 4294967296

SLUB: dfree enabled

PRIMING SLUB: main caches

SLUB: export __kmalloc at 0x401068c0 changed to 0x40106c80

SLUB: export vmalloc at 0x400f55a8 changed to 0x400f535c

SLUB: export vfree at 0x400f4748 changed to 0x400f4678

network namespace NR (VRF) started

mdio_bus mdio: /devices/fman0/mdio@f1000/p4080ds-xmdio1 has invalid PHY address

mmod_sysctl_inited: 1

Fman microcode 51 45 46

FMAN microcode UC size 0x1b64

default MII is 0xc10a8000 for tsec0

default MII is 0xc10b0000 for tsec0

Uboot wdt counter value: 0

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

[1] restart_guest_remap: self is calling remap_restart_unc due to: hcall_partition_restart_ha.

[0] loading binary image from 0x79fff000 to 0x3000000

[0] Loading uImage from 0x78000000 to 0

[0] branching to guest p1-linux, 2 cpus

HV> this is quiet!

end of DRAM 4294967296 memstart_addr0 total_lowmem 4294967296

SLUB: dfree enabled

PRIMING SLUB: main caches

SLUB: export __kmalloc at 0x401068c0 changed to 0x40106c80

SLUB: export vmalloc at 0x400f55a8 changed to 0x400f535c

RE: VDX6740 Booting Problem

Yulia_Abitbul — Thu, 09 Aug 2018 19:02:00 GMT

"Unable to handle kernel paging request for data at address 0xfffffff2Faulting instruction address: 0xc1502630

Oops taken on: 2018-08-09 at 14:22:06

Oops: Kernel access of bad area, sig: 11 [#1]"

That could be hardware failure, we need to check core_files to be sure.

Does it happen only once?

it is better to open a case to TAC team

RE: VDX6740 Booting Problem

Michael_Andreas — Thu, 09 Aug 2018 19:41:00 GMT

what version you are running on the 6740

RE: VDX6740 Booting Problem

Steffen_Schwade — Fri, 10 Aug 2018 14:00:00 GMT

please change the boot partition to SDA1

topic RE: VDX6740 Booting Problem in Data Center (VDX)

VDX6740 Booting Problem

RE: VDX6740 Booting Problem

RE: VDX6740 Booting Problem

RE: VDX6740 Booting Problem