MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16473.39381.452618.398385@alkaid.it.uu.se>
Date: Thu, 18 Mar 2004 13:45:09 +0100
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tulip (pnic) errors in 2.6.5-rc1
In-Reply-To: <40597E68.7090908@pobox.com>
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>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1167
Lines: 29

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.
 > 
 > Did you recently change module options, or forget to disable tulip_debug 
 > in modprobe.conf or modules.conf ?
 > 
 >          if (tulip_debug > 4)
 >                  printk(KERN_DEBUG "%s: exiting interrupt, csr5=%#4.4x.\n",
 >                             dev->name, inl(ioaddr + CSR5));
 > 
 > Those messages only appear if a non-default verbosity has been selected.

I had the same .config and kernel boot parameters as for 2.6.4,
except I disabled modules and everything non-essential, and
didn't apply my private patches.

440BX chipset, no I/O-APIC, no ACPI, no PREEMPT, direct PCI access,
two FA310TXs (eth0 idle, eth1 had light traffic).
-
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/