Re: [PATCH 1/6] megaraid_sas: Do not wait forever

2014-01-24 Thread Hannes Reinecke
xena, Sumit >> Subject: Re: [PATCH 1/6] megaraid_sas: Do not wait forever >> >> On 01/24/2014 08:46 AM, Desai, Kashyap wrote: >>> Hannes: >>> >>> We have already worked on "wait_event" usage in >> "megasas_issue_blocked_cmd". >

RE: [PATCH 1/6] megaraid_sas: Do not wait forever

2014-01-24 Thread Desai, Kashyap
> -Original Message- > From: Hannes Reinecke [mailto:h...@suse.de] > Sent: Friday, January 24, 2014 1:54 PM > To: Desai, Kashyap; James Bottomley > Cc: linux-scsi@vger.kernel.org; Adam Radford; Saxena, Sumit > Subject: Re: [PATCH 1/6] megaraid_sas: Do not wait forever

Re: [PATCH 1/6] megaraid_sas: Do not wait forever

2014-01-24 Thread Hannes Reinecke
On 01/24/2014 08:46 AM, Desai, Kashyap wrote: > Hannes: > > We have already worked on "wait_event" usage in "megasas_issue_blocked_cmd". > That code will be posted by LSI once we received test result from LSI Q/A team. > > If you see the current OCR code in Linux Driver we do "re-send the IOCTL

RE: [PATCH 1/6] megaraid_sas: Do not wait forever

2014-01-23 Thread Desai, Kashyap
day-1 design, but will try to cover wait_event_timout for some valid cases. ` Kashyap > -Original Message- > From: Hannes Reinecke [mailto:h...@suse.de] > Sent: Thursday, January 16, 2014 3:56 PM > To: James Bottomley > Cc: linux-scsi@vger.kernel.org; Hannes Reinecke;

[PATCH 1/6] megaraid_sas: Do not wait forever

2014-01-16 Thread Hannes Reinecke
If the firmware is incommunicado for whatever reason the driver will wait forever during initialisation, causing all sorts of hangcheck timers to trigger. We should rather wait for a defined time, and give up on the command if no response was received. Cc: Kashyap Desai Cc: Adam Radford Signed-o