linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Scott Branden <scott.branden@broadcom.com>,
	bp@alien8.de, x86@kernel.org, mingo@redhat.com
Cc: linux-kernel@vger.kernel.org, Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: Kernel panic - not syncing: IO-APIC + timer doesn't work!
Date: Wed, 29 Jul 2020 11:50:41 +0200	[thread overview]
Message-ID: <87y2n2abv2.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <cc298d3e-9a14-d3e1-025b-6bb1f8bfb4ae@broadcom.com>

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.

Thanks,

        tglx

  reply	other threads:[~2020-07-29  9:50 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 [this message]
2020-07-29 18:29           ` Tom Lendacky
2020-07-29 23:28             ` Scott Branden

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=87y2n2abv2.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=scott.branden@broadcom.com \
    --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).