Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753459Ab1DEOzB (ORCPT ); Tue, 5 Apr 2011 10:55:01 -0400 Received: from gate.crashing.org ([63.228.1.57]:42604 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753088Ab1DEOzA (ORCPT ); Tue, 5 Apr 2011 10:55:00 -0400 Message-ID: <56341.94.211.195.167.1302015286.squirrel@gate.crashing.org> In-Reply-To: <4D9AE10E.3080501@snafu.de> References: <4D99B60D.3030009@snafu.de> <4D99C83A.2080807@snafu.de> <4D9AE10E.3080501@snafu.de> Date: Tue, 5 Apr 2011 16:54:46 +0200 (CEST) Subject: Re: [Libusb-devel] Kernel bug message and missing data on libusb_interrupt_transfer From: "Segher Boessenkool" To: "Oncaphillis" Cc: "Xiaofan Chen" , libusb-devel@lists.sourceforge.net, "Kernel development list" User-Agent: SquirrelMail/1.4.10a-1.fc6 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Priority: 3 (Normal) Importance: Normal Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 868 Lines: 24 >> I'm in an environment where we are >> reluctant to switch between versions. I had a hard time to > Pid: 14293, comm: E25Stress Tainted: G D 2.6.30.10 #2 To Be > Filled By O.E.M. > RIP: 0010:[] [] kfree+0x7c/0xdb > Suprisingly now the kernel is reported as tainted although there isn't > any module inserted the That is not true; "G" means you have loaded a (GPL-compatible) module. "D" means the kernel died. It died because it tried to dealloc memory using a bad pointer, perhaps a null pointer. Your kernel is two years old, you should try a current kernel. Segher -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/