From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Yinghai Lu <yhlu.kernel@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Jeff Garzik <jeff@garzik.org>,
Ayaz Abdulla <aabdulla@nvidia.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: regression caused by: genirq: do not leave interupts enabled on free_irq
Date: Fri, 11 Apr 2008 17:19:43 +0200 [thread overview]
Message-ID: <200804111719.44833.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.1.10.0804111217450.3261@apollo.tec.linutronix.de>
On Friday, 11 of April 2008, Thomas Gleixner wrote:
> On Fri, 11 Apr 2008, Eric W. Biederman 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.
>
> Hmm, we disable the interrupt on free_irq(), but we reenable it in
> request_irq()/setup_irq(), which is called when the forcedeth driver
> initializes in the kexeced kernel. So there is some other deeper down
> problem lurking.
>
> Yinghai, can you apply that patch to RHEL 5.1 and check, what happens
> if you do:
>
> modprobe forcedeth
> ifup ...
> ifdown ...
> rmmod forcedeth
> modprobe forcedeth
> ifup ...
>
> This should result in the same problem, but probably simpler to debug.
I've just got a report from a forcedeth user that it doesn't work after a
resume from RAM for him any more. Can it be related?
Rafael
next prev parent reply other threads:[~2008-04-11 15:19 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 [this message]
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
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=200804111719.44833.rjw@sisk.pl \
--to=rjw@sisk.pl \
--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=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.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