From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: akpm@osdl.org, netdev@vger.kernel.org,
jeffrey.t.kirsher@intel.com, jesse.brandeburg@intel.com,
john.ronciak@intel.com, nils.rennebarth@packetalarm.com,
stern@rowland.harvard.edu
Subject: Re: [patch 7/9] e100: disable interrupts at boot
Date: Thu, 27 Apr 2006 09:05:47 -0600 [thread overview]
Message-ID: <200604270905.47774.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <44509628.4090704@garzik.org>
On Thursday 27 April 2006 04:00, Jeff Garzik wrote:
> akpm@osdl.org wrote:
> > From: Bjorn Helgaas <bjorn.helgaas@hp.com>
> >
> > Apparently the Intel PRO/100 device enables interrupts on reset. Unless
> > firmware explicitly disables PRO/100 interrupts, we can get a flood of
> > interrupts when a driver attaches to an unrelated device that happens to
> > share the PRO/100 IRQ.
> >
> > This should resolve this "irq 11: nobody cared" bug report:
> > http://bugzilla.kernel.org/show_bug.cgi?id=5918
> >
> > Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
> > Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>
> > Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> > Cc: John Ronciak <john.ronciak@intel.com>
> > Cc: <stern@rowland.harvard.edu>
> > Cc: <nils.rennebarth@packetalarm.com>
> > Signed-off-by: Andrew Morton <akpm@osdl.org>
>
> I'm really worried that we are burdening the kernel for a very very rare
> condition. Do we want to apply this for one stupid firmware?
>
> Can't early userspace just run setpci to fix this one?
I don't think so, because the problem occurs as soon as any driver
enables IRQ 11. I agree that it's rare, but it's a real pain to
debug it and identify it when it occurs.
prev parent reply other threads:[~2006-04-27 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 9:30 [patch 7/9] e100: disable interrupts at boot akpm
2006-04-27 10:00 ` Jeff Garzik
2006-04-27 15:05 ` Bjorn Helgaas [this message]
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=200604270905.47774.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nils.rennebarth@packetalarm.com \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).