Delivery-Date: Sun, 24 Jan 2016 02:10:07 -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 6FEB11E2FDF;
	Sun, 24 Jan 2016 02:10:05 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 1455538A72;
	Sun, 24 Jan 2016 07:10:03 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id B1683361AB
 for <tor-talk@lists.torproject.org>; Sun, 24 Jan 2016 07:09:59 +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 AuGELYG69rMH for <tor-talk@lists.torproject.org>;
 Sun, 24 Jan 2016 07:09:59 +0000 (UTC)
Received: from mx01.services.blackmesa.at (mx01.services.blackmesa.at
 [91.219.68.126])
 by eugeni.torproject.org (Postfix) with ESMTP id 7ED91265BD
 for <tor-talk@lists.torproject.org>; Sun, 24 Jan 2016 07:09:59 +0000 (UTC)
Received: by mx01.services.blackmesa.at (Postfix, from userid 1001)
 id 74C034BAD321; Sun, 24 Jan 2016 08:09:54 +0100 (CET)
Received: from webmail.services.blackmesa.at (mx01.blackmesa.projects.lab
 [127.0.0.1])
 by mx01.services.blackmesa.at (Postfix) with ESMTPA id EB06C4BAD31F
 for <tor-talk@lists.torproject.org>; Sun, 24 Jan 2016 08:09:54 +0100 (CET)
MIME-Version: 1.0
Date: Sun, 24 Jan 2016 08:09:54 +0100
From: creo <creo-tor-lists@blackmesa.at>
To: tor-talk@lists.torproject.org
In-Reply-To: <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>
 <40E8EAC4-1F93-4CA7-BF40-8F2BA2A1CAB5@frii.com>
Message-ID: <20ca7e128ecc22830becb4845b76ee83@blackmesa.at>
X-Sender: creo-tor-lists@blackmesa.at
User-Agent: Roundcube Webmail/1.0.3
Subject: Re: [tor-talk]
 =?utf-8?q?Kernel_OOPS_through_Tor_-_report_or_ignore?=
 =?utf-8?q?=3F?=
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

> grarpamp wrote:
> Neither should happen, so people should report them.

:-) Okay.

> grarpamp wrote:
> Then if it gets us closer to onioncat v2, sure ;)

As long as we don't come up with a proper solution for
handling the proposed changes to the onion key
(aka. making it longer than 80 bits) there will be no
such thing as there are too many pitfalls ... but
I guess afraid that's another story :P


> Ken Cline wrote:
> 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.

I'll definitely do that, ... don't trust that raspberry pi 2 anyway :)

> Ken Cline wrote:
> 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.

Not on purpose - it's not a Kernel panic, just an oops, which threw me
into a kdb session, giving me debug opportunities I can not take any
advantage of because my pure lack of knowledge :-) But it's never too
late to learn something new I guess :P


Thanks for your input guys :)
-- 
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

