Re: bad error handling in lpfc in 2.6.13

[Olaf Hering <olh@suse.de>]

 On Thu, Oct 06, James.Smart@Emulex.Com wrote:

> Patches were submitted to bring the driver up to rev 8.0.30, which was not
> pulled mainstream until 2.6.14-rc1 (or rc2). Please ensure you are running
> this driver. Note: a tarball with the sources, functional on 2.6.12/2.6.13
> can be found on sourceforge
> (http://sourceforge.net/project/showfiles.php?group_id=103050&package_id=110636)

Another thing I found today, sdb, sdc, sdd and sde did all map to the
very same "disk" on the other end, with 2.6.13.

I see this in dmesg:

<3>lpfc 0001:58:01.0: 0:0321 Unknown IOCB command Data: x0 x3 x0 x0
<3>lpfc 0001:58:01.0: 0:1303 Link Up Event x1 received Data: x1 x1 x4 x0

Will try the newer driver version and see how it goes.

> As for the error - Hardware error is a bad thing. Actually, we're already 
> rewriting the driver to deal with hardware errors that fail attach, such as
> this. It will be in our next release. Note that we also encountered an oops
> in the host midlayer, where a call to scsi_host_put is called directly after
> scsi_host_alloc, w/o an intervening scsi_host_add. We'll look throught the
> additional traces below and see if we see something.

I will move the card to another box and see how it goes. I heard the
p520 we have is pre-GA level.

-- 
short story of a lazy sysadmin:
 alias appserv=wotan