From: Gabriel C <nix.or.die@gmail.com>
To: "Ruslan Ruslichenko -X (rruslich - GLOBALLOGIC INC at Cisco)"
<rruslich@cisco.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Linux 4.9.6 ( Restore IO-APIC irq_chip retrigger callback , breaks my box )
Date: Mon, 6 Feb 2017 21:38:22 +0100 [thread overview]
Message-ID: <eea84556-baee-eb71-1429-16fdb21ecb20@gmail.com> (raw)
In-Reply-To: <9bca3132-babd-24de-8e9a-7f7da8f70f7e@cisco.com>
On 06.02.2017 20:05, Ruslan Ruslichenko -X (rruslich - GLOBALLOGIC INC at Cisco) wrote:
> On 02/06/2017 07:41 PM, Greg KH wrote:
>> On Mon, Feb 06, 2017 at 06:30:15PM +0100, Gabriel C wrote:
>>> On 26.01.2017 08:48, Greg KH wrote:
>>>
>>> Hi Greg,
>>>
>>>> I'm announcing the release of the 4.9.6 kernel.
>>>
>>> Somewhat late , however I didn't tested 4.9.6 but jumped from 4.9.5 to 4.9.7
>>> and found out by box won't boot anymore.
>>>
>>> It hangs early and freeze with a lot RCU warnings.
>>> Since I cannot setup a netconsole right now I cannot post the errors , really sorry.
>>>
>>> ( but I could make a picture if needed )
>>>
>>>
>>> I bisected it down to :
>>>
>>>> Ruslan Ruslichenko (1):
>>>> x86/ioapic: Restore IO-APIC irq_chip retrigger callback
>>> Reverting this one fixes the problem for me..
>>>
>>> Also this problem exists in Linus tree , I tested on:
>>> 4.10.0-rc6-00167-ga0a28644c1cf
>> Ok, at least we are consistent :)
>>
>>> The box is a PRIMERGY TX200 S5 , 2 socket , 2 x E5520 CPU(s) installed.
>>>
>>> Config:
>>> https://raw.githubusercontent.com/frugalware/frugalware-current/master/source/base/kernel/config.x86_64
>> Ruslan, any thoughts about what to do here?
> This looks strange. What this patch does is just revert previous
> behavior, broken by d32932d02e18.
> So we can try to test with last v4.1 stable, where retrigger callback
> were still present.
I can test that but first on weekend if you wish.
> Also on v4.10 maybe check with software emulation of this feature and
> reverted patch, e.g.:
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index e487493..49c3c71 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -170,6 +170,7 @@ config X86
> select USER_STACKTRACE_SUPPORT
> select VIRT_TO_BUS
> select X86_FEATURE_NAMES if PROC_FS
> + select HARDIRQS_SW_RESEND
>
> config INSTRUCTION_DECODER
> def_bool y
>
With patch reverted + this one I get a early kernel panic.. on 4.10.0-rc7
With just the patch reverted all is fine , the box boots and all seems fine.
> I think for further debugging logs will be needed.
Yes sure , I just need to find a way to set something up like netconsole here.
Right now I have no way doig that. I'll try to do that on weekend too also.
Regards,
Gabriel C
next prev parent reply other threads:[~2017-02-06 20:38 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 [this message]
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
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=eea84556-baee-eb71-1429-16fdb21ecb20@gmail.com \
--to=nix.or.die@gmail.com \
--cc=akpm@linux-foundation.org \
--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