All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <arekm@maven.pl>
To: linux-scsi@vger.kernel.org
Cc: aacraid@adaptec.com
Subject: adaptec 3405 + 4 sas disks: synchronize_callback: synchronize failed, status = 226
Date: Mon, 14 Jul 2008 08:09:19 +0200	[thread overview]
Message-ID: <200807140809.19937.arekm@maven.pl> (raw)


Hello,

I'm running 2.6.24.3 kernel and I'm getting few error messages comming from 
aacraid driver. Hardware is adaptec 3405 running firmware 15728 + 4 SAS 300GB 
harddisks configured in single raid10 array.

[167674.161866] synchronize_callback: synchronize failed, status = 226
[168977.738031] synchronize_callback: synchronize failed, status = 226
[172180.752140] synchronize_callback: synchronize failed, status = 226
[177494.855145] synchronize_callback: synchronize failed, status = 226
[189594.477223] synchronize_callback: synchronize failed, status = 226
[191411.881236] synchronize_callback: synchronize failed, status = 226
[217130.596663] synchronize_callback: synchronize failed, status = 226
[219236.032362] synchronize_callback: synchronize failed, status = 226

What does 226 mean and what does it indicate (serious problem?) ?

ps. would be good if prefix was added to these messages to know where these 
come from
-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2008-07-14  6:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14  6:09 Arkadiusz Miskiewicz [this message]
2008-07-14 11:19 ` adaptec 3405 + 4 sas disks: synchronize_callback: synchronize failed, status = 226 Mark Salyzyn
2008-07-14 11:45   ` Arkadiusz Miskiewicz

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=200807140809.19937.arekm@maven.pl \
    --to=arekm@maven.pl \
    --cc=aacraid@adaptec.com \
    --cc=linux-scsi@vger.kernel.org \
    /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.