From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 16547] mptscsih: ioc0: attempting task abort, raid array LUNs not detected properly on some boots
Date: Thu, 16 Sep 2010 06:03:35 GMT [thread overview]
Message-ID: <201009160603.o8G63ZLL004875@demeter2.kernel.org> (raw)
In-Reply-To: <bug-16547-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16547
kdesai <kashyap.desai@lsi.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kashyap.desai@lsi.com
--- Comment #5 from kdesai <kashyap.desai@lsi.com> 2010-09-16 06:03:33 ---
(In reply to comment #3)
> Some additional information on the MPT driver version and controller:
>
> backend01:~# grep -r "" /proc/mpt/*
> /proc/mpt/ioc0/summary:ioc0: LSIFC949E A1, FwRev=01030e00h, Ports=1, MaxQ=1023,
> LanAddr=00:06:[...], IRQ=33
> /proc/mpt/ioc0/info:ioc0:
> /proc/mpt/ioc0/info: ProductID = 0x1005 (LSIFC949E A1)
> /proc/mpt/ioc0/info: FWVersion = 0x01030e00 (fw_size=190556)
> /proc/mpt/ioc0/info: MsgVersion = 0x0105
> /proc/mpt/ioc0/info: FirstWhoInit = 0x00
> /proc/mpt/ioc0/info: EventState = 0x00
> /proc/mpt/ioc0/info: CurrentHostMfaHighAddr = 0x00000004
> /proc/mpt/ioc0/info: CurrentSenseBufferHighAddr = 0x00000004
> /proc/mpt/ioc0/info: MaxChainDepth = 0x3e frames
> /proc/mpt/ioc0/info: MinBlockSize = 0x20 bytes
> /proc/mpt/ioc0/info: RequestFrames @ 0xffff88043c102800 (Dma @
> 0x000000043c102800)
> /proc/mpt/ioc0/info: {CurReqSz=128} x {CurReqDepth=1023} = 130944 bytes ^=
> 0x20000
> /proc/mpt/ioc0/info: {MaxReqSz=128} {MaxReqDepth=1023}
> /proc/mpt/ioc0/info: Frames @ 0xffff88043c100000 (Dma @ 0x000000043c100000)
> /proc/mpt/ioc0/info: {CurRepSz=80} x {CurRepDepth=128} = 10240 bytes ^=
> 0x2880
> /proc/mpt/ioc0/info: {MaxRepSz=0} {MaxRepDepth=1023}
> /proc/mpt/ioc0/info: MaxDevices = 255
> /proc/mpt/ioc0/info: MaxBuses = 2
> /proc/mpt/ioc0/info: PortNumber = 1 (of 1)
> /proc/mpt/ioc0/info: LanAddr = 00:06:[...]
> /proc/mpt/ioc0/info: WWN = 2000[...]
> /proc/mpt/ioc1/summary:ioc1: LSIFC949E A1, FwRev=01030e00h, Ports=1, MaxQ=1023,
> LanAddr=00:06:2B:11:3B:79, IRQ=31
> /proc/mpt/ioc1/info:ioc1:
> /proc/mpt/ioc1/info: ProductID = 0x1005 (LSIFC949E A1)
> /proc/mpt/ioc1/info: FWVersion = 0x01030e00 (fw_size=190556)
> /proc/mpt/ioc1/info: MsgVersion = 0x0105
> /proc/mpt/ioc1/info: FirstWhoInit = 0x00
> /proc/mpt/ioc1/info: EventState = 0x00
> /proc/mpt/ioc1/info: CurrentHostMfaHighAddr = 0x00000004
> /proc/mpt/ioc1/info: CurrentSenseBufferHighAddr = 0x00000004
> /proc/mpt/ioc1/info: MaxChainDepth = 0x3e frames
> /proc/mpt/ioc1/info: MinBlockSize = 0x20 bytes
> /proc/mpt/ioc1/info: RequestFrames @ 0xffff88043c202800 (Dma @
> 0x000000043c202800)
> /proc/mpt/ioc1/info: {CurReqSz=128} x {CurReqDepth=1023} = 130944 bytes ^=
> 0x20000
> /proc/mpt/ioc1/info: {MaxReqSz=128} {MaxReqDepth=1023}
> /proc/mpt/ioc1/info: Frames @ 0xffff88043c200000 (Dma @ 0x000000043c200000)
> /proc/mpt/ioc1/info: {CurRepSz=80} x {CurRepDepth=128} = 10240 bytes ^=
> 0x2880
> /proc/mpt/ioc1/info: {MaxRepSz=0} {MaxRepDepth=1023}
> /proc/mpt/ioc1/info: MaxDevices = 255
> /proc/mpt/ioc1/info: MaxBuses = 2
> /proc/mpt/ioc1/info: PortNumber = 1 (of 1)
> /proc/mpt/ioc1/info: LanAddr = 00:06:[...]
> /proc/mpt/ioc1/info: WWN = 2000[...]
> /proc/mpt/summary:ioc0: LSIFC949E A1, FwRev=01030e00h, Ports=1, MaxQ=1023,
> LanAddr=00:06:2B:11:3B:78, IRQ=33
> /proc/mpt/summary:ioc1: LSIFC949E A1, FwRev=01030e00h, Ports=1, MaxQ=1023,
> LanAddr=00:06:2B:11:3B:79, IRQ=31
> /proc/mpt/version:mptlinux-3.04.12
> /proc/mpt/version: Fusion MPT base driver
> /proc/mpt/version: Fusion MPT FC host driver
Your bug is completely different issue. Whatever you are point to redhat
bugzilla is with respect to SAS controller.
In your case it is FC controller.
You have mentioned that
"Latest kernel known to work: 2.6.26 from Debian Backports"
Can you provide me driver version where things are working fine. In case of
some working kernel is there, I would like to simply upgrade MPTFUSION driver
(do not upgrade a whole kernel). This way I would like to change only one
component of the system at a time...
This will help to understand where things are broken.
FYI,
MPTFC drive is highly in mentionation mode. There are very very minimal changes
happened to MPTFC driver since 2008.
Last change went to upstream for MPTFC is
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=03cb3829e0e5650518ce37e2b4420a35e034dc9e
Thanks, Kashyap
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-09-16 7:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 9:22 [Bug 16547] New: mptscsih: ioc0: attempting task abort, raid array not detected properly on some boots bugzilla-daemon
2010-08-09 9:24 ` [Bug 16547] " bugzilla-daemon
2010-08-09 9:34 ` [Bug 16547] mptscsih: ioc0: attempting task abort, raid array LUNs " bugzilla-daemon
2010-08-09 9:35 ` bugzilla-daemon
2010-08-09 9:46 ` bugzilla-daemon
2010-09-12 11:08 ` bugzilla-daemon
2010-09-16 6:03 ` bugzilla-daemon [this message]
2010-09-16 6:05 ` bugzilla-daemon
2010-09-21 8:12 ` bugzilla-daemon
2010-09-21 13:23 ` bugzilla-daemon
2012-05-12 0:05 ` bugzilla-daemon
2013-12-10 21:54 ` 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=201009160603.o8G63ZLL004875@demeter2.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.