From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: Top 10 kernel oopses for the week ending January 5th, 2008 Date: Tue, 8 Jan 2008 10:27:34 -0800 (PST) Message-ID: References: <477FF149.4070609@linux.intel.com> <20080105213935.GN27894@ZenIV.linux.org.uk> <20080107174431.GC27741@fieldses.org> <4782CF9C.6000508@gmail.com> <20080108081401.d9576ac5.randy.dunlap@oracle.com> <4783B602.1050307@linux.intel.com> <4783BE06.1070507@linux.intel.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Randy Dunlap , Kevin Winchester , "J. Bruce Fields" , Al Viro , Linux Kernel Mailing List , Andrew Morton , NetDev To: Arjan van de Ven Return-path: Received: from smtp2.linux-foundation.org ([207.189.120.14]:41275 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751632AbYAHS2j (ORCPT ); Tue, 8 Jan 2008 13:28:39 -0500 In-Reply-To: <4783BE06.1070507@linux.intel.com> Sender: netdev-owner@vger.kernel.org List-ID: On Tue, 8 Jan 2008, Arjan van de Ven wrote: > > the database has the information so it's just a matter of slightly different > php code ;) > Before I do that... do you want the BUG's separate, part of the warnings or > part of the oopses? > (I rather make this change once ;) I'd like them all separate, they tend to be very different and contain different information. Put the warnings last, as the least important. Oopses at the top, since they tend to be the ones that are less expected. > > and notice how the Code: never made it into the raw message (and thus there > > is also no instruction disassembly). > > ok I'll fix this; I can fix this for all new entries at least, fixing > retroactive is going to be near impossible I suspect. Oh well.. Linus