Electronics > Repair
Tektronix DPO 4104 kernel panic
analogRF:
--- Quote from: adrianh on April 06, 2023, 07:03:18 pm ---> I tend to believe it is still a DRAM issue but I think if it was DRAM it should have stopped much earlier in the process
All it takes is one bit to bad in DRAM. It could end up being in the stack, the heap, the BSS.. My point is that it can trip up the kernel/user-space anywhere at anytime.
Given that the DRAM repair has fixed at least two problems that didn't have the same signature, I'd say spend the $20-30 and start replacing dram.
What I do worry about still with my scope is bad DRAM that is in use by a user-space process. If it ends up in a data processing area, the error will not be caught. So the reality is that we should all replace ALL of our DRAM.
--- End quote ---
can you decipher anything from the kernel messages? it seems it must have something to do with MIA whatever that is.
adrianh:
--- Quote from: analogRF on April 06, 2023, 07:07:34 pm ---can you decipher anything from the kernel messages? it seems it must have something to do with MIA whatever that is.
--- End quote ---
Sorry cannot help you there.
Could you please share your setup to get into u-boot? I was only ever able to get output from the serial port. I would be neat to interact with the bootloader and try the memtest.
pcwrangler:
From what I can see in your bootlog, it appears like another DRAM related issue to me. Suddenly stopping with garbage output coupled with the "bad area" error not too far above that...
--- Code: ---insmod: init_modScope application starting (normal mode)
---------------------- startScopeApp()Oops: kernel access of bad area, sig: 11
--- End code ---
Mine had a similar problem early in the boot process, stopping suddenly with no feedback. I think adrianh might be right, replace the DRAM chips. The low cost is well worth the try. Either way, please update this thread so we can keep track of these errors and their solutions.
As far as the MIA, no idea. The good news is the system caught the errors and reported it in the bootlog so it wasn't fatal (at least not to that point). Unless a full DRAM swap doesn't fix your issue, I wouldn't go down that rabbit hole.
boyddotee:
--- Quote from: adrianh on April 06, 2023, 08:29:12 pm ---
--- Quote from: analogRF on April 06, 2023, 07:07:34 pm ---can you decipher anything from the kernel messages? it seems it must have something to do with MIA whatever that is.
--- End quote ---
Sorry cannot help you there.
Could you please share your setup to get into u-boot? I was only ever able to get output from the serial port. I would be neat to interact with the bootloader and try the memtest.
--- End quote ---
For uboot, there is a short window of "hit any key", also works by sending a character via serial.
That short window may have been changed by the developer so it may take a few try's.
chaos_chris:
Hi all,
DPO4104 not leaving boot splash screen,
by reading the serial port (thank you!) I get as attached.
Does this sound familiar to anyone here?
Thank you very much in advance!
______________________________________________________
U-Boot 1.1.4 (Jan 8 2007 - 11:12:14) Tektronix, Inc. V1.06
CPU: AMCC PowerPC 440EP Rev. C 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
<9>VCO: 666 MHz
<9>CPU: 333 MHz
<9>PLB: 133 MHz
<9>OPB: 66 MHz
<9>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...
No USB mass storage devices found to update from.
Linux 2.4.20_mvl31-440ep_eval V 1.15 Tektronix Route66 Tue Jun 22 15:19:50 PDT 2010
stat of /var/log/dmesg failed: No such file or directory
rm: cannot remove '/var/run/*': No such file or directory
Warning: loading NiDKEng-1.6 will taint the kernel: non-GPL license - Proprietary
See http://www.tux.org/lkml/#export-tainted for information about tainted modules
Warning: loading NiDUsb-1.6 will taint the kernel: non-GPL license - Proprietary
See http://www.tux.org/lkml/#export-tainted for information about tainted modules
Warning: loading tek will taint the kernel: non-GPL license - Proprietary
See http://www.tux.org/lkml/#export-tainted for information about tainted modules
Scope application starting (normal mode)
---------------------- startScopeApp() running Init code ----------------------
versionBuildFWVersionString(): TimestampString: 25-Apr-12 11:13
VersionFIRMWAREVERSIONversion: v2.68
Major ver num: 2 Minor ver num: 68
Initializing Mia[0]<
<9>PA Bus error. Skipping initialization of devices on PA bus
Initializing Ibm440[0]
Initializing HFD204ADC[1]
Initializing HFD204ADC[0]
Model id: 0x03
Initializing Ltc1658Dac[0]
Board id: 0x01
Initializing M859[3]
Initializing M859[2]
Initializing M859[1]
Initializing M859[0]
HFD144[0] ID_REG = 0x00001440
HFD144[1] ID_REG = 0x00001440
HFD144[2] ID_REG = 0x00001440
HFD144[3] ID_REG = 0x00001440
Initializing Hfd144[0]
Initializing Hfd144[1]
Initializing Hfd144[2]
Initializing Hfd144[3]
<9>Open Max5362 successful.
Initializing Max5362[0]
Initializing Ltc1661Dac[1]
Initializing Ltc1661Dac[0]
hwInit failed
Init ADT7468 and locking.
Factory Checksum: Stored: 41143, Calculated: 41143 - OK
Spc CheckSum: stored: 37628 calculated: 37628 - OK
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version