Re: [PATCH 4/4] bnx2i: Add bnx2i iSCSI driver.

On Thu, 2009-05-07 at 14:01 -0700, Mike Christie wrote: > Michael Chan wrote: > > On Wed, 2009-05-06 at 09:48 -0700, Mike Christie wrote: > >> I think cxgb3i is one day going to want to support the same features > >> bnx2i does. If that is right, then should we just make the NX2_UIO > >> events

Re: No abort is sent for a WRITE command that takes too long

On Mon, May 18, 2009 at 6:01 PM, Mike Christie wrote: > > Erez Zilber wrote: >> On Mon, May 18, 2009 at 4:36 PM, Mike Christie wrote: >>> Erez Zilber wrote: I enabled open-iscsi logging + added some printk calls when the abort handler returns. Here's the log. I see that iscsi_eh_c

Re: No abort is sent for a WRITE command that takes too long

Erez Zilber wrote: > On Mon, May 18, 2009 at 4:36 PM, Mike Christie wrote: >> Erez Zilber wrote: >>> I enabled open-iscsi logging + added some printk calls when the abort >>> handler returns. >>> Here's the log. I see that iscsi_eh_cmd_timed_out gets called, but >>> there's no abort. >>> May 17 1

Re: No abort is sent for a WRITE command that takes too long

On Mon, May 18, 2009 at 4:36 PM, Mike Christie wrote: > > Erez Zilber wrote: >> >> I enabled open-iscsi logging + added some printk calls when the abort >> handler returns. >> Here's the log. I see that iscsi_eh_cmd_timed_out gets called, but >> there's no abort. > >> May 17 11:00:06 kpc36 kernel

Re: No abort is sent for a WRITE command that takes too long

Erez Zilber wrote: > > I enabled open-iscsi logging + added some printk calls when the abort > handler returns. > Here's the log. I see that iscsi_eh_cmd_timed_out gets called, but > there's no abort. > May 17 11:00:06 kpc36 kernel: session1: iscsi_eh_cmd_timed_out scsi > cmd 8101e30efe40 t