Summary: | app-emulation/xen-4.12.0_rc4 - ? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John L. Poole <prestopoole> |
Component: | Current packages | Assignee: | Gentoo Xen Devs <xen> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | hydrapolic |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge log of xen-tools (bzip2)
kernel config dmesg during DOM0 session lspci -vvv output in DOM0 session * [all diagnostics] from serial port serial port log HTML in 3 columns displaying logs |
Description
John L. Poole
2019-03-15 17:12:59 UTC
Created attachment 569220 [details]
emerge log of xen-tools (bzip2)
Created attachment 569222 [details]
kernel config
Created attachment 569224 [details]
dmesg during DOM0 session
Created attachment 569226 [details]
lspci -vvv output in DOM0 session
Created attachment 569228 [details]
* [all diagnostics] from serial port
During a successful boot-up of the Xen kernel and in a DOM0 instance, I switch to the kernel (Control-A thrice in the serial port console (PuTTY on Windows)) and depressed the "*" for a complete diagnostic. This is the log file of the output, extracted from the serial port log concurrently being posted in this Bug.
Note: I found if I performed a complete diagnostic, about a minute later, watchdog would shut the instance down. I included the two lines of the final notification following the diagnostic's dump. Thereafter, I had to manually reboot the server.
(XEN) [2019-03-15 16:28:28] .................................... done.
(XEN) [2019-03-15 16:28:46] Watchdog timer fired for domain 0
(XEN) [2019-03-15 16:28:46] Hardware Dom0 shutdown: watchdog rebooting machine
Created attachment 569230 [details]
serial port log
Includes failed attempts to boot and successful attempts as well as Xen diagnostics "*"
In the earlier bug, Bug # 679826, I modified the app-emulation/xen package with debugging code in an attempt to isolate the event where the system hangs. My attempts cause me to conclude that the function setup_local_APIC(void)" [lines 524-726] completes it's task and the the hanging it occurring at a higher level. Unfortunately, my inexperience with C leaves me clueless as to where this might be happening. I tried wrapping around all calls to "setup_local_APIC", but there may be a callback or hook at play from some macro. Here is a link to the patch I used: https://bugs.gentoo.org/attachment.cgi?id=568924 Here is a sample of my debug statements: https://bugs.gentoo.org/679826#c11 I'm prepared to create a debug patch for this version if desired. What I really would need is suggestions of where to insert "print" statements outside of the apic.c file. Posted "Bug" to xen-devel mailing list. https://lists.xenproject.org/archives/html/xen-devel/2019-03/msg01268.html (In reply to John L. Poole from comment #0) > This bug parallels Bug# 679826 which exhibits the same problems booting up "the same problems" *** This bug has been marked as a duplicate of bug 679826 *** Created attachment 569606 [details]
HTML in 3 columns displaying logs
It is helpful for me to be able to compare and contrast the boot logs of:
1) regular Gentoo kernel
2) grub2 launch of Xen kernel
3) EFI console launch of Xen kernel.
So I created an HTML page that displays all three in 3 scrollable columns. The purpose of this is to see if the log entries of the successful Gentoo boot reveal something ommitted form the Xen kernel. This is the first round and I wanted to post this so if anyone thinks this helpful and has suggestions I can incorporate same sooner rather than later. My next step is to map the output to various functions while reviewing the kernel configurations and log files of the emerge app-emulation/xen.
|