From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 90601] panic on write to 3ware raid array
Date: Mon, 05 Jan 2015 09:17:03 +0000 [thread overview]
Message-ID: <bug-90601-11613-2xPWZsajkH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-90601-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=90601
kashyap <kashyap.desai@lsi.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kashyap.desai@lsi.com
--- Comment #3 from kashyap <kashyap.desai@lsi.com> ---
Merlin,
1.)
Can you enable CONFIG_DMA_API_DEBUG in your kernel conf and send complete
/var/log/messages along with back trace.
2.)
>From existing logs I can figure out that crash happened at below place.
static void intel_unmap_sg(struct device *dev, struct scatterlist *sglist,
int nelems, enum dma_data_direction dir,
struct dma_attrs *attrs)
{
intel_unmap(dev, sglist[0].dma_address);
}
sglist[0] is NULL and while accessing dma_address (which is 0x10th index as per
below definition)
struct scatterlist {
#ifdef CONFIG_DEBUG_SG
unsigned long sg_magic;
#endif
unsigned long page_link;
unsigned int offset;
unsigned int length;
dma_addr_t dma_address; < -- 0x10th index
#ifdef CONFIG_NEED_SG_DMA_LENGTH
unsigned int dma_length;
#endif
};
Crash detail -
[ 1005.899543] Hardware name: Supermicro X9DR7/E-(J)LN4F/X9DR7/E-(J)LN4F, BIOS
3.0a 09/10/2013
[ 1005.899971] task: ffffffff8160a460 ti: ffffffff815f4000 task.ti:
ffffffff815f4000
[ 1005.900401] RIP: 0010:[<ffffffff813db181>] [<ffffffff813db181>]
intel_unmap_sg+0x1/0x10
~ kashyap
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2015-01-05 9:17 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 [this message]
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
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-2xPWZsajkH@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).