Doremi IMS1000 - Manual (Page 287)

IMS.OM.002949.DRM Page 287 of 320 Version 1.7
Doremi Labs
17.8.4 Empty ShowPlaylist
17.8.4.1 Description
ShowPlaylist is empty, SM and firmware versions are missing.
17.8.4.2 Identification
If the report was taken while the error was showing, look at 'lspci' in drmreport.txt.
If the report was taken after a reboot, look at 'lspci' in \doremi\log\kreport.log.x (kreport.log being
the previous boot, kreport.log.0 being the boot before, and so on).
Exec. command: 'lspci'
00:00.0 Host bridge: Intel Corporation Device 0709 (rev 08)
...
01:13.0 Multimedia controller: Intel Corporation Device 0706 (rev 01)
01:14.0 Multimedia controller: Intel Corporation Device 0705 (rev 01)
01:15.0 Unassigned class [ff00]: Intel Corporation CE Media Processor SPI Slave (rev 01)
01:16.0 Display controller: Intel Corporation Device 070a
01:1b.0 SD Host controller: Intel Corporation Device 070b
02:00.0 SATA controller: Marvell Technology Group Ltd. Device 9230 (rev 10)
03:00.0 Unassigned class [ff00]: Device 1fd5:0007 (rev 21)
The highlighted line 03:00.0 referencing the device 1fd5:0007 (FPGA) will be missing when this
issue occurs.
When looking at \doremi\log\kern.log (or \doremi\log\kern.log.x if the issue occurred a while
before the report was taken), you should NOT see this message when this issue occurs:
Jun 24 15:55:43 IMS01-SC3 kernel: pci 0000:03:00.0: reg 10: [mem 0xbfd00000-0xbfdfffff]
...
Jun 24 15:56:31 IMS01-SC3 kernel: dolphin 0000:03:00.0: enabling device (0000 -> 0002)
Jun 24 15:56:31 IMS01-SC3 kernel: dolphin 0000:03:00.0: PCI INT A -> GSI 17 (level, low) ->
IRQ 17
Jun 24 15:56:31 IMS01-SC3 kernel: dolphin 0000:03:00.0: setting latency timer to 64
Jun 24 15:56:31 IMS01-SC3 kernel: dolphin 0000:03:00.0: irq 65 for MSI/MSI-X
Jun 24 15:55:55 IMS01-SC3 kernel: Dolphin DEBUG: dolphin_malloc_ex: f0e00000 (4194304
bytes) [23c00000 - 24000000]
17.8.4.3 Solution
The solution for a customer would be to RMA the unit.
17.8.5 Playback Stops
17.8.5.1 Description
Unit stops playing.
17.8.5.2 Identification
When looking at \doremi\log\odetics.log (or \doremi\log\odetics.log.x if the issue occurred a
while before the report has been taken), you should see the following message when this issue
occurs: