-
Notifications
You must be signed in to change notification settings - Fork 51
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
kernel panic on host power on #11
Comments
I suspect this is due to my removal of the VGA setup from u-boot: 6d9e287#diff-84ea64abf02622ef709560b072e47382L83 I deleted this as u-boot wasn't using VGA. Oops. I will test this tory by doing the equivalent setup in the kernel. Seperaretly, we should fix the host so it does not crash when the BMC has done something it does not expect. Finally, as we discussed on Thursday, we should work out a way for the BMC to communicate to the host kernel that the VGA device is not present and should not be touched. @jk-ozlabs suggested removing the device tree node for the vga device before the kenrel sees it. |
The vga node is discovered over the PCIe bus and not via the host device tree. (there are security bits that can disable the vga device from the host). I believe the issue here is the BMC crashes when the host boots, around the time the VGA driver is initializing. The driver uses some scratch registers to find out how much BMC ram to use for the vga device. I suspect this memory was not reserved from the BMC and the host stomped on the BMC kernel's memory. |
I mistakenly thought the null pointer dereference was on the host. You're correct @mdmillerii, we don't reserve any memory for the vga device in OpenBMC |
According to BCM54612's datasheet, bit 7 of register openbmc#11 with shadow value 01000 indicates current duplex mode. If bit 7 is 0, it is full-duplex mode; otherwise half-duplex mode. The old code misinterpreted this bit, and this commit fixes this. Change-Id: I2fdb469cdf72ad3efaa4b2976f8cbb43ec935655 Signed-off-by: Wei-Chung Wen <wei-chung.wen@foxconn.com>
Change-Id: I558d5a04f25c77da71b9ef210e4f37ecd0c49dc1
I opened this against u-boot because the kernel has not changed. After moving to 2016.05 there is a kernel panic while booting the host:
its not much but that is all I get on the console
Meanwhile here is where we are in the boot (from the host console):
I was using openbmc/openbmc@856271d
The text was updated successfully, but these errors were encountered: