From: Gabriel C <nix.or.die@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
stable <stable@vger.kernel.org>,
lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>,
Ruslan Ruslichenko <rruslich@cisco.com>
Subject: Re: Linux 4.9.6 ( Restore IO-APIC irq_chip retrigger callback , breaks my box )
Date: Sat, 11 Feb 2017 21:58:26 +0100 [thread overview]
Message-ID: <d6942f9c-5b97-c40a-0452-c54306aed184@gmail.com> (raw)
In-Reply-To: <20170211142059.447eo6bgxycmp6kb@pd.tnic>
On 11.02.2017 15:21, Borislav Petkov wrote:
> On Sat, Feb 11, 2017 at 02:09:14PM +0100, Gabriel C wrote:
>> Adding ' dis_ucode_ldr ' to commandline makes the kernel hangs right after :
>
> Wait a minute, are you saying that without dis_ucode_ldr you can't even
> boot so far?
Yes , it will hang before tsc message ..
Also sometimes I have same trace sometimes it just hangs forever.
>
>> clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x20ac7f6ecc6, max_idle_ns: 440795315461 ns
>> ...
>>
>> and I have the bug triggered really quick..
>>
>> Also I cannot get netconsole to work , I'm sure is some problem here local and I don't have
>> any serial cable around right now. The only way I saw now to give you at least some ifo is to
>> make an video of that crash. You can find it there :
>>
>> http://ftp.frugalware.org/pub/other/people/crazy/kernel/t/crash.mp4
>
> Watchdog fires on all cores showing they're all idle. For some reason,
> not all cores get to dump the watchdog splat, though. Some seem really
> stuck.
>
> And you have TAINT_FIRMWARE_WORKAROUND due to
> intel_prepare_irq_remapping() noticing intr remapping is broken on that
> box.
Well yes and I'm not so sure is really broken.. I reverted the patch blacklisted my box right after it was addeded
the time and I don't have any issues .. however since I don't have a use of that feature I don't really care is marked broken or not..
>
> Would be better if you could disable that frugalware splash screen and
> switch to grub console mode so that we can see the very beginning of the
> boot.
I do that tomorrow ...
>
> Btw, your BIOS is from 2013. Is there new one, per chance, on your
> vendor's site? Might wanna consider updating it...
>
This BIOS was / is newest one :(
next prev parent reply other threads:[~2017-02-11 20:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 7:48 Linux 4.9.6 Greg KH
2017-01-26 7:48 ` Greg KH
2017-02-06 17:30 ` Linux 4.9.6 ( Restore IO-APIC irq_chip retrigger callback , breaks my box ) Gabriel C
2017-02-06 17:41 ` Greg KH
2017-02-06 19:05 ` Ruslan Ruslichenko -X (rruslich - GLOBALLOGIC INC at Cisco)
2017-02-06 20:38 ` Gabriel C
2017-02-06 23:06 ` Linus Torvalds
2017-02-07 20:46 ` Thomas Gleixner
2017-02-07 21:25 ` Thomas Gleixner
2017-02-10 23:17 ` Gabriel C
2017-02-11 1:42 ` Gabriel C
2017-02-11 8:26 ` Thomas Gleixner
2017-02-11 13:09 ` Gabriel C
2017-02-11 14:21 ` Borislav Petkov
2017-02-11 20:58 ` Gabriel C [this message]
2017-02-11 21:32 ` Borislav Petkov
2017-02-12 20:21 ` Gabriel C
2017-02-12 21:12 ` Borislav Petkov
2017-02-12 22:21 ` Gabriel C
2017-02-13 0:38 ` Borislav Petkov
2017-02-13 1:26 ` Gabriel C
2017-02-13 2:31 ` Mike Galbraith
2017-02-13 8:47 ` Thomas Gleixner
2017-02-13 8:52 ` [tip:timers/urgent] tick/broadcast: Prevent deadlock on tick_broadcast_lock tip-bot for Mike Galbraith
2017-02-13 10:28 ` Linux 4.9.6 ( Restore IO-APIC irq_chip retrigger callback , breaks my box ) Borislav Petkov
2017-02-07 21:24 ` Thomas Gleixner
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=d6942f9c-5b97-c40a-0452-c54306aed184@gmail.com \
--to=nix.or.die@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=rruslich@cisco.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®