Hi,
I see there is a bit of complaining on this original resend temporary
patch. But, since it seems to do a good job for some people, here is
my proposal to limit the 'range of fire' a little bit.
Marcin and Jean-Baptiste: try to test this with 2.6.23-rc2, please.
(Unless Ingo or Thomas
other plans with this problem?)
Thanks,
Jarek P.
Subject: [patch] genirq: temporary fix for level-triggered IRQ resend
Marcin Slusarz reported a ne2k-pci hung network interface regression.
delayed disable relies on the ability to re-trigger the interrupt in the
case that a real
Ingo Molnar wrote:
Linus,
with -rc2 approaching i think we should apply the minimal fix below to
get Marcin's ne2k-pci networking back in working order. The
WARN_ON_ONCE() will not prevent the system from working and it will be a
reminder.
a better workaround would be to inhibit the
* Gabriel C [EMAIL PROTECTED] wrote:
I get a warning on each boot now with this patch ..
[ 63.686613] WARNING: at kernel/irq/resend.c:70 check_irq_resend()
[ 63.686636] [c013c55c] check_irq_resend+0x8c/0xa0
[ 63.686653] [c013c15f] enable_irq+0xad/0xb3
[ 63.686662] [e886481e]
Linus,
with -rc2 approaching i think we should apply the minimal fix below to
get Marcin's ne2k-pci networking back in working order. The
WARN_ON_ONCE() will not prevent the system from working and it will be a
reminder.
a better workaround would be to inhibit the resent vector via the
* Ingo Molnar [EMAIL PROTECTED] wrote:
Linus,
with -rc2 approaching i think we should apply the minimal fix below to
get Marcin's ne2k-pci networking back in working order. The
WARN_ON_ONCE() will not prevent the system from working and it will be
a reminder.
there's one more
