From: Scott Branden <scott.branden@broadcom.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
bp@alien8.de, x86@kernel.org, mingo@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel panic - not syncing: IO-APIC + timer doesn't work!
Date: Wed, 29 Jul 2020 16:28:00 -0700 [thread overview]
Message-ID: <3f6879be-db6e-073d-6252-30d3c046e9e4@broadcom.com> (raw)
In-Reply-To: <e41ea714-a042-b29b-d22e-8ee71d23f2e9@amd.com>
Hi Tom,
On 2020-07-29 11:29 a.m., Tom Lendacky wrote:
> On 7/29/20 4:50 AM, Thomas Gleixner wrote:
>> Scott,
>>
>> Scott Branden <scott.branden@broadcom.com> writes:
>>> On 2020-07-28 1:22 a.m., Thomas Gleixner wrote:
>>>> Scott Branden <scott.branden@broadcom.com> writes:
>>>>> Bios now updated to latest. Same kernel panic issue. Log below.
>>>>>
>>>>> I think it is related to power cycling quickly.
>>>>> Should APIC work if PC power cycled in a few seconds or is that the
>>>>> problem?
>>>> Yes, emphasis on should. Just to clarify, if you reboot it works and
>>>> cold start works as well if power was off long enough?
>>>>
>>> So far I have only been able to reproduce the issue by cold start with power off for only a few seconds
>>> before re-powering the system. It has not failed via reboot yet that I remember.
>>> Will have to keep my eye on whether using reboot is an issue or not.
>>> And also keeping power off longer when doing a cold start.
>> Weird.
>>
>>> Please find attached the failed console log with ignore_loglevel.
>> Aside of the differences caused by the BIOS update there is nothing
>> related to the APIC/IO-APIC setup which is different between the working
>> and failing boot.
>>
>> TBH, I have no idea what's going wrong there. Maybe Tom has one.
> I asked around and was told this is most likely the motherboard has not
> decayed its DC rails. So it's quite possible that keeping it powered off
> for a longer period of time before powering back on may help.
It does appear that the APIC hardware or some other component does not reset
something and assumes the power up value is 0.
Too bad proper voltage monitoring/full reset is not in place.
I was just reporting the issue as instructed by the kernel panic.
I think the issue is avoided by leaving the system powered off longer.
> Thanks,
> Tom
>
>> Thanks,
>>
>> tglx
>>
prev parent reply other threads:[~2020-07-29 23:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 18:39 Kernel panic - not syncing: IO-APIC + timer doesn't work! Scott Branden
2020-07-27 19:46 ` Andy Shevchenko
2020-07-27 20:51 ` Thomas Gleixner
2020-07-27 21:06 ` Scott Branden
2020-07-27 22:48 ` Scott Branden
2020-07-28 8:22 ` Thomas Gleixner
2020-07-28 17:30 ` Scott Branden
2020-07-29 9:50 ` Thomas Gleixner
2020-07-29 18:29 ` Tom Lendacky
2020-07-29 23:28 ` Scott Branden [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f6879be-db6e-073d-6252-30d3c046e9e4@broadcom.com \
--to=scott.branden@broadcom.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).