Wind River Support Network

HomeDefectsLIN5-19779
Fixed

LIN5-19779 : WR Linux 5 does not work good together with Simics, timeouts, hanging...

Created: Nov 28, 2014    Updated: Dec 19, 2017
Resolved Date: Dec 11, 2014
Found In Version: 5.0.1.10,5.0.1.20
Fix Version: 5.0.1.22
Severity: Severe
Applicable for: Wind River Linux 5
Component/s: BSP

Description

Hi !

The customer has had problems with systems running on simics with WR Linux.
In the large system setups that Ericsson uses it is important to have a configuration
that gives best possible performance.

With some settings of the simics configuration parameter cpu-switch-time they run in to
different timeout and hanging situations during boot. The problems happens when using WR Linux 5
but not with latest versions of WR Linux 6.

The only solution to the problem is to change the simics configuration to a one that gives
a not so good performance.

Some of the customer problems have been possible to reproduce outside the customer environment.

Analyze have been done by Intel engineering team and their opinion is that something is wrong 
on linux side.

Steps to reproduce.
Example login timeout:

Description: In simics it is usual to have an automatic login script. In this failing example
the automatic login fails with a login timeout, it is neither possible to do a manual login. The example uses Wr Linux 5.0.1.10 which is part of the
simics packages.

1. A simics installation is needed, packages 1000, 2086 and 16107.
If you don't know how to do a simics installation, please contact me or some local engineer that have this knowledge.

2. Start simics either in eclipse or outside eclipse, example
without eclipse

$./simics targets/qoriq-t4/t4240qds-wrlinux-multi.simics

3. set cpu-switch-time to 12325
simics> cpu-switch-time 12325

4. Run

simics> run

The system consists of two identical t4240 boards, t4240qds1 and t4240qds2.
The same linux is run on both boards. On one of them the login fails and on
the other one the login is successful.

This TSR is part of a root cause analysis which has a deadline December 10th
I need a complete analyze no later than in the morning December 9th Swedish time. If there are bugs it is not needed to have a ready bugfix at this date. It is only needed to have a complete technical description of what actually happens in the failing case

If questions needs to be asked to Simics development team I will coordinate this. 

There has been a mail thread discussing this where Steve Long has taken part.

regards
Roger

Other Downloads


Live chat
Online