Re: question -- does this look right to you?
Two observations — Not sure what they mean, but they are at least data points:
1) Looking at the system logs of the boot process, there does not seem to be any errors related to this.
Here is the relevant part of the output of “journalctl -b” — along with a bit of context on either side…
> Jan 05 01:17:20 sheeva kernel: Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
> Jan 05 01:17:20 sheeva kernel: console [ttyS0] disabled
> Jan 05 01:17:20 sheeva kernel: f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
> Jan 05 01:17:20 sheeva kernel: console [ttyS0] enabled
> Jan 05 01:17:20 sheeva kernel: nand: device found, Manufacturer ID: 0xec, Chip ID: 0xdc
> Jan 05 01:17:20 sheeva kernel: nand: Samsung NAND 512MiB 3,3V 8-bit
> Jan 05 01:17:20 sheeva kernel: nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
> Jan 05 01:17:20 sheeva kernel: Scanning device for bad blocks
> Jan 05 01:17:20 sheeva kernel: Bad eraseblock 1769 at 0x00000dd20000
> Jan 05 01:17:20 sheeva kernel: 3 ofpart partitions found on MTD device orion_nand
> Jan 05 01:17:20 sheeva kernel: Creating 3 MTD partitions on "orion_nand":
> Jan 05 01:17:20 sheeva kernel: 0x000000000000-0x000000100000 : "u-boot"
> Jan 05 01:17:20 sheeva kernel: 0x000000100000-0x000000500000 : "uImage"
> Jan 05 01:17:20 sheeva kernel: 0x000000500000-0x000020000000 : "root"
> Jan 05 01:17:20 sheeva kernel: mousedev: PS/2 mouse device common for all mice
> Jan 05 01:17:20 sheeva kernel: rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
> Jan 05 01:17:20 sheeva kernel: i2c /dev entries driver
> Jan 05 01:17:20 sheeva kernel: ledtrig-cpu: registered to indicate activity on CPUs
Except for the one mention of a bad erase block, I don’t see any errors. Though I don’t have any information to say whether the addresses on “orion_nand” are reasonable…
2) While looking at the journal log, I tried running “fw_printenv” to see if there were any error messages that might give us a clue. There were none. The log was silent for the period of several minutes before and after.
Enjoy!
Rick
Reply to: