218 replies to this topic

[Erik Slagter]

yes, here the same problem with vu ultimo 4k and internal harddisc with normal .ts records.

And where is the dmesg output?

[Erik Slagter]

<dmesg output>

Yes, that is something we can use. I already see both events crashed at exactly the same point in the driver code, if that continues, it may be simple to fix by VU+.

 

Please use an attachment btw, instead of pasting it into the post and make your lines don't get cropped or wrapped around.

[Pike_Bishop]

Hi Erik,

 

 

And where is the dmesg output?

 

sorry you're right, but at the moment many records are running maybe i can post it tomorrow or on weekend.

 

 

regards

Biki3

Edited by Biki3, 22 November 2017 - 20:12.

[sjlouis]

Erik, what do you want? A log file? If yes, how can I get it?

 

If you ask something to Vu+ manufacturers, can you ask them to improve 4x speed? If 2x works well, 4x jumps from picture to picture. it's not fluid, it's jerky.

 

Thank you .

[Erik Slagter]

Explained already several times.

[Pike_Bishop]

Hi,

 

i attach the dmesg output here

 

 

regards

Biki3

Attached Files

•  dmesg.log   41.48KB   5 downloads

[sjlouis]

Don't bother trying to debug this, it has nothing to do with enigma.

 

Do this:

 

- login to the receiver, do dmesg -c and ignore the output.

- trigger the issue

- do dmesg -c again

- you will see lots of output from the kernel, stack traces from a null pointer dereference and the words "OOPS" or "BUG".

 

I other words, driver naughtyness and they have been stopped by the Linux kernel. Only remedy is total reboot.

 

Whenever you see spinners and they don't go away, ALWAYS first check the output of dmesg.

 

 

Crash = no ping, no telnet login, need power cycle = can not be a problem in the image, must he driver or hardware issue

GSOD = post output here

Other weirdness = post output of dmesg here

 

 

I believe I have already asked, in this or another thread, for dmesg output. The dmesg output in this case is the only thing that will be helpful, and it will show a driver crash. I want to collect these and send them to VU+. That is the only think we can do.

I've red again the post and I don't find how to have a logfile and where it is. Perhaps I have to search in the forum.

[Erik Slagter]

Hi,

 

i attach the dmesg output here

 

regards

Biki3

Thanks. It appears to crash exactly at the same spot as the other two crash reports, so that's promising.

[Pike_Bishop]

@sjlous

 

in telnet make;

dmesg > /tmp/dmesg.log 2>&1

when your box hangs then you have on your box under /tmp the file dmesg.log, you can copy it per FTP on your pc and then attach it in a new post here.

 

 

regards

Biki3

Edited by Biki3, 23 November 2017 - 18:50.

[Pike_Bishop]

Hi Erik,

 

 

so that's promising

that sounds good

 

 

regards

Biki3

[sjlouis]

Ok, thank you Biki3. And i get a lot of files with Windows Explorer. It's convenient (for a few little files).

[sjlouis]

I've done the log, I attach it .

 

 dmesg.log   32.71KB   3 downloads

Edited by sjlouis, 26 November 2017 - 14:50.

[Erik Slagter]

It looks even more promising, VU+ released a driver update for the Ultimo4k with a rather cryptic comment, but it actually does seem to solve this problem! The new driver is in rc-6.1.

[sjlouis]

Yes!!!

 

Thank you Erik .

[Erik Slagter]

Don't thank me, I didn't report it yet But does it fix the issue?

[sjlouis]

I don't know where I can get this driver. Can you explain please?

 

Thank you .

[Pike_Bishop]

the driver is automatically in image if you flash it - so if you flash the rc-6.1 image from date 26.11.2017 are the drivers from date 22.11.2017 in there

it's nothing to do for you, unless flashing.

 

 

regards

Biki3

Edited by Biki3, 26 November 2017 - 21:00.

[sjlouis]

Ok, I haven't understood. I thought RC-6.1 was the driver name.

 

Thank you .

[Pike_Bishop]

Hi Erik,

 

 

Don't thank me, I didn't report it yet But does it fix the issue?

no it didn't fix the issue.

 

 

regards

Biki3

[sjlouis]

It doesn't work also for me .

 

We have to wait more.