FOG - boot to FOS - rcu_sched self-detected stall on CPU
-
It’s the fact that it doesn’t do anything but displaying the message over and over again, so it does prevent functionality.
I have found references online to a BIOS setting named AMD C1E, but this is an Intel board, so that might not be the solution; maybe there is an equivalent to it…
However, this message should not stall the device I’d assume based on your reply?
-
@abos_systemax I don’t, I’m just asking a question.
Maybe try enabling/disabling VTx? I’m grasping at straws though.
I suspect, this also happens under full registration?
-
@Tom-Elliott
It does indeed stall in the Full registration as well.
Enableling VT/VTd doesnt resolve the issue -
Do you have another of the same type of system? Just wanting to know if this is a one off case, or if all systems of the same type have the same problem.
-
I ask this because:
https://www.kernel.org/doc/Documentation/RCU/stallwarn.txt -
@Tom-Elliott
I was trying to understand that document when I found it on google, but am unfamilair with all the abbreviations used, I am also a ‘transitioner’ from Windows to Linux, so it isn’t my forté yet.I have more devices of the kind, will test as soon as I receive the other from our warehouse
-
@Tom-Elliott it does appear to be model related because the other device also isn’t able to boot (with the same rcu_sched messages)
-
Can you try changing the kernel out for one of the 4.6 kernels? 4.7 I added a bunch more “stuff” which may have included RCU_Scheduling. 4.6, I’m pretty certain, did not have the “extras” and may help you out here.
-
@Tom-Elliott both 4.6.4 and 4.5.0 give the same error as the 4.8.1 bzImage32s
e1: i even went as far as downgrading to 3.0.1, but that one results in a blinking cursor on the top left
e2: as does 4.1.0e3: 4.2.0 is the first kernel to display the rcu_sched error apparently
-
@Tom-Elliott
ok, so as soon as I disable Hyper-treading (which makes ipxe monstrously slow btw), I still receive the Informational error, but immediatly after that I receive an rcu_sched kthread starved for xxxxxx jiffies! (where xxxx is a number)
_RCU_GP_WAIT_FQS(3) -> state=0x1 (and the following message is state=0x0) -
@abos_systemax If you re-up to the current kernel and set the log level down (from FOG Configuration->FOG Settings->FOG Boot Settings->FOG_KERNEL_LOGLEVEL) I imagine you will see less of these messages?
-
@Tom-Elliott setting it to 0 gives me the blinking cursor, 1 as well
bumping it up to Debug and log level 7, logs until PCI device initialisation before the RCU informationals appear and I then receive a task dump for CPU 0bumping it back down to level 4 doesn’t show less messages, so apparently Log level 7 is the same as log level 4 with Kernel_debug?
btw there is a small typo in the helptext for loglevel (the instead of they)
-
@Tom-Elliott There isn’t a firmware update available for these machines either. It’s on 1.22 and Lenovo’s latest release is 1.22
-
I can also confirm that other brands of Linux are able too boot.
-
as a matter of debugging, I tried booting to UEFI…
Then I receive the iPXE error 0x7f048283, which is - funnily enough - the same error I had yesterday on a Lenovo M700 which wás able to boot on Legacy -
@abos_systemax Loglevel is independent of the “Kernel Debug”
Kernel Debug will turn on all debug messages. Loglevel will automatically be set to full for the kernel debug regardless of what you set the loglevel to.
I doubt it’s firmware related. The messages, in and of themselves is fine.
Is this booting bzImage or bzImage32?
Is the system in UEFI or Legacy?
-
@Tom-Elliott the device displays the INFOrmational; when in Legacy (and booting bzImage32), but displays the 0x7f048283 when in UEFI
If i force the bzImage on legacy then … =it works= -
@abos_systemax Erm, why is it booting bzImage32 for legacy but bzImage for uefi?
32 is only for 32 bit requests.
-
@Tom-Elliott I don’t know why it boots to bz32… it does apparently…
I assumed that it used bzImage for UEFI because UEFI doesn’t really support x32?however, I retrieved the boot command from the boot.php and forced the boot.php to present it to this machine with bzImage instead of bzImage32 and now it apparently seems to work…
Somehow it doesn’t give it’s archtype correctly?
===
If I drop to Shelland check the buildarch, then it displays i386.
Could this be my DHCP server that is confused? -
This is my DHCP config:
option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2 = unsigned integer 16; option PXE.mtftp-sport code 3 = unsigned integer 16; option PXE.mtftp-tmout code 4 = unsigned integer 8; option PXE.mtftp-delay code 5 = unsigned integer 8; option arch code 93 = unsigned integer 16; # RFC4578 authoritative; allow unknown-clients; option broadcast-address 192.168.71.255; option subnet-mask 255.255.252.0; option routers 192.168.68.1; ddns-update-style none; option domain-name "local"; option domain-name-servers 192.168.68.11, 8.8.8.8; default-lease-time 600; max-lease-time 7200; log-facility local7; # LAN subnet 192.168.68.0 netmask 255.255.252.0 { max-lease-time 14400; default-lease-time 14400; allow unknown-clients; next-server 192.168.68.13; range 192.168.68.30 192.168.71.200; } class "pxeclient" { match if substring (option vendor-class-identifier, 0, 9) = "PXEClient"; if substring (option vendor-class-identifier, 15, 5) = "00000" { # BIOS client filename "undionly.kpxe"; } elsif substring (option vendor-class-identifier, 15, 5) = "00006" { # EFI client 32 bit filename "ipxe32.efi"; } else { # default to EFI 64 bit filename "ipxe.efi"; } }The config states the following:
Chip: undionly
filename: undionly.kpxe
buildarch: i386
platform: pcbios
