On Sun, 2007-04-01 at 16:29 -0400, Douglas Gilbert wrote:
...
sas: phy3 added to port0, phy_mask:0x8
sas: DOING DISCOVERY on port 0, pid:2110
aic94xx: scb:0x80 timed out
This might be the problem.
I see this periodically when a phy goes out to lunch on my system ...
with me, it always seems
James Bottomley wrote:
On Sun, 2007-04-01 at 16:29 -0400, Douglas Gilbert wrote:
...
sas: phy3 added to port0, phy_mask:0x8
sas: DOING DISCOVERY on port 0, pid:2110
aic94xx: scb:0x80 timed out
This might be the problem.
I see this periodically when a phy goes out to lunch on my system
James Bottomley wrote:
On Sat, 2007-03-31 at 15:05 -0400, Douglas Gilbert wrote:
James, note the SAS address of the first expander.
Thanks, just checking ... what happens when you directly attach a disk?
Then I get what I term as udev hell. That is when
FC6 gets to the point during boot-up
Douglas Gilbert wrote:
So that is almost 12 months that I have been reporting
this driver as broken. Is it just me or my hardware?
I seem to recall you saying that the LSI Fusion card was plugged into
the same expander as the 48300? If so, does unplugging the Fusion card
from the expander
Darrick J. Wong wrote:
Douglas Gilbert wrote:
So that is almost 12 months that I have been reporting
this driver as broken. Is it just me or my hardware?
I seem to recall you saying that the LSI Fusion card was plugged into
the same expander as the 48300? If so, does unplugging the
On Sat, 2007-03-31 at 15:05 -0400, Douglas Gilbert wrote:
James, note the SAS address of the first expander.
Thanks, just checking ... what happens when you directly attach a disk?
Or even try the other expander?
James
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
6 matches
Mail list logo
