linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 31212] New: aacraid is generally unstable with newer kernels
Date: Wed, 16 Mar 2011 17:43:58 GMT	[thread overview]
Message-ID: <bug-31212-11613@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=31212

           Summary: aacraid is generally unstable with newer kernels
           Product: SCSI Drivers
           Version: 2.5
    Kernel Version: 2.6.32, 2.6.37.3
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: AACRAID
        AssignedTo: scsi_drivers-aacraid@kernel-bugs.osdl.org
        ReportedBy: nemesis@icequake.net
        Regression: No


Created an attachment (id=50962)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=50962)
dmesg

I have a HP DL380 with an Adaptec 2120S that, many moons ago, never exhibited
any problems.  Since lenny and squeeze I have had frequent "Host adapter abort
request" messages followed by a RAID firmware panic under heavy disk I/O.  In
2.6.32 it seemed impossible to recover from these things, it would offline the
RAID and disable the system.  In 2.6.37.3 it seems better at recovering after a
delay, but I am afraid something is wrong at a low level that may corrupt data:

[572820.064043] aacraid: Host adapter abort request (2,0,0,0)
[572820.149996] aacraid: Host adapter abort request (2,0,0,0)
[572820.235786] aacraid: Host adapter abort request (2,0,0,0)
[572820.321554] aacraid: Host adapter abort request (2,0,0,0)
[572820.407418] aacraid: Host adapter reset request. SCSI hang ?
[572820.496444] AAC: Host adapter BLINK LED 0x3
[572820.567966] AAC0: adapter kernel panic'd 3.
[595047.992045] aacraid: Host adapter abort request (2,0,0,0)
[595048.078463] aacraid: Host adapter abort request (2,0,0,0)
[595048.164959] aacraid: Host adapter abort request (2,0,0,0)
[595048.250844] aacraid: Host adapter abort request (2,0,0,0)
[595048.336629] aacraid: Host adapter abort request (2,0,0,0)
[595048.336637] aacraid: Host adapter abort request (2,0,0,0)
[595048.336644] aacraid: Host adapter abort request (2,0,0,0)
[595048.336650] aacraid: Host adapter abort request (2,0,0,0)
[595048.336657] aacraid: Host adapter abort request (2,0,0,0)
[595048.336663] aacraid: Host adapter abort request (2,0,0,0)
[595048.336773] aacraid: Host adapter reset request. SCSI hang ?
[595048.336782] AAC: Host adapter BLINK LED 0x3
[595048.336916] AAC0: adapter kernel panic'd 3.
[596524.064044] aacraid: Host adapter abort request (2,0,0,0)
[596524.146368] aacraid: Host adapter abort request (2,0,0,0)
[596524.228197] aacraid: Host adapter abort request (2,0,0,0)
[596524.309288] aacraid: Host adapter abort request (2,0,0,0)
[596524.389967] aacraid: Host adapter reset request. SCSI hang ?
[596524.473168] AAC: Host adapter BLINK LED 0x3
[596524.538332] AAC0: adapter kernel panic'd 3.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2011-03-16 17:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 17:43 bugzilla-daemon [this message]
2011-03-16 17:44 ` [Bug 31212] aacraid is generally unstable with newer kernels bugzilla-daemon
2011-03-16 17:45 ` bugzilla-daemon
2011-03-16 17:48 ` bugzilla-daemon
2011-03-17 17:02 ` bugzilla-daemon
2011-03-17 17:02 ` bugzilla-daemon
2011-04-06 23:56 ` bugzilla-daemon
2012-05-29 22:59 ` bugzilla-daemon
2012-11-04 16:05 ` bugzilla-daemon
2012-12-25  9:31 ` bugzilla-daemon
2012-12-25  9:32 ` bugzilla-daemon
2012-12-25  9:33 ` bugzilla-daemon
2012-12-25  9:44 ` bugzilla-daemon
2013-04-28  8:45 ` 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=bug-31212-11613@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).