netdev - Re: [patch 4/6] [TULIP] Quiet down tulip_stop

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070316001010.GE5291@nifty>
Date:	Thu, 15 Mar 2007 17:10:10 -0700
From:	Valerie Henson <val_henson@...ux.intel.com>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	akpm@...l.org, netdev@...r.kernel.org,
	Grant Grundler <grundler@...isc-linux.org>
Subject: Re: [patch 4/6] [TULIP]  Quiet down tulip_stop_rxtx

On Thu, Mar 15, 2007 at 11:25:10AM -0400, Jeff Garzik wrote:
> 
> Here's the problem with this:  this printk is signalling that the DMA 
> engines have not yet stopped, which is an event of which we should be wary.
> 
> While it makes sense to do this patch, since the complaining cards 
> appear to work anyway, we also need to take into account the times when 
> this is not a spurious warning.
> 
> Thus, I would consider maybe adding a warning somewhere in the 
> DMA-engine-start region of code, that complains if the DMA engines are 
> already active, or somesuch.

Yeah, I agree it's signifying a problem, and we should have a warning
(only one) until we figure out what's going on.  Put on my to-do list.

-VAL
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html