From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@elte.hu>, "Jeff Garzik" <jeff@garzik.org>,
"Ayaz Abdulla" <aabdulla@nvidia.com>,
LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: regression caused by: genirq: do not leave interupts enabled on free_irq
Date: Tue, 15 Apr 2008 01:03:15 -0700 [thread overview]
Message-ID: <86802c440804150103s59f6fe16ncf08a3154c03d2bb@mail.gmail.com> (raw)
In-Reply-To: <20080415004400.bb941191.akpm@linux-foundation.org>
On Tue, Apr 15, 2008 at 12:44 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
>
> On Fri, 11 Apr 2008 12:48:43 -0700 "Yinghai Lu" <yhlu.kernel@gmail.com> wrote:
>
> > On Fri, Apr 11, 2008 at 11:22 AM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> > > On Fri, Apr 11, 2008 at 12:30 AM, Eric W. Biederman
> > > <ebiederm@xmission.com> wrote:
> > > >
> > > >
> > >
> > >
> > > > On Fri, 2008-04-11 at 00:17 -0700, Yinghai Lu wrote:
> > > > > On Fri, Apr 11, 2008 at 12:14 AM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> > > > > > On Fri, Apr 11, 2008 at 12:01 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > > > > > > On Thu, 10 Apr 2008, Yinghai Lu wrote:
> > > > > > > > last week found:
> > > > > > > > after latest kernel kexec RHEL 5.1 or other stack kernel, the nvidia
> > > > > > > > forcedeth doesn't work anymore.
> > > > > > > >
> > > > > > > > I stared at forcedeth.c two days. and revert every patches about that
> > > > > > > > doesn't help.
> > > > > > >
> > > > > > > So forcedeth does not come up again, when you kexec from linus.git
> > > > > > > into an older distro kernel. Or is it the other way round ?
> > > > > > RHEL 5.1 kexec RHEL 5.1 : works
> > > > > > RHEL 5.1 kexec linus kernel: works
> > > > > > linus (after -rc2) kexec linus tree: works:
> > > > > > linus (after -rc2) kexec RHEL 5.1 : forcedeth will not come up
> > > > > > linus ( before -rc2 include rc2) kexec RHEL 5.1 works
> > > > > >
> > > > > the forcedeth can not get IP address...
> > > >
> > > > Sounds like you are not getting any interrupts when you receive a
> > > > packet. (i.e. The interrupt line is staying disabled).
> > > >
> > > > Is MSI an option here? I'm wondering if we disable the MSI and
> > > > something is not enabling it.
> > >
> > >
> > >
> > > after
> > > setpci -s 0x00:08.0 0x60.b=0xfe
> > >
> > > the eth0 can get ip address with ifup eth0.
> >
> > it is RHEL 5.1 problem...with msi.
> >
> > somehow msi entry msi_attrib_maskbit=is_mask_bit_support always get
> > 0...., and use msi_irq_wo_maskbit_type instead of
> > msi_irq_w_maskbit_type
> >
> > so when load that directly without kexec
> > that 0x60 always to 0x00.
> >
> > and this time kernel after 2.6.25-rc2 ( not included) really shutdown
> > the msi with 0xff the all maskbit...
> >
>
> So... where did this end up? It's a post-2.6.24 regression, isn't it?
>
> Do we think it's a bug in the RHEL 5.1 kernel? Even so, that's a problem
> for the 2.6.25 kernel.
it is RHEL 5.1 kernel problem, it has code for maskbit with msi there,
but that does work...
I sent out patch for 2.6.25 so it can be used to kexec old kernel that
doesn't support maskbit for MSI.
please comment...
[PATCH] x86_64: restore mask_bits in msi shutdown
for MSI, default_shutdown will call mask_bit for msi device. so all
mask bits will
left disabled after free_irq.
then if kexec next kernel that only can use msi_enable bit.
all device's MSI can not be used.
So try to restore MSI mask bits that is saved before using msi in first kernel.
http://lkml.org/lkml/2008/4/11/369
YH
next prev parent reply other threads:[~2008-04-15 8:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 6:13 regression caused by: genirq: do not leave interupts enabled on free_irq Yinghai Lu
2008-04-11 7:01 ` Thomas Gleixner
2008-04-11 7:14 ` Yinghai Lu
2008-04-11 7:17 ` Yinghai Lu
2008-04-11 7:30 ` Eric W. Biederman
2008-04-11 8:40 ` Yinghai Lu
2008-04-11 15:59 ` Daniel Barkalow
2008-04-11 10:31 ` Thomas Gleixner
2008-04-11 15:19 ` Rafael J. Wysocki
2008-04-11 16:23 ` Yinghai Lu
2008-04-11 18:22 ` Yinghai Lu
2008-04-11 19:48 ` Yinghai Lu
2008-04-15 7:44 ` Andrew Morton
2008-04-15 8:03 ` Yinghai Lu [this message]
2008-04-15 8:17 ` Ingo Molnar
2008-04-15 8:23 ` Yinghai Lu
2008-04-15 8:06 ` Yinghai Lu
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=86802c440804150103s59f6fe16ncf08a3154c03d2bb@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=aabdulla@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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