From: Thomas Gleixner <tglx@linutronix.de>
To: Gabriel C <nix.or.die@gmail.com>
Cc: 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 09:26:19 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1702110924371.3734@nanos> (raw)
In-Reply-To: <1e88cc0e-4d34-a314-a44f-8324335b79e3@gmail.com>
On Sat, 11 Feb 2017, Gabriel C wrote:
> On 07.02.2017 22:25, Thomas Gleixner wrote:
> Hi Thomas ,
>
> Sorry I was travelling..
Nothing to be sorry about.
> > Btw, how far in the boot process is the machine when this happens?
>
> Right after :
>
> Uncompressing Linux.....
> Booting the kernel..
>
> So early..
You might try with 'earlyprintk' on the command line. That should tell more.
> One thing is strange .. on all one socket boxes I have the kernel seems
> to be fine with that patch while breaks on both dual socket boxes ( well
> both have near same HW )
That's really weird.
Thanks,
tglx
next prev parent reply other threads:[~2017-02-11 9:05 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 [this message]
2017-02-11 13:09 ` Gabriel C
2017-02-11 14:21 ` Borislav Petkov
2017-02-11 20:58 ` Gabriel C
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=alpine.DEB.2.20.1702110924371.3734@nanos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=nix.or.die@gmail.com \
--cc=rruslich@cisco.com \
--cc=stable@vger.kernel.org \
--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®