| Electronics > Repair |
| Tektronix DPO 4104 kernel panic |
| << < (6/10) > >> |
| adrianh:
Can you please post/attach the *entire* log? |
| MarkF3837:
Here ya go: U-Boot 1.1.4 (Jan 8 2007 - 11:12:14) Tektronix, Inc. V1.06 CPU: AMCC PowerPC 440EP Rev. B at 333.333 MHz (PLB=133, OPB=66, EBC=66 MHz) I2C boot EEPROM enabled Internal PCI arbiter enabled, PCI async ext clock used 32 kB I-Cache 32 kB D-Cache Board: Tektronix Route66 IBM 440EP Main Board VCO: 666 MHz CPU: 333 MHz PLB: 133 MHz OPB: 66 MHz EPB: 66 MHz I2C: ready DRAM: 128 MB FLASH: 64.5 MB PCI: Bus Dev VenId DevId Class Int 00 13 10b5 9056 0680 18 00 15 1002 4c59 0300 17 DISP: Type 1 In: serial Out: serial Err: serial Enter password - autobooting in 3 seconds ## Booting image at f0000000 ... Image Name: Linux-2.4.20_mvl31-440ep_eval Image Type: PowerPC Linux Multi-File Image (gzip compressed) Data Size: 1441010 Bytes = 1.4 MB Load Address: 00000000 Entry Point: 00000000 Contents: Image 0: 1033953 Bytes = 1009.7 kB Image 1: 407042 Bytes = 397.5 kB Verifying Checksum ... OK Uncompressing Multi-File Image ... OK cmdline is console=ttyS0,9600 quiet bigphysarea=519 panic=2 root=/dev/mtdblock7 rw mem=131072k Loading Ramdisk to 07f2b000, end 07f8e602 ... OK Checking for firmware update... Mounted /dev/sda1 as /mnt/sda1 Checking md5sum... fwUpdate.sh: OK md5sum check passed, continuing... Firmware update script found in image. Executing script... Firmware platform check passed. This is a new kernel. This instrument is a DPO4xxx. No firmware version file found in flash, performing update - kernel.img found. - filesystem.tar.gz found. - bootloader.img found. - comparing versions... V1.06 V1.06 installed bootloader is equal or newer. Skipping. - splash.img found. - splashmso.img found. - route66_fp.s19 found. Front panel version file contents - Route66 FP 0 27 3 - fwEnvUpdate.sh found. Update files were found. Checking file integrity, please wait... Running: /usr/bin/md5sum -c < md5sum.txt bootloader.img: OK dispBmp: OK filesystem.tar.gz: OK firmware_complete4.bmp: OK firmware_update4.bmp: OK fwEnvUpdate.sh: OK fwUpdate.sh: OK getPlatform: OK kernel.img: OK nv.jffs2: OK ppver.txt: OK radeonRegs.ppc: OK radeonVideoCap.scr: OK root.jffs2: OK route66_fp.s19: OK route66_fp_version.txt: OK splash.img: OK splashmso.img: OK uBootExtract: OK Using /usr/share/modules/radeonfb.o md5sum check passed for all files, continuing... Performing update in 15 seconds... (The front panel will be updated during the next powerup.) Flashing splash.img... DO NOT TURN OFF THE SYSTEM!!!! - Erasing flash; this may take a while... Erasing 128 Kibyte @ e0000 -- 87 % complete. - Writing to flash; this may take a while... Finished updating splash screen. Flashing kernel.img... DO NOT TURN OFF THE SYSTEM!!!! - Erasing flash; this may take a while... Erasing 128 Kibyte @ 160000 -- 91 % complete. - Writing to flash; this may take a while... Finished updating kernel. Flashing kernel.img into backup partition... - Erasing flash; this may take a while... Erasing 128 Kibyte @ 160000 -- 91 % complete. - Writing to flash; this may take a while... Finished updating backup kernel. Updating filesystem... DO NOT TURN OFF THE SYSTEM!!!! Extracting the contents of /usr/local/perm... - Erasing flash... this may take a while. Erasing 128 Kibyte @ 1de0000 -- 99 % complete. mount: Mounting /dev/mtdblock7 on /mnt/rootfs failed: Invalid argument - Writing to flash; this may take a while... tar: Cannot create directory `./usr/local': No space left on device tar: Cannot create directory `./usr/local': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: Cannot create directory `./usr/local': No space left on device tar: Cannot create directory `./usr/local/': No space left on device tar: ./usr/local/bin/scopeApp.ppcep: No such file or directory An error occured while updating the root filesystem! |
| adrianh:
Well, your issue is certainly different than the two that have been fixed. I suppose bad dram could result in the "no space left on device" error... However the "invalid argument" warning is a little disturbing. I wish I understood more how flash updating works! (Does anyone want to capture a log of a successful fw update??) Bad dram? maybe. Bad flash chip?? (is the flash mounted as a filesystem after erasing and before writing - probably). I can imagine a corrupt bit in a ram filesystem that happened to make an inode disappear... Again, it will cost you only $20 in dram and some serious smd soldering, but it sure would be nice to have a more solid theory. Do you know where the flash chip is? Might be easier to try replacing that first. |
| MarkF3837:
Good idea: there's a single flash chip (AM29LV040B-90JC) in a 32-PLCC. Easy to rework. There are four mystery BGAs that appear to be on the same bus; they don't matter, because I don't have BGA rework equipment. Where does the boot code reside? If it is in this part, then I'll need to get a programmer. |
| JohnPi:
Can someone please post a photo of where the serial port is on these scopes ? We have about 4 of these in our lab that fail to boot, and I may try exchange DRAMs between them... |
| Navigation |
| Message Index |
| Next page |
| Previous page |