From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S268410AbTCFVpU>; Thu, 6 Mar 2003 16:45:20 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S268409AbTCFVpU>; Thu, 6 Mar 2003 16:45:20 -0500
Received: from divine.city.tvnet.hu ([195.38.100.154]:26480 "EHLO
	divine.city.tvnet.hu") by vger.kernel.org with ESMTP
	id <S268410AbTCFVpT>; Thu, 6 Mar 2003 16:45:19 -0500
Date: Thu, 6 Mar 2003 22:46:19 +0100 (MET)
From: Szakacsits Szabolcs <szaka@sienet.hu>
To: "Randy.Dunlap" <rddunlap@osdl.org>
cc: Anton Altaparmakov <aia21@cantab.net>, <linux-kernel@vger.kernel.org>
Subject: Oops counter (was Re: ntfs OOPS (2.5.63))
In-Reply-To: <20030306123601.0fdcc6ad.rddunlap@osdl.org>
Message-ID: <Pine.LNX.4.30.0303062230470.31029-100000@divine.city.tvnet.hu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org


> | > ==> Mar  1 13:35:44 midway kernel: Oops: 0002
> | >
> | > This means oops counter is 2. So there were two oopses before with
> | > counter value 0 and 1.
> |
> | I just checked, this is not true (I could dig up the false source
> | of information if interested).

I didn't have to: Google listed it in the top 5 hits searching for
"oops counter" ...

> However, such an oops counter could be useful...

I believed immediately this feature was added, it looked so good idea.

	Szaka