All of lore.kernel.org
 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, 26 Feb 2015 05:44:47 +0000	[thread overview]
Message-ID: <bug-90601-11613-q1jChMQq1l@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 #13 from kashyap <kashyap.desai@avagotech.com> ---
My old email id is not working now, so I have to update my email id to new
avagotech domain. Sorry for delay in response.

Does this mean issue does not happen with 3.16.1 
but only happens with 3.17.1 (onwards) ? This is good data point.

Can you share whole dmesg logs for both 3.16.1 and 3.17.1 ?

Also are you using intel_iommu=on in your config ? Can you boot without
enabling Intel IOMMU? 

New logs with ""CONFIG_DMA_API_DEBUG" does not help much. You may have to post
complete logs. We may have some interesting data before crash.

Thanks, Kashyap

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

  parent reply	other threads:[~2015-02-26  5:44 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 [this message]
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
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-q1jChMQq1l@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 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.