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 151661] Adaptec 3805 prints "AAC: Host adapter dead -1" every 10 seconds but works fine anyway
Date: Mon, 15 Aug 2016 07:17:01 +0000	[thread overview]
Message-ID: <bug-151661-11613-r7tdCw0WPF@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-151661-11613@https.bugzilla.kernel.org/>

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

Harold Snel <harold@snel.ws> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |harold@snel.ws

--- Comment #7 from Harold Snel <harold@snel.ws> ---
I have the exact same issue on my server running with an Adaptec 3405. The root
system is mounted on that controller on an SSD harddisk. Until I upgraded from
14.04 TLS to 16.04 TLS it was working fine.

After I upgraded to an new kernel first (from 4.2.0-41 to 4.2.0-42) the issue
with the 'dead adapter' started. To test if a full system upgrade to 16.04 TLS
would help I upgrade the system to that release. But on that version the
problem is still there and the system is not usable.

Now I'm running on 16.04 TLS but with the older kernel (4.2.0-41) and thats
working just fine. But I want to use the newest kernel because thats how it
should be :-)

Here is some controller info:
===
root@server:~# lspci -nnvs 03:0e.0
03:0e.0 RAID bus controller [0104]: Adaptec AAC-RAID [9005:0285]
         Subsystem: Adaptec 3405 [9005:02bb]
         Flags: bus master, stepping, 66MHz, medium devsel, latency 64, 
IRQ 18
         Memory at fda00000 (64-bit, non-prefetchable) [size=2M]
         Expansion ROM at fdcc0000 [disabled] [size=256K]
         Capabilities: [c0] Power Management version 2
         Capabilities: [d0] MSI: Enable- Count=1/2 Maskable- 64bit+
         Capabilities: [e0] PCI-X non-bridge device
         Kernel driver in use: aacraid
         Kernel modules: aacraid
===

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2016-08-15  7:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-06 21:47 [Bug 151661] New: Adaptec 3805 prints "AAC: Host adapter dead -1" every 10 seconds but works fine anyway bugzilla-daemon
2016-08-11 15:53 ` [Bug 151661] " bugzilla-daemon
2016-08-11 15:54 ` bugzilla-daemon
2016-08-11 15:55 ` bugzilla-daemon
2016-08-12  5:42 ` bugzilla-daemon
2016-08-12  6:17 ` bugzilla-daemon
2016-08-14 22:39 ` bugzilla-daemon
2016-08-15  7:17 ` bugzilla-daemon [this message]
2016-08-17 18:43 ` bugzilla-daemon
2016-08-18 21:15 ` [Bug 151661] Adaptec 3405 " bugzilla-daemon
2016-08-22 21:52 ` bugzilla-daemon
2016-08-22 21:54 ` bugzilla-daemon
2016-08-22 21:54 ` bugzilla-daemon
2016-09-04 11:25 ` bugzilla-daemon
2016-09-14 10:09 ` bugzilla-daemon
2016-09-14 10:18 ` bugzilla-daemon
2016-09-14 10:20 ` bugzilla-daemon
2016-09-14 10:22 ` bugzilla-daemon
2016-10-03 20:45 ` bugzilla-daemon
2017-01-15 11:10 ` bugzilla-daemon
2017-02-10  9:23 ` bugzilla-daemon
2017-06-21 22:43 ` bugzilla-daemon
2018-01-06 16:02 ` bugzilla-daemon
2018-01-08 17:44 ` 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-151661-11613-r7tdCw0WPF@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).