Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Aug 2001 20:30:03 -0700 (PDT)
From:      Kris Kennaway <kris@obsecurity.org>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: bin/30173: Kernel panic caused by cron (movl)
Message-ID:  <200108290330.f7T3U3685720@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/30173; it has been noted by GNATS.

From: Kris Kennaway <kris@obsecurity.org>
To: =?iso-8859-1?Q?F=E9lix-Antoine_Paradis?= <reel@freebsd-fr.org>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: bin/30173: Kernel panic caused by cron (movl)
Date: Tue, 28 Aug 2001 20:28:30 -0700

 --48TaNjbzBVislYPb
 Content-Type: text/plain; charset=iso-8859-1
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Tue, Aug 28, 2001 at 05:53:14PM -0700, F=E9lix-Antoine Paradis wrote:
 >=20
 > >Number:         30173
 > >Category:       bin
 > >Synopsis:       Kernel panic caused by cron (movl)
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       high
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:       =20
 > >Keywords:      =20
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Tue Aug 28 18:00:02 PDT 2001
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     F=E9lix-Antoine Paradis
 > >Release:        FreeBSD 4.4-PRERELEASE
 > >Organization:
 > Unix Consult Technologies
 > >Environment:
 > FreeBSD machine 4.4-PRERELEASE FreeBSD 4.4-PRERELEASE #0: Mon Aug 13 12:1=
 4:0
 > 6 EDT 2001     reel@machine:/usr/src/sys/compile/ZEUS  i386
 >=20
 > >Description:
 > Got a kernel panic with notified that the program causing it was cron.
 > I looked in it a bit more and somewhere it specified movl.
 
 <sarcasm>
 Ok, that narrows it down.  There can't be many places in the kernel
 which use the movl opcode.
 </sarcasm>
 
 This PR is currently content-free.  Please consult the chapter in the
 FreeBSD handbook which deals with kernel panics, obtain a crashdump
 and a traceback and include the results as a followup.  Otherwise
 there is no way for anyone to replicate or identify your problem.
 
 Kris
 
 --48TaNjbzBVislYPb
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQE7jGFdWry0BWjoQKURAsRKAJ9nigh2d6N0GJXA5uZd+ZppKUHn2QCfX3Nq
 L9Ly4LjH4/2K5MUtK16aU0w=
 =t3es
 -----END PGP SIGNATURE-----
 
 --48TaNjbzBVislYPb--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108290330.f7T3U3685720>