Date: Thu, 18 Mar 2004 08:39:21 -0800
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: jgarzik@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: tulip (pnic) errors in 2.6.5-rc1
Message-Id: <20040318083921.049f93c3.rddunlap@osdl.org>
In-Reply-To: <16473.52851.367709.934661@alkaid.it.uu.se>
References: <16473.28514.341276.209224@alkaid.it.uu.se>
	<40597123.8020903@pobox.com>
	<405971B3.3080700@pobox.com>
	<16473.32039.160055.63522@alkaid.it.uu.se>
	<40597E68.7090908@pobox.com>
	<16473.52851.367709.934661@alkaid.it.uu.se>
Organization: OSDL
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 987
Lines: 28

On Thu, 18 Mar 2004 17:29:39 +0100 Mikael Pettersson wrote:

| Jeff Garzik writes:
|  > Mikael Pettersson wrote:
|  > > Jeff Garzik writes:
|  > >  > er, oops... lemme find the right patch...
|  > > 
|  > > No change, still a flood of those tulip_rx() interrupt messages.
|  > 
|  > hmmm.  Well, it is something unrelated to tulip driver, then.
| 
| Testing older -bk versions I've found that 2.6.4-bk2
| is Ok but 2.6.4-bk3 has this message flood problem.

That looks like exactly where the netdev_priv() patch went
in -- the one that Jeff asked you to back out and test again.
So I would have to ask you to verify that backing that patch
out didn't help, while we continue to look in other places
for possible problems...

Thanks,
--
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/