On 29 April 2015 at 20:09, Nathan Rennie-Waldock <nathan.renniewaldock@xxxxxxxxx> wrote: > On 29 April 2015 at 19:05, James Bottomley > <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> wrote: >> On Wed, 2015-04-29 at 09:24 -0700, Adam Talbot wrote: >>> Attached is what I see on my 4.0.0 patched kernel. I am going through >>> a SAS expander: >>> [ 5.176095] scsi host4: mvsas >>> [ 5.180076] sas: phy-4:0 added to port-4:0, phy_mask:0x1 (50030480002f51ff) >>> [ 5.180079] drivers/scsi/mvsas/mv_sas.c 1118:set wide port phy map 1 >>> [ 5.190007] sas: phy1 matched wide port0 >>> [ 5.190010] sas: phy-4:1 added to port-4:0, phy_mask:0x3 (50030480002f51ff) >>> [ 5.190012] drivers/scsi/mvsas/mv_sas.c 1118:set wide port phy map 3 >>> [ 5.209850] sas: phy2 matched wide port0 >>> [ 5.209853] sas: phy-4:2 added to port-4:0, phy_mask:0x7 (50030480002f51ff) >>> [ 5.209854] drivers/scsi/mvsas/mv_sas.c 1118:set wide port phy map 7 >>> [ 5.239609] sas: phy3 matched wide port0 >>> [ 5.239612] sas: phy-4:3 added to port-4:0, phy_mask:0xf (50030480002f51ff) >>> [ 5.239613] drivers/scsi/mvsas/mv_sas.c 1118:set wide port phy map f >>> [ 5.279368] sas: DOING DISCOVERY on port 0, pid:6 >>> [ 5.280102] sas: ex 50030480002f51ff phy00:S:9 attached: >>> 5005043011ab0000 (host) >>> [ 5.280356] sas: ex 50030480002f51ff phy01:S:9 attached: >>> 5005043011ab0000 (host) >>> [ 5.280622] sas: ex 50030480002f51ff phy02:S:9 attached: >>> 5005043011ab0000 (host) >>> [ 5.280877] sas: ex 50030480002f51ff phy03:S:9 attached: >>> 5005043011ab0000 (host) >>> [ 5.281141] sas: ex 50030480002f51ff phy04:D:9 attached: >>> 50030480002f51c4 (stp) >>> [ 5.281339] sas: ex 50030480002f51ff phy05:D:9 attached: >>> 50030480002f51c5 (stp) >>> [ 5.281547] sas: ex 50030480002f51ff phy06:D:9 attached: >>> 50030480002f51c6 (stp) >>> [ 5.281801] sas: ex 50030480002f51ff phy07:D:9 attached: >>> 50030480002f51c7 (stp) >>> [ 5.282003] sas: ex 50030480002f51ff phy08:D:9 attached: >>> 50030480002f51c8 (stp) >>> [ 5.282216] sas: ex 50030480002f51ff phy09:D:8 attached: >>> 50030480002f51c9 (stp) >>> [ 5.282419] sas: ex 50030480002f51ff phy10:D:8 attached: >>> 50030480002f51ca (stp) >>> [ 5.282636] sas: ex 50030480002f51ff phy11:D:8 attached: >>> 50030480002f51cb (stp) >>> [ 5.282862] sas: ex 50030480002f51ff phy12:D:8 attached: >>> 50030480002f51cc (stp) >>> [ 5.283042] sas: ex 50030480002f51ff phy13:D:9 attached: >>> 50030480002f51cd (stp) >>> [ 5.283202] sas: ex 50030480002f51ff phy14:D:8 attached: >>> 50030480002f51ce (stp) >>> [ 5.283355] sas: ex 50030480002f51ff phy15:D:0 attached: >>> 0000000000000000 (no device) >>> [ 5.283504] sas: ex 50030480002f51ff phy16:D:0 attached: >>> 0000000000000000 (no device) >>> [ 5.283655] sas: ex 50030480002f51ff phy17:D:0 attached: >>> 0000000000000000 (no device) >>> [ 5.283808] sas: ex 50030480002f51ff phy18:D:0 attached: >>> 0000000000000000 (no device) >>> [ 5.283957] sas: ex 50030480002f51ff phy19:D:0 attached: >>> 0000000000000000 (no device) >>> [ 5.284084] sas: ex 50030480002f51ff phy20:T:0 attached: >>> 0000000000000000 (no device) >>> [ 5.284235] sas: ex 50030480002f51ff phy21:T:0 attached: >>> 0000000000000000 (no device) >>> [ 5.284385] sas: ex 50030480002f51ff phy22:T:0 attached: >>> 0000000000000000 (no device) >>> [ 5.284508] sas: ex 50030480002f51ff phy23:T:0 attached: >>> 0000000000000000 (no device) >>> [ 5.284659] sas: ex 50030480002f51ff phy24:T:0 attached: >>> 0000000000000000 (no device) >>> [ 5.284787] sas: ex 50030480002f51ff phy25:T:0 attached: >>> 0000000000000000 (no device) >>> [ 5.284938] sas: ex 50030480002f51ff phy26:T:0 attached: >>> 0000000000000000 (no device) >>> [ 5.285091] sas: ex 50030480002f51ff phy27:T:0 attached: >>> 0000000000000000 (no device) >>> [ 5.285220] sas: ex 50030480002f51ff phy28:D:9 attached: >>> 50030480002f51fd (host+target) >>> [ 5.285346] sas: ex 50030480002f51ff phy29:D:0 attached: >>> 0000000000000000 (no device) >>> [ 5.286367] sas: DONE DISCOVERY on port 0, pid:6, result:0 >>> [ 5.286426] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 >>> [ 5.286438] sas: ata5: end_device-4:0:4: dev error handler >>> [ 5.286501] sas: ata6: end_device-4:0:5: dev error handler >>> [ 5.286622] sas: ata7: end_device-4:0:6: dev error handler >>> [ 5.286717] sas: ata8: end_device-4:0:7: dev error handler >>> [ 5.286802] sas: ata9: end_device-4:0:8: dev error handler >>> [ 5.286866] sas: ata10: end_device-4:0:9: dev error handler >>> [ 5.286922] sas: ata11: end_device-4:0:10: dev error handler >>> [ 5.287008] sas: ata12: end_device-4:0:11: dev error handler >>> [ 5.287096] sas: ata13: end_device-4:0:12: dev error handler >>> [ 5.287183] sas: ata14: end_device-4:0:13: dev error handler >>> [ 5.287265] sas: ata15: end_device-4:0:14: dev error handler >> >> Right, but I actually need the configuration of the system that is >> currently oopsing. Your trace seems to show a normal SATA discovery >> (the error handler shows up because a reset fis is part of SATA >> discovery). >> >> James >> >> > Alright, rebooted with "debug ignore_loglevel", log attached. > > I'm running an Areca ARC-1320ix-16 (with onboard expander) with 10 > SATA drives attached. > (Sending again because mailing list rejects HTML) > Apparently this driver has never worked with my card (at least with SATA drives, haven't got any SAS drives to test with). I tested the first release that had the PCI ID added (2.6.32-rc4) and get the same result: no drives detected. I also tested 4.2.2 and that throws warnings on unloading the driver (full log attached). WARNING: CPU: 0 PID: 371 at fs/sysfs/group.c:224 sysfs_remove_group+0x9c/0xa0() sysfs group ffffffff81cc5680 not found for kobject 'phy-10:0:3'
Attachment:
mvsas-4.2.2.log
Description: Binary data
