linux-kernel - Re: Kernel panic - not syncing: IO-APIC + timer doesn't work!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <3f6879be-db6e-073d-6252-30d3c046e9e4@broadcom.com>
Date:   Wed, 29 Jul 2020 16:28:00 -0700
From:   Scott Branden <scott.branden@...adcom.com>
To:     Tom Lendacky <thomas.lendacky@....com>,
        Thomas Gleixner <tglx@...utronix.de>, bp@...en8.de,
        x86@...nel.org, mingo@...hat.com
Cc:     linux-kernel@...r.kernel.org
Subject: Re: Kernel panic - not syncing: IO-APIC + timer doesn't work!

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@...adcom.com> writes:
>>> On 2020-07-28 1:22 a.m., Thomas Gleixner wrote:
>>>> Scott Branden <scott.branden@...adcom.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
>>