From: Jack Wang <xjtuwjp@gmail.com>
To: Evgeny <sys64@inbox.ru>
Cc: linux-scsi@vger.kernel.org
Subject: Re: aic94xx and kernel panic
Date: Mon, 19 Aug 2013 14:25:43 +0200 [thread overview]
Message-ID: <52120EC7.60800@gmail.com> (raw)
In-Reply-To: <521200DA.5020601@inbox.ru>
On 08/19/2013 01:26 PM, Evgeny wrote:
> I've tried 3.10.2 and it's also affected.
>
> Could you recommend something else?
Could you enable LIST_DEBUG in your kernel hacking and retry?
It looks like it bug_on list not empty as expected, some ascb->list may
need
&asd_ha->seq.pend_q_lock protection, you need to figure out your self.
PS: the aic94xx is out of maintain for some years as I see. You may need
to update to newer hardware.
Jack
>
>
> 19.08.2013 12:03, Jack Wang пишет:
>> On 08/16/2013 10:26 AM, Evgeny wrote:
>>> Hello.
>>>
>>> I've been testing vanilla 3.4.45 (config attached), 3.4.56 kernels on
>>> centos 5.9 with Adaptec AIC-9410W SAS controller:
>> There's some fix in libsas about error handle , As I remember most of
>> patch finally merged in 3.7, could you try newer kernel?
>>
>> KR
>> Jack
>>> ------------
>>> 09:02.0 RAID bus controller: Adaptec AIC-9410W SAS (Razor ASIC RAID)
>>> (rev 09)
>>> Subsystem: Super Micro Computer Inc Device 9280
>>> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+
>>> Stepping- SERR+ FastB2B- DisINTx-
>>> Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort-
>>> <TAbort- <MAbort- >SERR- <PERR- INTx-
>>> Latency: 64 (32000ns min, 26750ns max), Cache Line Size: 32 bytes
>>> Interrupt: pin A routed to IRQ 18
>>> Region 0: Memory at d8300000 (64-bit, non-prefetchable) [size=256K]
>>> Region 2: Memory at d8000000 (64-bit, prefetchable) [size=128K]
>>> Region 4: I/O ports at 3000 [size=256]
>>> [virtual] Expansion ROM at d8080000 [disabled] [size=512K]
>>> Capabilities: [40] PCI-X non-bridge device
>>> Command: DPERE- ERO- RBC=4096 OST=8
>>> Status: Dev=09:02.0 64bit+ 133MHz+ SCD- USC- DC=simple
>>> DMMRBC=4096 DMOST=8 DMCRS=128 RSCEM- 266MHz- 533MHz-
>>> Capabilities: [58] Power Management version 2
>>> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
>>> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>>> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
>>> Capabilities: [e0] MSI: Enable- Count=1/4 Maskable- 64bit+
>>> Address: 0000000000000000 Data: 0000
>>> Kernel driver in use: aic94xx
>>> Kernel modules: aic94xx
>>> ----------
>>>
>>> Under a heavy load made by bonnie:
>>>
>>> ----------
>>> bonnie++ -d /tmp/test -x 10000 -s 24g -u root
>>> ----------
>>>
>>> after 8-14 hours system gets kernel panic (log attached).
>>>
>>> Could anyone help with it?
>>>
>>>
>>> Thanks!
>>> Evgeny
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-08-19 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 8:26 aic94xx and kernel panic Evgeny
2013-08-19 8:03 ` Jack Wang
2013-08-19 11:26 ` Evgeny
2013-08-19 12:25 ` Jack Wang [this message]
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=52120EC7.60800@gmail.com \
--to=xjtuwjp@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sys64@inbox.ru \
/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).