similar to: CentOS 7.4 paniced when running LTP tests

Displaying 20 results from an estimated 80 matches similar to: "CentOS 7.4 paniced when running LTP tests"

2007 Oct 11
0
Vista crashed when do the ltp memory testing under domain 0
Hello, When run x86_32 SMP Vista HVM guest and run LTP memory stress testing under domain 0, after some time, vista will blue screen with this message:"a clock interrupt was not received on a secondary processor within the allocated time interval" with Bug Check 0x101. This issue can also be reproduced copy big files under vista for a long time.( not alway ). Could anyone give some
2012 Jan 10
0
ltp hugemmap02 fails on ocfs2
Hi Tiger, ltp-20120104 hugemmap02 testcase fails on ocfs2 filesystem with both UEK 2.6.39-100.0.18 and RHEL 2.6.18-300.el5: hugemmap02 1 TCONF : huge mmap failed to test the scenario hugemmap02 1 TCONF : huge mmap failed to test the scenario hugemmap02 0 TWARN : tst_rmdir: rmobj(/mnt/ocfs2/ltp-mQdlAx5411/hugSJXB0B) failed: lstat(/mnt/ocfs2/ltp-mQdlAx5411/hugSJXB0B) failed;
2004 Aug 17
0
[BUG] LTP:mkdir try to inherits S_ISGID failed
This bug has the same reproduce step as below. the dir2 has no S_ISGID set. see bug 131. >-----Original Message----- >From: ocfs2-devel-bounces@oss.oracle.com=20 >[mailto:ocfs2-devel-bounces@oss.oracle.com] On Behalf Of Ling, Xiaofeng >Sent: 2004=C4=EA8=D4=C218=C8=D5 9:45 >To: ocfs2-devel@oss.oracle.com >Subject: [Ocfs2-devel] [BUG] LTP:mkdir try to inherits group id failed >
2006 Oct 05
1
ltp.c best_pitch vs. pitch
Hi there, I was browsing the speex code when I stumbled across something I could not understand the reason, and thought maybe it was a bug? In LTP.C function pitch_search_3tap, after searching for the best pitch candidate, the function returns the last pitch candidate rather than the best pitch candidate, is this normal? kind regards, Sufian
2004 Apr 08
0
ltp test result for ocfs2 for 2.4
This is the test result on 2.4.20 kernel, it is much like the result on 2.6.3 kernel. Both hang on rmdir03. Anther result is when on a SMP kernel of 2.4.20 on UP machine, the test crashs on "create" test. > -----Original Message----- > From: ocfs2-devel-bounces@oss.oracle.com > [mailto:ocfs2-devel-bounces@oss.oracle.com] On Behalf Of > Ling, Xiaofeng > Sent:
2004 Aug 18
4
LTP system call test all pass!
After fix bug 130 and 131, and some LTP bugs. ocfs2 can now pass all LTP filesystem related system call testcases. detail result see attach. ------------------- Intel China Software Lab. iNet: 8-752-1243 8621-52574545-1243(O) xfling@users.sourceforge.net Opinions are my own and don't represent those of my employer -------------- next part -------------- A non-text attachment was
2004 Aug 17
1
[Bug] LTP: mkdir fail after setreuid
For chdir03 investigation result: The fail is caused by the mkdir fail after setreuid. Key code in the test case: if ((pid =3D fork()) < 0) { tst_brkm(TBROK, cleanup, "first fork failed"); } if (pid =3D=3D 0) { /* first child */ /* set the child's ID to ltpuser1 */ if (setreuid(ltpuser1->pw_uid,
2011 Jan 19
0
Bug#603727: xen-hypervisor-4.0-amd64: i386 Dom0 crashes after doing some I/O on local storage (software Raid1 on SAS-drives with mpt2sas driver)
I have the exact same issue on several Sunfire v20z (hardware LSI RAID controler). Under high IO load, the raid controler starts complaining with disk errors : [163442.483878] mptbase: ioc0: LogInfo(0x11070000): F/W: DMA Error [163445.172333] sd 2:0:0:0: [sda] Unhandled error code [163445.172338] sd 2:0:0:0: [sda] Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK [163445.172345] sd 2:0:0:0:
2006 May 08
1
hardware support
We have had some problems bringing up SLES10/Xen on DL360 box (dual processor). The Compaq boxes have this notion of "auto" mode for MPS/APIC to deal with buggy OSes and under this setting (which is the default setting), vanilla Linux (2.6.16) comes up on this box in UP mode since it finds the local APIC disabled in bios. However, the xen based kernel tries to come up MP and fails in a
2020 Feb 14
1
[PATCH 1/2] virtio-blk: fix hw_queue stopped on arbitrary error
Hi Halil, When swiotlb full is hit for virtio_blk, there is below warning for once (the warning is not by this patch set). Is this expected or just false positive? [ 54.767257] virtio-pci 0000:00:04.0: swiotlb buffer is full (sz: 16 bytes), total 32768 (slots), used 258 (slots) [ 54.767260] virtio-pci 0000:00:04.0: overflow 0x0000000075770110+16 of DMA mask ffffffffffffffff bus limit 0 [
2018 Mar 27
0
BUG: corrupted list in remove_wait_queue
On 2018?03?24? 20:32, syzbot wrote: > syzbot has found reproducer for the following crash on upstream commit > 99fec39e7725d091c94d1bb0242e40c8092994f6 (Fri Mar 23 22:34:18 2018 +0000) > Merge tag 'trace-v4.16-rc4' of > git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace > syzbot dashboard link: >
2014 Nov 10
0
kernel BUG at drivers/block/virtio_blk.c:172
On Fri, 31 Oct 2014, Ming Lei wrote: > Date: Fri, 31 Oct 2014 12:40:00 +0800 > From: Ming Lei <tom.leiming at gmail.com> > To: Jens Axboe <axboe at kernel.dk> > Cc: Luk?? Czerner <lczerner at redhat.com>, > Linux Virtualization <virtualization at lists.linux-foundation.org>, > Christoph Hellwig <hch at lst.de> > Subject: Re: Re: kernel
2013 Jun 10
1
btrfs-cleaner Blocked on xfstests 068
I''m running into a problem with the btrfs-cleaner thread becoming blocked on xfstests 068. The test locks up indefinitely without completing (normally it finished in about 45 seconds on my test box). I''ve replicated the issue on 3.10.0_rc5 and the for-linus branch of 3.9.0. I ran a git bisect on the 3.9.0 for-linus branch, and tracked my issue to the following commit: commit
2006 Oct 31
0
6397933 fs node paniced while mounting global filesystem (/global/.devices/node@x)
Author: rsb Repository: /hg/zfs-crypto/gate Revision: 7a6414a00f773a4c3f71b22bcbef215513abc919 Log message: 6397933 fs node paniced while mounting global filesystem (/global/.devices/node at x) Files: update: usr/src/uts/common/fs/vfs.c
2003 Jun 20
2
Zsh fork bomb paniced my kernel.
Hi, My machine just bombed when I did the following stupid command. :(){:|:};: Zsh chewed up everything on the machine... I ran it knowing I'd probably have to reboot. But, I hardly expected it to panic. Or, was that normal? Anyway, the following is some detail... Please mail me if there is more I'm ment to do. Thanks in advance :) ultraviolet@tulip:~ %> uname -a FreeBSD
2013 Jun 30
1
locks under printf(9) and WITNESS = panic?
when booting stable/9 under a debug kernel with WITNESS enabled and verbose I get the following panic.. It seems very much like the discussion from a year back on current: http://lists.freebsd.org/pipermail/freebsd-current/2012-January/031375.html Any ideas? uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1 uhub0: 2 ports with 2 removable, self powered uhub1: 2
2013 Sep 27
1
lock order reversal in 10-alpha2
After booting from a 10-alpha2 disk I am seeing "lock order reversal" messages show up from time to time. Current logs have 35 entries. The machine normally is running 9.1 from zfs root and I have setup a separate disk (eSATA case connected through backplane port to onboard SATA port) that I have installed 10-alpha amd64 onto a ufs partition to test port building with. I started by
2008 May 10
2
kernel- 2.6.25.3 + xen 3.2
Hi Does anyone uses 2.6.25-3 kernel and xen-3.2? I have a problem with kernel 2.6.24. I find some patch for this kernel? Regards, Albert _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2004 Oct 21
0
compile errors samba 3.0.7 vfs
Hi all, sorry for the long posting. Samba 2.2.x is outdated. Trying to switch to 3.0.7 with no success. The vfs layer is one of my current problems. Googled some time for an solution for this: [2004/10/21 20:04:00, 0] smbd/server.c:main(760) smbd version 3.0.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2004 [2004/10/21 22:12:07, 0] smbd/server.c:main(760) smbd version
2003 Mar 22
0
ext3 oops with 2.4.20
Bug report follows. Please CC me if you want me to read the reply, as I'm not subscribed to ext3-users. [1.] One line summary of the problem: Ext3 has just causing filesystem corruption which required fsck to fix. [2.] Full description of the problem/report: I just had my machine lock up with an ext3 oops, preceeded by a bunch of error messages in the logs. On rebooting, after replaying the