Delivery-Date: Sat, 23 Jan 2016 16:05:45 -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 03FF71E0AEA;
	Sat, 23 Jan 2016 16:05:44 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B325636CE6;
	Sat, 23 Jan 2016 21:05:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 33D6236C18
 for <tor-talk@lists.torproject.org>; Sat, 23 Jan 2016 21:05:33 +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 dS_zjisTIL38 for <tor-talk@lists.torproject.org>;
 Sat, 23 Jan 2016 21:05:33 +0000 (UTC)
Received: from mx01.services.blackmesa.at (mx01.services.blackmesa.at
 [91.219.68.126])
 by eugeni.torproject.org (Postfix) with ESMTP id F3E873682E
 for <tor-talk@lists.torproject.org>; Sat, 23 Jan 2016 21:05:32 +0000 (UTC)
Received: by mx01.services.blackmesa.at (Postfix, from userid 1001)
 id 00A0B4BAD321; Sat, 23 Jan 2016 22:05:28 +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 53F824BAD31F
 for <tor-talk@lists.torproject.org>; Sat, 23 Jan 2016 22:05:28 +0100 (CET)
MIME-Version: 1.0
Date: Sat, 23 Jan 2016 22:05:28 +0100
From: creo <creo-tor-lists@blackmesa.at>
To: tor-talk@lists.torproject.org
In-Reply-To: <20160123191442.GA2981@ix.home>
References: <20160116212250.GA14827@ix-293.local>
 <n7p00n$ia8$1@ger.gmane.org> <20160123191442.GA2981@ix.home>
Message-ID: <975f6dce11caa36e05b79e0b6172bacf@blackmesa.at>
X-Sender: creo-tor-lists@blackmesa.at
User-Agent: Roundcube Webmail/1.0.3
Subject: [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>

Hej guys,

my Tor node crashed a few days ago. After I noticed the downtime
and connected to it, I found the linux kernel oops and left it
there since it seems debugging is still possible to some extent.

Message indicates that the problem was indeed Tor related,
the system is running on ARM.

Does it make sense to report the content of the oops notice and
if yes - would it help to let the system alone in this state in
case somebody comes up with further questions and certain commands
that may bring deeper insight, or is it better to just reboot the
node and continue the operation?

I'm asking because I'm not sure how "interesting" such information
may be .. not being a kernel guy at all reminds me of typical
Windows BlueScreens spewing out memory allocation ranges - nice
to have that information as a Windows Kernel Developer maybe, but
not for the usual userspace developer - so if its not worth the
wait, I'd better get the node up and doing some work again ;-)


Sanx for your input,

D.

-- 
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

