[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <JIUG4Z$FE429A5F18B9052E8E0CF6906B6CB68A@laposte.net>
Date: Wed, 30 May 2007 09:43:47 +0200
From: Emmanuel Fusté <emmanuel.fuste@...oste.net>
To: "romieu" <romieu@...zoreil.com>
Cc: "tsbogend" <tsbogend@...ha.franken.de>,
"lsorense" <lsorense@...lub.uwaterloo.ca>,
"pcnet32" <pcnet32@...izon.net>, "netdev" <netdev@...r.kernel.org>
Subject: Re: [PCNET32] Lock solid with netconsole
> Even if the driver-agnostic part of the irq processing can be interrupted
> locally, the irq handlers are run sequentially on a given cpu. It does not
> leave a lot of room for a deadlock-prone printk().
>
> It _can_ happen but I'd prefer to pinpoint a specific candidate path
> where it would have happened.
>
Hi,
Could this bug fix from Stephen Hemminger be another track to follow ?
http://marc.info/?l=linux-netdev&m=118048588011069&w=2
If you think so, I could give it a try whitout applying the "spin_lock_irqsave" patch.
---
Créez votre adresse électronique prenom.nom@...oste.net
1 Go d'espace de stockage, anti-spam et anti-virus intégrés.
-
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
Powered by blists - more mailing lists