-
Notifications
You must be signed in to change notification settings - Fork 1
Cst jack check for extended apic #210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
1564516
d26fbcb
27bef90
ec21db8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| #!/bin/bash | ||
|
|
||
| #set -ue # Fail with an error code if there's any sub-command/variable error | ||
|
|
||
| DESCRIPTION="Check that extended APIC is available for assigning IRQs" | ||
| # script type is single, parallel, sequential, or parallel-compare-backends | ||
| SCRIPT_TYPE="parallel" | ||
| JIRA_REFERENCE="" | ||
| WTA_REFERENCE="" | ||
| KB_REFERENCE="" | ||
|
|
||
| RETURN_CODE="0" | ||
|
|
||
| #check that extended APIC (or x2apic) is available, because it's required for more | ||
| # space for IRQs | ||
|
|
||
| grep -m1 -q -E '^flags.*(\<extapic|\<x2apic)' /proc/cpuinfo 2>/dev/null | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we know for certain that all relevant platforms have x2apic? down to the oldest supported server platforms? I never took notice of that to know myself.
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Apparently came out in 2008 with Nehalem.... I think that's older than weka. |
||
| EXT_APIC_STATUS=$? | ||
| if [[ ${EXT_APIC_STATUS} -eq 0 ]] ; then | ||
| RETURN_CODE="0" | ||
| else | ||
| RETURN_CODE="254" | ||
| echo "There is no extended APIC available. This can prevent the assignment" | ||
| echo "of enough IRQs to support all hardware, resulting in the kernel" | ||
| echo "error message: vector space exhaustion. This in turn can completely" | ||
| echo "prevent the kernel accessing devices such as NVMEs." | ||
| echo "A frequent cause of no extended APIC is the disabling of IOMMUs" | ||
| fi | ||
|
|
||
| if [[ ${RETURN_CODE} -eq "0" ]]; then | ||
| echo "Extended APIC reports available" | ||
| else | ||
| echo "No extended APIC available" | ||
| fi | ||
| exit ${RETURN_CODE} | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Weka doesnt care about the interrupts, the issue was that the kernel couldn't allocate interrupts and that caused the KERNEL to fail to use the device, which in turn made weka unable to use it since the device couldn't be scanned to know that it is a weka signed device.