Reply to your suggestions,
1. with the kernel parameters, **aacraid.expose_physicals=0,
aacraid.dacmode=0**:
I tried both parameters, but failed.
2. about "[PATCH] Stop using num_physpages in aacraid":
I am not using this patch: I saw drivers/scsi/aacraid/aachba.c
(kernel-2.6.25.3)
3. about other kernels
Our machine normally runs with kernel-2.6.24 and
this failure occurs only with kernel-2.6.25 and later, including 2.6.26-rc1
Sincerely,
-------------------------------------------------------------
Takuya Yoshikawa @ NTT Open Source Software Center
e-mail: yoshikawa.takuya@xxxxxxxxxxxxx
-------------------------------------------------------------
Not a panic, merely a problem probing the physical devices. It may
seem 'forever' but that is what happens when it must issue commands to
every target and lun on two physical busses. You may be able to
mitigate this with the kernel parameter aacraid.expose_physicals=0, or
aacraid.dacmode=0
Status 8193 (0x2003) is not a known valid response code from the
Firmware, it is a result of the Firmware not processing the command in
the first place.
Could be a result of 'Subject: Re: [PATCH] Stop using num_physpages in
aacraid '? Could you revert that one out to see? Could you instrument
the return value to the new referenced function
dma_get_required_mask(&dev->pdev->dev) that is incorporated in that
patch?
Sincerely -- Mark Salyzyn
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
