Delivery-Date: Sat, 23 Jan 2016 19:17:21 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id A5CF01E0AEA;
	Sat, 23 Jan 2016 19:17:19 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B5C6F362C5;
	Sun, 24 Jan 2016 00:17:12 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D10F335369
 for <tor-talk@lists.torproject.org>; Sun, 24 Jan 2016 00:17:08 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id MrQbTBx2DN5j for <tor-talk@lists.torproject.org>;
 Sun, 24 Jan 2016 00:17:08 +0000 (UTC)
Received: from magic02.frii.com (magicmail02.frii.com [216.17.135.171])
 by eugeni.torproject.org (Postfix) with SMTP id A43E3243BB
 for <tor-talk@lists.torproject.org>; Sun, 24 Jan 2016 00:17:05 +0000 (UTC)
Received: (qmail 28145 invoked from network); 24 Jan 2016 00:17:02 -0000
Received: from localhost (HELO [192.168.101.125]) (cline@frii.com@127.0.0.1)
 by magic02.frii.com with SMTP
 (ca88df44-c22f-11e5-8dd6-9309b1772849); Sat, 23 Jan 2016 17:17:02 -0700
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Pgp-Agent: GPGMail 2.5.2
From: Ken Cline <cline@frii.com>
In-Reply-To: <CAD2Ti2-iaD0yct=2215rsG7QEP7WQSpoQcw3hQYoDLn-C8FjpQ@mail.gmail.com>
Date: Sat, 23 Jan 2016 17:17:01 -0700
Message-Id: <40E8EAC4-1F93-4CA7-BF40-8F2BA2A1CAB5@frii.com>
References: <20160116212250.GA14827@ix-293.local> <n7p00n$ia8$1@ger.gmane.org>
 <20160123191442.GA2981@ix.home>
 <975f6dce11caa36e05b79e0b6172bacf@blackmesa.at>
 <CAD2Ti2-iaD0yct=2215rsG7QEP7WQSpoQcw3hQYoDLn-C8FjpQ@mail.gmail.com>
To: tor-talk@lists.torproject.org
X-Mailer: Apple Mail (2.2104)
X-MagicMail-OS: MagicMail 2.0-Stable
X-MagicMail-UUID: ca88df44-c22f-11e5-8dd6-9309b1772849
X-MagicMail-Authenticated: cline@frii.com
X-MagicMail-SourceIP: 127.0.0.1
X-MagicMail-EnvelopeFrom: <cline@frii.com>
Subject: Re: [tor-talk] Kernel OOPS through Tor - report or ignore?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============7003278192185645912=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


--===============7003278192185645912==
Content-Type: multipart/signed; boundary="Apple-Mail=_2B35DEF0-0AFA-4102-BD34-15E90785512D"; protocol="application/pgp-signature"; micalg=pgp-sha1


--Apple-Mail=_2B35DEF0-0AFA-4102-BD34-15E90785512D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On 23 Jan 2016, at 4:29 PM, grarpamp <grarpamp@gmail.com> wrote:
>=20
> On Sat, Jan 23, 2016 at 4:05 PM, creo <creo-tor-lists@blackmesa.at> =
wrote:
>> Does it make sense to report the content of the oops notice and
>=20
> Typically
> Kernel panics go to the OS people.
> Program crashes go to the app people.
> Neither should happen, so people should report them.

Check for other causes before reporting:  Is the software (OS kernel & =
extensions in this case) up to date?  Is there a hardware error?  I =
reported a Tor crash, only to find it was caused by a failing disk.

Creo, It sounds like you have a crash recovery utility running.  If so, =
save the crash dump and reboot.  You can send the dump in or wait to see =
if it happens a second time.

--Apple-Mail=_2B35DEF0-0AFA-4102-BD34-15E90785512D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlakF/0ACgkQhVEOpGWd7KDhEACeNdpvcxgzxQzGI4ebJyWvDiOf
SVwAoMbq6+JO5JhIWaPQaEiZrGsoD0IG
=c5MD
-----END PGP SIGNATURE-----

--Apple-Mail=_2B35DEF0-0AFA-4102-BD34-15E90785512D--

--===============7003278192185645912==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

--===============7003278192185645912==--

