From: wagi@monom.org (Daniel Wagner)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Reviewing 4.4 stable updates
Date: Thu, 17 May 2018 07:35:06 +0200 [thread overview]
Message-ID: <c69d5a4e-251b-3737-dd52-fa38f2565efe@monom.org> (raw)
In-Reply-To: <000301d3ed80$8e0c3d80$aa24b880$@toshiba.co.jp>
Hi Daniel,
>> Just out of curiosity, do you also test the cip-rt kernel with fuego? I
>> got a report that a x86 box has problems to boot with the recent cip-rt
>> kernel. In the early device bring up a NULL pointer is dereferenced
>> (late_resume_init). So far I was not able to reproduce it on my machine.
>>
>> Hence if you test the cip-rt kernel I would be interested to get
>> feedback as well :)
>
> I do test the cip-rt kernel sometimes, but not in an automated way yet (in the end automation requires maintenance and that takes time). With the latest version I didn't have boot problems on x86_64, but I haven't tried on other architectures. I run cyclictest with some load background and got a maximum latency of 125us (only run it for 10 minutes).
Thanks for the feedback. After some more debugging, it looks like the
boot problem is cased by kexec on the test machine. IOW, the test kernel
seems just fine.
Thanks,
Daniel
prev parent reply other threads:[~2018-05-17 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 13:18 [cip-dev] Reviewing 4.4 stable updates Ben Hutchings
2018-04-25 23:52 ` Daniel Sangorrin
2018-04-26 14:30 ` Ben Hutchings
2018-05-15 4:06 ` Daniel Sangorrin
2018-05-15 6:44 ` Daniel Sangorrin
2018-05-15 7:44 ` Agustín Benito Bethencourt
2018-05-15 7:53 ` Daniel Wagner
2018-05-17 1:44 ` Daniel Sangorrin
2018-05-17 5:35 ` Daniel Wagner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c69d5a4e-251b-3737-dd52-fa38f2565efe@monom.org \
--to=wagi@monom.org \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox