From owner-freebsd-questions  Thu Jul  3 01:18:04 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA28031
          for questions-outgoing; Thu, 3 Jul 1997 01:18:04 -0700 (PDT)
Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA28025
          for <freebsd-questions@FreeBSD.ORG>; Thu, 3 Jul 1997 01:18:02 -0700 (PDT)
Received: from gil.physik.rwth-aachen.de ([137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12)
	with ESMTP id KAA16514; Thu, 3 Jul 1997 10:18:13 +0200 (MET DST)
Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id KAA24663; Thu, 3 Jul 1997 10:17:50 +0200 (MEST)
Message-ID: <19970703101750.10209@gil.physik.rwth-aachen.de>
Date: Thu, 3 Jul 1997 10:17:50 +0200
From: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de>
To: "Riley J. McIntire" <rileyj@train.tgci.com>
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: Core dump signal 11
References: <199707022221.PAA10403@train.tgci.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.75e
In-Reply-To: <199707022221.PAA10403@train.tgci.com>; from Riley J. McIntire on Wed, Jul 02, 1997 at 03:24:06PM +0000
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, Jul 02, 1997 at 03:24:06PM +0000, Riley J. McIntire wrote:
> Hi,
> 
> On a 2.2.2-R machine I put together a few weeks ago and walked 
> away from for a while I just noticed:
> 
> Jun 24 15:00:01 moat /kernal: pid 20869 (atrun), uid 0: exited on siganl 11 (core 
> dumped)

I grep'ed through the l;ogs of one of my 'cumber' machines
(3.0-current of 0505) and found a lot of those in conjunction with a
corrupt /var FS.

Jun 30 09:00:00 toots /kernel: pid 6653 (atrun), uid 0: exited on signal 11
(core dumped)
Jun 30 09:05:00 toots /kernel: pid 6662 (atrun), uid 0: exited on signal 11
 (core dumped)
Jun 30 09:10:00 toots /kernel: pid 6668 (atrun), uid 0: exited on signal 11
 (core dumped)
Jun 30 09:15:00 toots /kernel: pid 6677 (atrun), uid 0: exited on signal 11 
(core dumped)
Jun 30 09:20:00 toots /kernel: pid 6686 (atrun), uid 0: exited on signal 11 
(core dumped)
Jun 30 09:25:00 toots /kernel: pid 6691 (atrun), uid 0: exited on signal 11 
(core dumped)
Jun 30 09:30:00 toots /kernel: pid 6697 (atrun), uid 0: exited on signal 11 
(core dumped)
Jun 30 09:35:00 toots /kernel: pid 6706 (atrun), uid 0: exited on signal 11 
(core dumped)

and:

/var/log/messages:Jun 30 10:30:00 toots atrun[233]: Cannot stat in
/var/at/jobs/: Bad file descriptor
/var/log/messages:Jun 30 10:40:00 toots atrun[367]: Cannot stat in
/var/at/jobs/: Bad file descriptor
/var/log/messages:Jun 30 10:55:00 toots atrun[668]: Cannot stat in
/var/at/jobs/: Bad file descriptor
/var/log/messages:Jun 30 11:00:00 toots atrun[684]: Cannot stat in
/var/at/jobs/: Bad file descriptor                

[lines broken for convenience]


The trouble went away after I rebooted and fsck'ed /var.


've seen "signal 11" discussed here, but can't find it in the 
> archives.  My recollection is that during a "make world" a signal 11 
> indicates bad memory, either ram or cache.  Is that indicated here?  
> Anything else?
> 
> And a newbie question please?  When a core dumps, where and what does 
> it dump?
> 
> tia,
> 
> Riley

-- 
Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de