All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Adam Talbot <ajtalbot1@gmail.com>
Cc: Nathan Rennie-Waldock <nathan.renniewaldock@gmail.com>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [Bug 81861] Oops by mvsas v0.8.16: sas: ataX: end_device-Y:0:Z: dev error handler -> general protection fault, RIP: mvs_task_prep_ata+0x80/0x3a0
Date: Wed, 29 Apr 2015 11:05:00 -0700	[thread overview]
Message-ID: <1430330700.2189.17.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAH_2GhcOwjQqD0VYqMiD9UGRsYf4L-XRPaMHwPiRR1c2-PSQ7A@mail.gmail.com>

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



  reply	other threads:[~2015-04-29 18:05 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 17:33 [Bug 81861] New: mvsas.ko v0.8.16 error messages and kernel crashes attaching 4 SATA drives to specific HP SAS expander ports bugzilla-daemon
2014-08-07 20:29 ` [Bug 81861] " bugzilla-daemon
2014-08-08  8:19 ` bugzilla-daemon
2014-08-08  8:24 ` [Bug 81861] Oops by mvsas v0.8.16: sas: ataX: end_device-Y:0:Z: dev error handler -> general protection fault, RIP: mvs_task_prep_ata+0x80/0x3a0 bugzilla-daemon
2014-08-08  8:34 ` bugzilla-daemon
2014-08-12 20:09 ` bugzilla-daemon
2014-08-12 22:02 ` bugzilla-daemon
2014-08-21 18:35 ` bugzilla-daemon
2014-08-22 12:13 ` bugzilla-daemon
2014-08-22 12:16 ` bugzilla-daemon
2014-08-22 12:17 ` bugzilla-daemon
2014-08-22 13:19 ` bugzilla-daemon
2014-08-22 14:05 ` bugzilla-daemon
2014-08-22 17:00 ` bugzilla-daemon
2014-08-22 17:36 ` bugzilla-daemon
2014-08-23 20:04 ` bugzilla-daemon
2014-08-23 20:06 ` bugzilla-daemon
2014-08-23 22:12 ` bugzilla-daemon
2014-09-23 21:56 ` bugzilla-daemon
2014-09-24  0:32   ` Elliott, Robert (Server Storage)
2014-09-26  7:04 ` bugzilla-daemon
2014-10-19 15:56 ` bugzilla-daemon
2014-12-17 19:49 ` bugzilla-daemon
2015-01-26 23:19 ` bugzilla-daemon
2015-01-26 23:20 ` bugzilla-daemon
2015-01-26 23:21 ` bugzilla-daemon
2015-04-23 11:31 ` bugzilla-daemon
2015-04-29 13:40 ` bugzilla-daemon
2015-04-29 14:20   ` James Bottomley
     [not found]     ` <CAC2CY-2YAy8GfjCHO+PrFWAuBnhfnMvK33KJ3YCVRZXJMEHykQ@mail.gmail.com>
2015-04-29 15:41       ` James Bottomley
2015-04-29 16:24         ` Adam Talbot
2015-04-29 18:05           ` James Bottomley [this message]
2015-04-29 18:07             ` Adam Talbot
2015-04-29 18:10               ` James Bottomley
2015-04-29 19:09             ` Nathan Rennie-Waldock
2015-10-05  0:07               ` Nathan Rennie-Waldock
2015-04-29 13:41 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1430330700.2189.17.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=ajtalbot1@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nathan.renniewaldock@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.