Author Topic: Tektronix DPO 4104 kernel panic  (Read 7722 times)

0 Members and 1 Guest are viewing this topic.

Offline adrianhTopic starter

  • Contributor
  • Posts: 15
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #25 on: January 04, 2022, 01:11:18 am »
Can you please post/attach the *entire* log?
 

Offline MarkF3837

  • Newbie
  • Posts: 7
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #26 on: January 04, 2022, 02:02:30 am »
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!

 

Offline adrianhTopic starter

  • Contributor
  • Posts: 15
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #27 on: January 04, 2022, 03:10:49 am »
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.
 

Offline MarkF3837

  • Newbie
  • Posts: 7
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #28 on: January 04, 2022, 06:23:20 am »
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.
 

Offline JohnPi

  • Regular Contributor
  • *
  • Posts: 159
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #29 on: January 04, 2022, 06:06:02 pm »
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...
 

Offline MarkF3837

  • Newbie
  • Posts: 7
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #30 on: January 05, 2022, 12:48:02 am »
It's on the bottom of my DSP4104. Remove the cover and there is an opening in the Aluminum shield. A 1.27 mm pitch connector has 20 pins. I identified two; see the photo. Signal is 3.3V & 9600 b/s.
 

Offline pcwrangler

  • Regular Contributor
  • *
  • Posts: 73
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #31 on: January 09, 2022, 10:40:03 pm »
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.

1. The bootloader does reside on that AM29LV040B. It is easy to remove/replace but yes you will need a programmer to do anything with it. Read it multiple times with it firmly in the programmer to compare against each other and rule out intermittent errors (indicating bad chip or bad contacts to programmer) and make backups! But first: Your log shows it skipped updating the bootloader because it was "same or newer". Have you tried the "force update" procedure mentioned in the firmware documentation? If you do, make sure you watch and copy the log in the process.
2. What is the full boot log withOUT trying to update the firmware via USB?
3. It is conceivable that the RAM is bad, as Adrian said, and that is causing havoc with the install. If the above doesn't work, I would spend the ~$20 and give it a try.

Good Luck
 

Offline MarkF3837

  • Newbie
  • Posts: 7
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #32 on: February 03, 2022, 02:02:26 am »
Finally had some free time. After replacing flash and RAM, behavior is the same, even after adding "forceinstall.txt" to the USB drive. Could something in the bootloader be corrupted? Has anyone uploaded their flash contents? I could try booting with that code.
 

Offline pcwrangler

  • Regular Contributor
  • *
  • Posts: 73
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #33 on: February 05, 2022, 05:20:12 am »
Finally had some free time. After replacing flash and RAM, behavior is the same, even after adding "forceinstall.txt" to the USB drive. Could something in the bootloader be corrupted? Has anyone uploaded their flash contents? I could try booting with that code.

Did you save the log when you tried the force install?
 

Offline pcwrangler

  • Regular Contributor
  • *
  • Posts: 73
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #34 on: February 05, 2022, 05:01:02 pm »
... Could something in the bootloader be corrupted? Has anyone uploaded their flash contents? I could try booting with that code.

Sent you a PM
 

Offline MarkF3837

  • Newbie
  • Posts: 7
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #35 on: February 07, 2022, 06:50:29 pm »
I flashed a known good copy of boot code. The middle part of the console output was different, but the first part and the (failed) last part are identical to the original. Same thing comparing old/new outputs for a forced update.

I may have to poke at address & mux lines to see if something looks funny. Another (grasping at straws) possibility: What size DDR RAM are in others' 'scopes? Mine has MT46V16M16; this is an early version instrument, and maybe they changed to MT46V32M16?

In the meantime, I'm going to try and track down the noise source in my current 1 GHz 'scope: a TDS784D. At least there are schematics for TDS5xx & TDS6xx families out in the internets.
 

Offline pcwrangler

  • Regular Contributor
  • *
  • Posts: 73
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #36 on: February 07, 2022, 09:12:07 pm »
That's the exact model DRAM my MSO4104 has which were bad so I replaced them. The whole saga is in my original thread below. It might give you ideas when you're ready to revisit your 4104.
https://www.eevblog.com/forum/repair/tek-mso4104-no-boot/

Good luck with the others.
 

Offline mikehank

  • Regular Contributor
  • *
  • Posts: 61
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #37 on: March 15, 2022, 08:20:44 pm »
Replace the CPU memory.  Four gullwing chips near the processor.  Two on either side.
 

Offline analogRF

  • Super Contributor
  • ***
  • Posts: 1021
  • Country: ca
Re: Tektronix DPO 4104 kernel panic
« Reply #38 on: April 06, 2023, 06:47:16 pm »
I hope adrianh and pcwrangler still check this thread and be interested  ;) ;)

