Trung, The LAVA environment knows about those paths - I'd look into whether the prompts you get on logging in are the ones that LAVA is telling you that it is expecting? Robert "Trung. Huynh"

Hi Daniel, Robert, We got into test section already, but have no idea why it attempts to execute the thing non-exist at all: # /lava-237/bin/lava-test-runner /lava-237/0 as you can see our error log

Hi, (this is a long mail) in order to understand the ideas about the future of the CIP Testing project, let me enumerate the basic requirements that led CIP to pursue the current strategy, now under

Hi, (this i a long mail) As the below summary shows with more or less accuracy, the steps taken on the CIP Testing Project front has been: 1 Discuss the testing strategy. (completed) 2 Identify as

Hi, I just uploaded the links to the slides and video of the talk delivered by Ben H. and myself at ELCE 2017. Check them out:

Hello Sean, Following on from our conversations at ELC-E I wanted to reboot this thread. Have you had a chance to look into this topic again? Did you create the gitlab project in the end? What were

From: Sebastian Reichel <sebastian.reichel@...> commit 2501b015313fe2fa40ed11fa4dd1748e09b7c773 upstream. On some systems its desirable to have watchdog reboot the system when it does

From: Guenter Roeck <linux@...> commit 3c10bbde10fe4dca52726e246cefa6b0a1dfbd3e upstream. WDOG_HW_RUNNING indicates that the hardware watchdog is running while the watchdog device is

From: Wei Yongjun <yongjun_wei@...> commit 138913cb632be12344982e54ccd12f6f15971bf upstream. Fix the error handling paths of watchdog_dev_init(). Signed-off-by: Wei Yongjun

From: Rasmus Villemoes <rasmus.villemoes@...> commit 3fbfe9264756d3fd99a9210345016c94ec4ada73 upstream. If the driver indicates that the watchdog is running, the framework should feed it until

From: Pratyush Anand <panand@...> commit 1894cad9bf2c10359b2b7a0c00e564698f712751 upstream. When max_hw_heartbeat_ms has a none zero value, max_timeout is not used. So it's value can be 0. In

From: Guenter Roeck <linux@...> commit e1f30282a1d3d0c75d5a08e47c6ac1563065be52 upstream. lockdep reports the following circular locking

From: Guenter Roeck <linux@...> commit 11d7aba9ceb726d86aaaca3eb5f7d79de38989c5 upstream. The watchdog infrastructure now supports handling watchdog keepalive if the watchdog is running

From: Guenter Roeck <linux@...> commit d0684c8a9354953efdea214b437445c00743cf49 upstream. Not all hardware watchdogs can be stopped. The driver for such watchdogs would typically only set

From: Guenter Roeck <linux@...> commit ee142889e32f564f9b5e57b68b06693ec5473074 upstream. The WDOG_HW_RUNNING flag is expected to be set by watchdog drivers if the hardware watchdog is

From: Guenter Roeck <linux@...> commit 664a39236e718f9f03fa73fc01006da9ced04efc upstream. Introduce an optional hardware maximum heartbeat in the watchdog core. The hardware maximum

Hello, This is updated series after Ben's review. >>>>>>>>>> * On 10/25/17 12:43, Ben Hutchings wrote: * On 10/25/17 12:46, Ben Hutchings wrote: <<<<<<<<<<<<< This series contains * backport of

Hi Chris, Daniel, v4.4.55-cip3 was fully tested, including UT,IT,ST. v4.4.69-cip4 , v4.4.75-cip6 also worked with just some simple tests. Best regards, Binh Nguyen

Hi Ben, # I added the fuego mailing list to Cc Thanks for the notes!

Hello Daniel, Apologies for the slow response. Lots of ramblings below, happy to set up a call if it's easier to go through the details. Let me explain... The renesas-rz github website is used to