Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 9 Sep 2002 15:30:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 9 Sep 2002 15:30:51 -0400 Received: from e31.co.us.ibm.com ([32.97.110.129]:15094 "EHLO e31.co.us.ibm.com") by vger.kernel.org with ESMTP id ; Mon, 9 Sep 2002 15:30:50 -0400 Subject: New failures in nightly LTP test From: Paul Larson To: lkml Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 09 Sep 2002 14:22:55 -0500 Message-Id: <1031599375.30394.43.camel@plars.austin.ibm.com> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1177 Lines: 33 The nightly LTP test against the 2.5 kernel bk tree last night turned up some test failures we don't normally see. These failures did not show up in the run from the previous night. execve06 0 INFO : Test FAILED getpgid01 0 INFO : getpgid01 FAILED mprotect03 1 FAIL : child returned unexpected status All three are showing warnings that look like this before the failure: mprotect03 0 WARN : signal() failed for signal 41. error:22 Invalid argument. mprotect03 0 WARN : signal() failed for signal 51. error:22 Invalid argument. The beginning changeset was: ChangeSet@1.632, 2002-09-08 08:23:34-07:00, ink@jurassic.park.msu.ru [PATCH] pci bus resources, transparent bridges The ending changeset was: ChangeSet@1.641, 2002-09-08 20:04:56-07:00, mingo@elte.hu [PATCH] Re: pinpointed: PANIC caused by dequeue_signal() in current Linus Any ideas on what may be causing this? Thanks, Paul Larson - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/