I have a DPO4054 which one day just froze and after power cycle it never booted again (stuck at splash screen). All voltages and oscillators are ok and no hot spot on the board out of the ordinary. Here is the boot log I get:
Code: [Select]
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
        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...
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
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
Error programming MIA, USERi stayed low 0x00000000
insmod: init_modScope application starting (normal mode)
---------------------- startScopeApp()Oops: kernel access of bad area, sig: 11
NIP: C00CBA10 XER: 20000000 LR: C003FE20 SP: C06E9E10 REGS: c06e9d60 TRAP: 0800    Tainted: P
MSR: 00009030 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DEAR: CE16CA8C, ESR: 00000000
DEAR: CE16CA8C, ESR: 00000000
TASK = c06e8000[68] 'scopeApp.ppcep' Last syscall: 5
last math c06e8000 last altivec 00000000
GPR00: 00000000 C06E9E10 C06E8000 C01F184C C7DB5540 00000000 C7DB55A4 C7E98000
GPR08: C01EB430 C01F1834 C7DB54C0 00000050 28004888 1175BF40 0FF897D0 0FF89F8C
GPR16: 0FF89FB4 0FF89760 12B379E0 12B37940 00009032 C06E9F40 00000000 C00029DC
GPR24: C00026A0 FFFFFFED C719FDC0 C01F0000 C7DB5540 C01F0000 000000F0 CE16CA8C
Call backtrace:
C7EAF008 C003FE20 C003E774 C003E820 C003EA60 C000272C 0FF78720
10CB1D1C 10CB19C0 10CB45EC 10CB5310 10CB4F74 10CB6AAC 10CC5104
10CC5D64
 running Init code ----------------------
versionBuildFWVersionString(): TimestampString: 25-Apr-12  11:13
                               VersionFIRMWAREVERSIONversion: v2.68
                               Major ver num: 2 Minor ver num: 68
mv: canÞù

I also entered the U-Boot and tried the memory test (mtest). By default it checks from 0x00400000 to 0x07000000 which passes with no error. I also tried 'mtest' from 0x00100000 to 0x07f00000 and no errors. However, I do get error at 0x07f8efb8 when I try to test RAM from 0x07f00000 to 0x07ff0000:
Code: [Select]
=> mtest 07f00000 07ff0000

Testing 07f00000 ... 07ff0000:
Iteration:      1

FAILURE (read/write) @ 0x07f8efb8: expected 0x00023bef, actual 0x07f8efd0)

However, I tried that on a DPO4104 with the same FW version and I get exactly the same error at that address with the same value. So I suppose this should not mean the RAM is bad.

I have forced firmware update twice with 2.68 and it all goes through with no problem and after restart I get the same error.

Any idea what I should be looking at?

What is Mia? Is that the Altera Stratix FPGA? or the PCI bridge chip? Or the ATI mobility Radeon?

any help is highly appreciated....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
 

Offline adrianhTopic starter

  • Contributor
  • Posts: 15
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #39 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.
 
The following users thanked this post: analogRF

Offline analogRF

  • Super Contributor
  • ***
  • Posts: 1021
  • Country: ca
Re: Tektronix DPO 4104 kernel panic
« Reply #40 on: April 06, 2023, 07:07:34 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.

can you decipher anything from the kernel messages? it seems it must have something to do with MIA whatever that is.
 

Offline adrianhTopic starter

  • Contributor
  • Posts: 15
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #41 on: April 06, 2023, 08:29:12 pm »
can you decipher anything from the kernel messages? it seems it must have something to do with MIA whatever that is.

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.
 

Offline pcwrangler

  • Regular Contributor
  • *
  • Posts: 73
  • Country: us
Re: Tektronix DPO 4104 kernel panic
« Reply #42 on: April 09, 2023, 03:39:48 am »
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: [Select]
insmod: init_modScope application starting (normal mode)
---------------------- startScopeApp()Oops: kernel access of bad area, sig: 11
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.
 

Offline boyddotee

  • Contributor
  • Posts: 27
  • Country: gb
Re: Tektronix DPO 4104 kernel panic
« Reply #43 on: May 10, 2023, 12:22:41 pm »
can you decipher anything from the kernel messages? it seems it must have something to do with MIA whatever that is.

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.

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.
 

Offline chaos_chris

  • Newbie
  • Posts: 1
  • Country: de
Re: Tektronix DPO 4104 kernel panic
« Reply #44 on: September 30, 2024, 12:53:36 pm »
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
 
« Last Edit: September 30, 2024, 12:59:03 pm by chaos_chris »
 

Offline squadchannel

  • Frequent Contributor
  • **
  • Posts: 423
  • Country: jp
  • deepl translate user
Re: Tektronix DPO 4104 kernel panic
« Reply #45 on: September 30, 2024, 01:25:51 pm »
guessing from the logs quoted in this reply, stuck on demux initialization?
Could be a hardware issue.

https://www.eevblog.com/forum/testgear/possible-ticking-time-bomb-in-tek-dpo3000-and-mso3000-series-of-scopes-dpo4000/msg3539784/#msg3539784
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf