Date: Tue, 29 Jul 2008 13:47:06 -0700 (PDT)
Message-Id: <20080729.134706.249036102.davem@davemloft.net>
To: arjan@infradead.org
Cc: komurojun-mbn@nifty.com, linux-kernel@vger.kernel.org,
       netdev@vger.kernel.org
Subject: Re: NETDEV WATCHDOG: wifi0: transmit timed out
From: David Miller <davem@davemloft.net>
In-Reply-To: <20080729065859.2bcc65ed@infradead.org>
References: <20080525112308.03a5fda7.komurojun-mbn@nifty.com>
	<20080729215315.5a505fe7.komurojun-mbn@nifty.com>
	<20080729065859.2bcc65ed@infradead.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1009
Lines: 28

From: Arjan van de Ven <arjan@infradead.org>
Date: Tue, 29 Jul 2008 06:58:59 -0700

> On Tue, 29 Jul 2008 21:53:15 +0900
> Komuro <komurojun-mbn@nifty.com> wrote:
> 
> > Hi,
> > 
> > Please try to comment out the "WARN_ON_ONCE"
> > at net/sched/sched_generic.c.
> > 
> 
> "I have a hardware failure so I'll comment out the message that says
> so, and then I won't have a failure". Yeah that'll work well.

Yes, this is indeed a recidulious suggestion, to hide the problem
instead of trying to figure out what it might actually be.

Komuro has a serious problem accepting the fact that this condition is
in fact an abnormal error should should be logged, and he keeps
pushing to get this WARN_ON() removed over and over again.

I'm just ignoring him at this point.
--
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/