PCR 14604 - Boot needs a way to stop all cores on kernel fatal
Summary: Boot needs a way to stop all cores on kernel fatal
Status: NEW
Alias: None
Product: Kernel
Classification: Deos
Component: Kernel (show other PCRs)
Version: mainline
Hardware: All Deos
: Hold
: Enhancement
Target Milestone: mainline
Assignee: .Kernel
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2022-10-20 09:33 MST by rroffelsen
Modified: 2023-08-23 09:25 MST (History)
0 users

See Also:
Impact Assessment: TBD
Organization: DDC-I, Inc.
rroffelsen: Requirements?
rroffelsen: Code?
rroffelsen: TestCases?
rroffelsen: TestProcedures?
rroffelsen: Other?

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this PCR.
Description rroffelsen 2022-10-20 09:33:30 MST 
Currently when a kernel fatal occurs it only happens on one core. This leaves the other cores in an unknow state making it difficult (impossible?) for boot to ensure it has exclusive access to devices it may need to log the failure.

Note: Any solution should also consider the use case where platforms provide applications a means detecting and raising a fatal error to boot without notifying the kernel.
Comment 1 deosbugs.ccb 2023-02-13 13:07:02 MST 
CCB visited this PCR on 2023-02-13-71816
Comment 2 deosbugs.ccb 2023-02-13 13:37:59 MST 
PCR being placed on HOLD for jupiter verf.  It will be considered for a subsequent verf.
Comment 3 deosbugs.ccb 2023-08-14 11:04:49 MST 
CCB visited this PCR on 2023-08-14-64795
Comment 4 deosbugs.ccb 2023-08-23 09:25:24 MST 
PCR to remain on HOLD for kismet, given time constraints and lack of customer request.