[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <E5313AF6F2BFD14293E5FD0F94750F86A5D7348A7B@HQ1-EXCH01.corp.brocade.com>
Date: Mon, 18 Apr 2011 12:26:12 -0700
From: Rasesh Mody <rmody@...cade.com>
To: David Miller <davem@...emloft.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Debashis Dutt <ddutt@...cade.COM>
Subject: RE: [PATCH 1/2] bna: fix for clean fw re-initialization
>From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
>On Behalf Of David Miller
>Sent: Thursday, April 14, 2011 1:40 PM
>To: Rasesh Mody
>Cc: netdev@...r.kernel.org; Debashis Dutt
>Subject: Re: [PATCH 1/2] bna: fix for clean fw re-initialization
>
>From: Rasesh Mody <rmody@...cade.com>
>Date: Thu, 14 Apr 2011 11:05:18 -0700
>
>> During a kernel crash, bna control path state machine and firmware do
>not
>> get a notification and hence are not cleanly shutdown. The registers
>> holding driver/IOC state information are not reset back to valid
>> disabled/parking values. This causes subsequent driver initialization
>> to hang during kdump kernel boot. This patch, during the
>initialization
>> of first PCI function, resets corresponding register when unclean
>shutown
>> is detect by reading chip registers. This will make sure that ioc/fw
>> gets clean re-initialization.
>>
>> Signed-off-by: Debashis Dutt <ddutt@...cade.com>
>> Signed-off-by: Rasesh Mody <rmody@...cade.com>
>
>Applied.
Hello David,
We were not able to see these patches when we did a git-pull of
net-next-2.6. We were wondering if the patches are stuck behind
others and not committed to the tree.
Thanks.
--
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