From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 187231] kernel panic during hpsa MSI plus tg3 MSI
Date: Fri, 11 Nov 2016 09:54:23 +0000 [thread overview]
Message-ID: <bug-187231-11613-yt2lu9cYjE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-187231-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=187231
--- Comment #5 from Patrick Schaaf <kernelorg@bof.de> ---
After almost 4 days my problematic box downgraded to 3.14.79, finally made some
noise, like this:
2016-11-11T03:31:10.608539+01:00 kvm3f kernel: [320020.727691] hpsa
0000:03:00.0: Abort request on C0:B0:T0:L0
2016-11-11T03:31:10.608555+01:00 kvm3f kernel: [320020.728175] hpsa
0000:03:00.0: cp ffff8868f2c17000 is reported invalid (probably means target
device no longer present)
2016-11-11T03:31:10.608557+01:00 kvm3f kernel: [320020.728796] hpsa
0000:03:00.0: cp ffff8868f2c17000 is reported invalid (probably means target
device no longer present)
2016-11-11T03:31:10.608558+01:00 kvm3f kernel: [320020.729389] hpsa
0000:03:00.0: FAILED abort on device C0:B0:T0:L0
2016-11-11T03:31:10.608560+01:00 kvm3f kernel: [320020.729708] hpsa
0000:03:00.0: resetting device 0:0:0:0
2016-11-11T03:31:26.968534+01:00 kvm3f kernel: [320037.081397] hpsa
0000:03:00.0: device is ready.
So, maybe there is a somewhat weirdly faulty drive in that array, which
otherwise does not show any (SMART / ILO logs) symptoms...
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-11-11 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 13:53 [Bug 187231] New: kernel panic during hpsa MSI plus tg3 MSI bugzilla-daemon
2016-11-07 15:25 ` [Bug 187231] " bugzilla-daemon
2016-11-07 15:45 ` bugzilla-daemon
2016-11-07 16:16 ` bugzilla-daemon
2016-11-08 16:01 ` bugzilla-daemon
2016-11-11 9:54 ` bugzilla-daemon [this message]
2016-11-16 6:17 ` 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-187231-11613-yt2lu9cYjE@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).