mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Wilck <martin.wilck@fujitsu-siemens.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "vgoyal@in.ibm.com" <vgoyal@in.ibm.com>,
	Haren Myneni <hbabu@us.ibm.com>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PATCH/RFC: [kdump] fix APIC shutdown sequence
Date: Wed, 08 Aug 2007 11:03:17 +0200	[thread overview]
Message-ID: <46B986D5.2010407@fujitsu-siemens.com> (raw)
In-Reply-To: <m1ir7qg7kd.fsf@ebiederm.dsl.xmission.com>

Hello Eric,

> How bad is it if you just run with irqpoll in the kdump kernel?
> If running with irqpoll is usable that is probably preferable
> to putting in a hardware work around we can survive without.

Yes, I tried that. No effect.

> Have you done any looking at moving where the kernel initalizes
> io_apics?  One of the todo items on the path is to leave
> io_apic mode enabled and just startup the kernel in io_apic
> mode.

I have tried to recover from the "IRR set" situation in several ways by
changing setup_IO_APIC_irq(). But I haven't found a way to recover from
this situation once disable_IO_APIC() had been called.
I concluded thatthe sequence of events
"send INT message - never receive EOI - disable IO-APIC pin"
messes up the IO-APIC (at least this specific one in the
PCIEx-PCI bridge of the ICH7).

The current state of affairs is that the only thing that "worked" was to
re-enable irqs.

> When doing that a version of your work around (if needed)
> would certainly be reasonable.

> My general concern is that the trickier we get in the code
> running in the crashed kernel the less reliable the entire
> process will be.

That's certainly correct. I am grateful for all hints that simplify my patch.

Thanks,
Martin

-- 
Martin Wilck
PRIMERGY System Software Engineer
FSC IP ESP DE6

Fujitsu Siemens Computers GmbH
Heinz-Nixdorf-Ring 1
33106 Paderborn
Germany

Tel:			++49 5251 8 15113
Fax:			++49 5251 8 20409
Email:			mailto:martin.wilck@fujitsu-siemens.com
Internet:		http://www.fujitsu-siemens.com
Company Details:	http://www.fujitsu-siemens.com/imprint.html

  reply	other threads:[~2007-08-08  9:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 15:08 Martin Wilck
2007-08-07 14:29 ` Vivek Goyal
2007-08-07 17:41   ` Martin Wilck
2007-08-08  1:04     ` Eric W. Biederman
2007-08-08  9:03       ` Martin Wilck [this message]
2007-08-08  9:33         ` Vivek Goyal
2007-08-08 12:04           ` Martin Wilck
2007-08-08 15:21         ` Eric W. Biederman
2007-08-08 17:35           ` Martin Wilck
2007-08-08 17:56             ` Eric W. Biederman
2007-08-08 18:22               ` Martin Wilck
2007-08-08 18:38               ` Martin Wilck
2007-08-08 10:36     ` Vivek Goyal
2007-08-08 14:06       ` Chip Coldwell
2007-08-08 14:42         ` Vivek Goyal
2007-08-08 18:15           ` Martin Wilck
2007-08-09 10:11             ` Vivek Goyal
2007-08-09 17:35               ` Martin Wilck
2007-08-07 19:44   ` Chip Coldwell
2007-08-08  0:29 ` Andrew Morton
2007-08-08  8:32   ` Martin Wilck
2007-08-08 11:38 ` Vivek Goyal
2007-08-08 18:07   ` Martin Wilck
2007-08-08 21:25     ` Eric W. Biederman

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=46B986D5.2010407@fujitsu-siemens.com \
    --to=martin.wilck@fujitsu-siemens.com \
    --cc=ebiederm@xmission.com \
    --cc=hbabu@us.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@in.ibm.com \
    /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

Powered by JetHome