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
Subject: Re: Kernel panic - not syncing: IO-APIC + timer doesn't work!
Date: Tue, 28 Jul 2020 10:22:31 +0200	[thread overview]
Message-ID: <87blk0aw1k.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <e0ce41cd-9149-e43e-f4ca-e75503cb82e3@broadcom.com>

Scott,

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?

> [    0.000000] Linux version 5.8.0-rc6 (oe-user@oe-host) (x86_64-poky-linux-gcc (GCC) 10.1.0, GNU ld (GNU Binutils) 2.34.0.20200220) #1 SMP Sat Jul 25 03:55:25 UTC 2020
> [    0.000000] Command line: BOOT_IMAGE=/bzImage ima_policy=tcb
> apic=debug ip=dhcp raid=noautodetect console=ttyS0,115200
> root=/dev/nfs nfsroot=192.168.1.100:/nfs/vxc,hard,tcp,intr,v3 rootwait
> nfsrootdebug

The working dmesg and the failing console log are hard to compare
because the latter does not contain debug level printks. Please add
'ignore_loglevel' to the command line parameters.

Thanks,

        tglx

  reply	other threads:[~2020-07-28  8:22 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 [this message]
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

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=87blk0aw1k.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=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).