netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jarek Poplawski <jarkao2@o2.pl>
Cc: Jean-Baptiste Vignaud <vignaud@xandmail.fr>,
	"marcin.slusarz" <marcin.slusarz@gmail.com>,
	tglx <tglx@linutronix.de>,
	torvalds <torvalds@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	shemminger <shemminger@linux-foundation.org>,
	linux-net <linux-net@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>, akpm <akpm@linux-foundation.org>,
	alan <alan@lxorguk.ukuu.org.uk>
Subject: Re: [patch (testing)] Re: 2.6.20->2.6.21 - networking dies after random time
Date: Fri, 10 Aug 2007 11:08:33 +0200	[thread overview]
Message-ID: <20070810090833.GA15121@elte.hu> (raw)
In-Reply-To: <20070810090318.GG1764@ff.dom.local>


* Jarek Poplawski <jarkao2@o2.pl> wrote:

> On 10-08-2007 10:05, Thomas Gleixner wrote:
> ...
> > But suppressing the resend is not fixing the driver problem. The 
> > problem can show up with spurious interrupts and with interrupts on 
> > a shared PCI interrupt line at any time. It just might take weeks 
> > instead of minutes.
> 
> Maybe I miss something but it's not the same!

_now_ i finally understand what you probably meant: because sw-resend 
worked and hw-resend didnt, it's hw-resend that is causing the breakage, 
not any driver or irqflow bug - correct?

	Ingo

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10  8:15 [patch (testing)] Re: 2.6.20->2.6.21 - networking dies after random time Jean-Baptiste Vignaud
2007-08-10  8:37 ` Jarek Poplawski
2007-08-10  8:48   ` Ingo Molnar
2007-08-10  9:03     ` Jarek Poplawski
2007-08-10  9:08       ` Ingo Molnar [this message]
2007-08-10  9:19         ` Jarek Poplawski
2007-08-10  9:38           ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2007-08-10  8:41 Jean-Baptiste Vignaud
2007-07-31 13:20 Jarek Poplawski
2007-08-06  7:00 ` Marcin Ślusarz
2007-08-06  7:03   ` Ingo Molnar
2007-08-07  7:46     ` Marcin Ślusarz
2007-08-07  8:23       ` Jarek Poplawski
     [not found]         ` <4bacf17f0708070237w19d184b3p7f74b53612edb9a6@mail.gmail.com>
2007-08-07  9:52           ` Jarek Poplawski
2007-08-07 12:13             ` Jarek Poplawski
2007-08-08 11:09               ` Marcin Ślusarz
2007-08-08 11:42                 ` Jarek Poplawski
2007-08-09  9:19                   ` [patch (testing)] " Jarek Poplawski
     [not found]                     ` <4bacf17f0708092333n17e0ba19jf2c769531610868d@mail.gmail.com>
2007-08-10  7:10                       ` Jarek Poplawski
2007-08-10 10:43                         ` Marcin Ślusarz
2007-08-10 11:37                           ` Jarek Poplawski

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=20070810090833.GA15121@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jarkao2@o2.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=vignaud@xandmail.fr \
    /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).