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 90601] panic on write to 3ware raid array
Date: Thu, 16 Apr 2015 11:21:22 +0000	[thread overview]
Message-ID: <bug-90601-11613-FiZqAlLag2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-90601-11613@https.bugzilla.kernel.org/>

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

--- Comment #18 from merlin@liao.homelinux.org ---
Created attachment 174171
  --> https://bugzilla.kernel.org/attachment.cgi?id=174171&action=edit
dmesg

I finally managed to get a dmesg output with the crashing kernel.

Especially this part might indicate the root of the problem?
[Thu Apr 16 13:02:10 2015] ------------[ cut here ]------------
[Thu Apr 16 13:02:10 2015] WARNING: CPU: 6 PID: 1736 at lib/dma-debug.c:601
debug_dma_assert_idle+0x17c/0x1e0()
[Thu Apr 16 13:02:10 2015] 3w-sas 0000:03:00.0: DMA-API: cpu touching an active
dma mapped cacheline [cln=0x0000000101ff8e00]
[Thu Apr 16 13:02:10 2015] Modules linked in:
[Thu Apr 16 13:02:10 2015] CPU: 6 PID: 1736 Comm: mount Not tainted
4.0.0-gentoo #1
[Thu Apr 16 13:02:11 2015] Hardware name: Supermicro
X9DR7/E-(J)LN4F/X9DR7/E-(J)LN4F, BIOS 3.0a 09/10/2013
[Thu Apr 16 13:02:11 2015]  ffffffff8170e0f5 ffff88406050fcb8 ffffffff814c8778
000000000000009a
[Thu Apr 16 13:02:11 2015]  ffff88406050fd08 ffff88406050fcf8 ffffffff8107c250
ffff884060422e08
[Thu Apr 16 13:02:11 2015]  ffff8840647fe5e0 0000000000000206 ffffea00e1bf9ce8
ffff884060422e08
[Thu Apr 16 13:02:11 2015] Call Trace:
[Thu Apr 16 13:02:11 2015]  [<ffffffff814c8778>] dump_stack+0x45/0x57
[Thu Apr 16 13:02:11 2015]  [<ffffffff8107c250>] warn_slowpath_common+0x80/0xc0
[Thu Apr 16 13:02:11 2015]  [<ffffffff8107c2d1>] warn_slowpath_fmt+0x41/0x50
[Thu Apr 16 13:02:11 2015]  [<ffffffff812b9dfc>]
debug_dma_assert_idle+0x17c/0x1e0
[Thu Apr 16 13:02:11 2015]  [<ffffffff81114814>] do_wp_page+0xc4/0x810
[Thu Apr 16 13:02:11 2015]  [<ffffffff8111744c>] handle_mm_fault+0xb3c/0x10f0
[Thu Apr 16 13:02:11 2015]  [<ffffffff8111ca6d>] ? do_mmap_pgoff+0x34d/0x400
[Thu Apr 16 13:02:11 2015]  [<ffffffff81070ec6>] __do_page_fault+0x146/0x390
[Thu Apr 16 13:02:11 2015]  [<ffffffff8107114c>] do_page_fault+0xc/0x10
[Thu Apr 16 13:02:11 2015]  [<ffffffff814cf252>] page_fault+0x22/0x30
[Thu Apr 16 13:02:11 2015] ---[ end trace 326b0530baa65706 ]---


I was still able to login with root after that and reproduce the crash with
another backtrace. See the next attachment.

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

  parent reply	other threads:[~2015-04-16 11:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02 14:31 [Bug 90601] New: panic on write to 3ware raid array bugzilla-daemon
2015-01-02 14:32 ` [Bug 90601] " bugzilla-daemon
2015-01-02 14:33 ` bugzilla-daemon
2015-01-05  9:17 ` bugzilla-daemon
2015-01-06 15:28 ` bugzilla-daemon
2015-01-06 15:29 ` bugzilla-daemon
2015-01-06 15:30 ` bugzilla-daemon
2015-01-06 15:48 ` bugzilla-daemon
2015-01-21 11:51 ` bugzilla-daemon
2015-02-13  7:25 ` bugzilla-daemon
2015-02-13  7:54 ` bugzilla-daemon
2015-02-13  8:28 ` bugzilla-daemon
2015-02-13 16:20 ` bugzilla-daemon
2015-02-26  5:44 ` bugzilla-daemon
2015-02-26  7:32 ` bugzilla-daemon
2015-02-26 13:38 ` bugzilla-daemon
2015-04-13 16:16 ` bugzilla-daemon
2015-04-13 16:16 ` bugzilla-daemon
2015-04-16 11:21 ` bugzilla-daemon [this message]
2015-04-16 11:25 ` bugzilla-daemon
2015-04-16 11:25 ` bugzilla-daemon
2015-04-19  3:59 ` bugzilla-daemon
2015-04-19  4:00 ` bugzilla-daemon
2015-04-19  4:00 ` bugzilla-daemon
2015-04-19  4:04 ` bugzilla-daemon
2015-04-19  4:05 ` bugzilla-daemon
2015-04-19  4:07 ` bugzilla-daemon
2015-04-19  4:21 ` bugzilla-daemon
2015-04-20 17:43 ` bugzilla-daemon
2015-10-10  7:30 ` 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-90601-11613-FiZqAlLag2@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).