Bug 11035

Summary:	Pentium N3700 crash
Product:	[Runtime] General Runtime	Reporter:	smartdu <smartdu>
Component:	General Runtime	Assignee:	smartdu <smartdu>
Status:	RESOLVED INVALID	QA Contact:
Severity:	critical
Priority:	Medium	CC:	ciyingjue, sgw
Version:	2.2.1
Target Milestone:	2.2.2
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

Description smartdu 2017-02-09 01:24:40 UTC

i use morty branch to build Pentium N3700 platform，About 5 hours will be crash

i run gst-launch-1.0 rtspsrc location=rtsp://192.168.64.37:554/mpeg4 latency=0 ! decodebin ! autovideosink 
or
yami' simpleplayer xxx.h264

Comment 1 Saul Wold 2017-02-09 19:22:32 UTC

Can you please provide some additional details about both the platform your are using and the actual failure. Saying it crashes after 5 hours is not very useful.

Do you have a Kernel OOP? or Segfault?

Do you have a specific mpeg or h264 file that causes the failure or any?

Comment 2 jmdvirus 2017-02-15 09:15:12 UTC

I'm glad you can answer me.

I'm sorry, we have no more information.

Usb port for keyboard and mouse has no response when system dead.
Display has no response too. I can do nothing more.

I use tail -f /var/log/messages, but no output when system dead.
The network port light was blinking, but I can't connect it though network (ssh, of cause it was ok before).

I guess hardware has some problem, but the manufacturer of the device give nothing.

Is there some special method to debug this?

Comment 3 Saul Wold 2017-02-16 16:15:05 UTC

Sorry without more details about the device, it's very hard.  Can you test/confirm this issue on a NUC or similar public device with an N3700?  

What MACHINE target are you building for?  Are you building with meta-intel?

There was some recent changes to both the morty and the meta-intel/morty branch.

Any additional build information might be helpful

Comment 4 Saul Wold 2017-04-13 18:54:28 UTC

As we have not gotten any additional information about this issue concerning this issue, we are going to close it, if you can provide the additional details then please re-open this bug.