From: Philippe Gerum <rpm@xenomai.org>
To: ivan@rtxi.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>, xenomai@lists.linux.dev
Subject: Re: Troubleshooting x86_64 evl bootup
Date: Mon, 22 Jan 2024 14:43:07 +0100 [thread overview]
Message-ID: <87plxtfper.fsf@xenomai.org> (raw)
In-Reply-To: <ce6d6d1504bb7d589daa14d03fd81d76@rtxi.org>
ivan@rtxi.org writes:
> Hello,
>
> On 2024-01-18 01:51, Jan Kiszka wrote:
>> Hi,
>> On 18.01.24 00:22, ivan@rtxi.org wrote:
>>> On 2024-01-04 13:34, ivan@rtxi.org wrote:
>>> Hello everyone,
>>> I tried building and installing with a newer kernel version
>>> (v6.6.y-evl-rebase) and i get the same error during bootup. This time
>>> however, there is an additional message:
>>> clocksource: Switched to clocksource tsc
>>> After which it hangs for a minute then the same output previously
>>> described is printed. Am I doing something wrong? What additional
>>> information do you need?
>>>
>> Yes, kernel config, to begin with. A complete boot log would also be
>> nice (catch via UART, please).
>
> Attached is the kernel config for the build. Unfortunately I don't
> have a
> way to capture early printk logs through UART, but I will attempt
> other ways.
>
>> There is now a demo image, also for x86, generated via
>> xenomai-images
>> (currently only in 'next'). That config ([1] + [2]) may be lacking some
>> bits you need driver-wise, but maybe it's worth to check and try if
>> that
>> one makes any differences.
>
> I will try this as well and let you know if anything changes.
>
>> Do you see this boot issue only on the Phenom hardware or also on
>> others?
>>
>
> There are a few our old machines that show similar issues:
> 1. Intel Xeon w3680 (Used to have XENOMAI+IPIPE)
> 2. Intel Core 2 Duo (No xenomai/testing laptop)
>
I successfully booted 6.6-evl on the legacy hardware below, so there is
hope:
https://ark.intel.com/content/www/us/en/ark/products/34687/intel-desktop-board-dq45cb.html
An issue with virtualizing the tick device is indeed very likely, this
would also match the init sequence following the tsc calibration.
You may want to disable EVL entirely, only keeping the interrupt
pipeline enabled along with its basic testsuite at bootup. That would
be:
CONFIG_IRQ_PIPELINE
CONFIG_DEBUG_IRQ_PIPELINE
CONFIG_IRQ_PIPELINE_TORTURE
# CONFIG_EVL
# CONFIG_DOVETAIL
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz
stepping : 6
microcode : 0x60c
cpu MHz : 1600.175
cache size : 3072 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm pti dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknown
bogomips : 5066.78
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz
stepping : 6
microcode : 0x60c
cpu MHz : 1705.682
cache size : 3072 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm pti dtherm
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknown
bogomips : 5066.78
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
--
Philippe.
next prev parent reply other threads:[~2024-01-22 13:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 18:34 Troubleshooting x86_64 evl bootup ivan
2024-01-17 23:22 ` ivan
2024-01-18 6:51 ` Jan Kiszka
2024-01-19 21:06 ` ivan
2024-01-22 13:43 ` Philippe Gerum [this message]
2024-01-22 19:40 ` ivan
2024-01-25 9:41 ` Jan Kiszka
2024-01-25 23:35 ` ivan
2024-01-26 5:50 ` Chen, Hongzhan
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=87plxtfper.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=ivan@rtxi.org \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.