From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: alexey.kodanev@oracle.com
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] tpci test trigger RHEL6.4GA crash!
Date: Tue, 29 Oct 2013 17:05:41 +0800 [thread overview]
Message-ID: <526F7A65.7010206@cn.fujitsu.com> (raw)
In-Reply-To: <526F779B.2030205@oracle.com>
On 10/29/2013 04:53 PM, alexey.kodanev@oracle.com wrote:
> Hi!
> On 10/28/2013 12:44 PM, Zeng Linggang wrote:
>> Hi,
>>
>> When we execute the test of tpci in RHEL6.4GA, the system will crash:
>> - filesystem is broken
>> - network is off
>> Some logs are as follows:
>>
>> [root@RHEL6U4GA-Intel64 ltp]# ata1.00: exception Emask 0x52 SAct 0x1 SErr 0xffffffff action 0xe frozen
>> ata1: SError: { RecovData RecovCommon UnrecovData Persist Proto HostInt PHYInt CommWake 10B8B Display
>> Seq TrStaTrns UnrecFIS DevExch }
>> ata1.00: failed command: WRITE FPDMA QUEUED
>> ata1.00: cmd 61/08:00:c8:fb:f3/00:00:39:00:00/40 tag 0 ncq 4096 out
>> res 40/00:18:48:eb:33/00:00:38:00:00/40 Emask 0x56 (ATA bus error)
>> ata1.00: stauts: { DRDY }
>> ata1.00 failed to resume link (SControl FFFFFFFF)
>> ata1.00 failed to resume link (SControl FFFFFFFF)
>> ata1.00 failed to resume link (SControl FFFFFFFF)
>> Buffer I/O error on device sda13, logical block 4752991
>> sd 0:0:0:0: rejecting I/O to offline device
>> sd 0:0:0:0: rejecting I/O to offline device
>> ...
>> EXT4-fs error (device sda13): ext4_find_entry: reading directory #524297 offset 0
>> EXT4-fs error (device sda13): ext4_find_entry: reading directory #524297 offset 0
>> ...
>>
> Could you please find out which particular test case does it? it can be
> done manually the following way:
> insmod ltp_pci.ko
>
> Get your ata bus and pci slot number, then write it to the file (the
> number is 16bit unsigned integer, the first 8 bits is a device number,
> the last is a bus number):
>
> echo "number" > /sys/devices/ltp_tcpi/bus_slot
>
> Then try test-cases one by one:
> echo 1 > /sys/devices/ltp_tcpi/tcase
> ...
> echo 17 > /sys/devices/ltp_tcpi/tcase
>
> You can check the result of each test case by reading
> /sys/devices/ltp_tcpi/result file. 0 - PASS, 1 - FAIL.
PCI_RESOURCES, will cause kernel crash, could you please
check it?
Thanks,
Wanlong Gao
>
> Thanks,
> Alexey
>
> ------------------------------------------------------------------------------
> Android is increasing in popularity, but the open development platform that
> developers love is also attractive to malware creators. Download this white
> paper to learn more about secure code signing practices that can help keep
> Android apps secure.
> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next parent reply other threads:[~2013-10-29 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1382949890.5455.40.camel@fedora19>
[not found] ` <526F779B.2030205@oracle.com>
2013-10-29 9:05 ` Wanlong Gao [this message]
2013-10-30 3:35 ` [LTP] tpci test trigger RHEL6.4GA crash! Wanlong Gao
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=526F7A65.7010206@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=alexey.kodanev@oracle.com \
--cc=ltp-list@lists.sourceforge.net \
/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