[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#270204: marked as done (kernel-image-2.6-k7: oprofile causes segfaults and oopses)



Your message dated Sun, 17 Oct 2004 18:29:46 -0400
with message-id <1098052186.24178.40.camel@localhost>
and subject line hardware problems
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 6 Sep 2004 06:23:06 +0000
>From peter@llama.cordes.ca Sun Sep 05 23:23:06 2004
Return-path: <peter@llama.cordes.ca>
Received: from smtpin.eastlink.ca [24.222.0.18] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1C4CuA-00042I-00; Sun, 05 Sep 2004 23:23:06 -0700
Received: from holly.cordes.ca ([24.222.156.67])
 by mx3.eastlink.ca (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3
 2004)) with ESMTP id <0I3L0026KWDN95@mx3.eastlink.ca> for
 submit@bugs.debian.org; Mon, 06 Sep 2004 03:22:35 -0300 (ADT)
Received: from peter by holly.cordes.ca with local (Exim 4.34)
	id 1C4Ctf-0001Ty-4Y; Mon, 06 Sep 2004 03:22:35 -0300
Date: Mon, 06 Sep 2004 03:22:35 -0300
From: Peter Cordes <peter@cordes.ca>
Subject: kernel-image-2.6-k7: oprofile causes segfaults and oopses
Sender: Peter Cordes <peter@llama.cordes.ca>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Message-id: <E1C4Ctf-0001Ty-4Y@holly.cordes.ca>
MIME-version: 1.0
X-Mailer: reportbug 2.63
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: kernel-image-2.6.8-1-k7
Version: 2.6.8-2
Severity: normal

 Using oprofile (running opcontrol --start) makes the system unstable[1]
when running a Debian kernel.  I first noticed this with a 2.6.7 kernel I
compiled myself (from Debian sources), so I upgraded to 2.6.8-1-k7, where I
observed the same symptoms.  A vanilla (kernel.org tarball) kernel built
with very nearly the same config options produces none of these symptoms
even with oprofile collecting data.  When I'm not using oprofile, the system
is rock solid stable.  (memtest86+ and cpuburn don't report any errors, etc.)

 Oh, I think I used gcc 3.4 to build the vanilla 2.6.8 kernel, but probably
not for the 2.6.7 that had the same oprofile problems.  If it's a gcc thing,
that would explain it.  I was going to report this as a bug against the
kernel-source package, but it might well not be Debian's patches that are at
fault.  I am sure that the 2.6 kernels Debian distributes crash when I use
oprofile.  If you can't reproduce this with kernel-image-2.6.8-1-k7, I'll
try to do some more narrowing down.  I don't have time to use kdb/kgdb to
actually find the problem myself, though :(

 All my testing related to this has been on an Athlon tbird running Sarge.

[1] instability includes segfaults, errors, and oopses all over the place.
e.g. when doing tar xjf kernel-source-2.6.8.tar.bz2, it doesn't complete
because bzip2 or tar finds an error in the data they're processing.  mozilla
can barely start without segfaulting.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-vanilla
Locale: LANG=C, LC_CTYPE=C

---------------------------------------
Received: (at 270204-done) by bugs.debian.org; 17 Oct 2004 22:29:48 +0000
>From dilinger@voxel.net Sun Oct 17 15:29:48 2004
Return-path: <dilinger@voxel.net>
Received: from zero.voxel.net [209.123.232.253] (postfix)
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1CJJXA-0003AZ-00; Sun, 17 Oct 2004 15:29:48 -0700
Received: from spiral.internal (alb-24-194-62-26.nycap.rr.com [24.194.62.26])
	by zero.voxel.net (Postfix) with ESMTP id 000E624AF26
	for <270204-done@bugs.debian.org>; Sun, 17 Oct 2004 18:29:47 -0400 (EDT)
Subject: hardware problems
From: Andres Salomon <dilinger@voxel.net>
To: 270204-done@bugs.debian.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-yDDjMzDPZXdgbfPojON6"
Date: Sun, 17 Oct 2004 18:29:46 -0400
Message-Id: <1098052186.24178.40.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.2 
Delivered-To: 270204-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
	version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


--=-yDDjMzDPZXdgbfPojON6
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Reporter has indicated this bug is due to bad RAM.  Closing..

--=20
Andres Salomon <dilinger@voxel.net>

--=-yDDjMzDPZXdgbfPojON6
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBcvJZ78o9R9NraMQRAo5TAKCt6RRI04Qsudmx7aWj2KQ65VCvhQCfXHYl
WWliuOeK274SxgPng+5L4WI=
=yOVY
-----END PGP SIGNATURE-----

--=-yDDjMzDPZXdgbfPojON6--



Reply to: