From: "Segher Boessenkool" <segher@kernel.crashing.org>
To: "Oncaphillis" <oncaphillis@snafu.de>
Cc: "Xiaofan Chen" <xiaofanc@gmail.com>,
libusb-devel@lists.sourceforge.net,
"Kernel development list" <linux-kernel@vger.kernel.org>
Subject: Re: [Libusb-devel] Kernel bug message and missing data on libusb_interrupt_transfer
Date: Tue, 5 Apr 2011 16:54:46 +0200 (CEST) [thread overview]
Message-ID: <56341.94.211.195.167.1302015286.squirrel@gate.crashing.org> (raw)
In-Reply-To: <4D9AE10E.3080501@snafu.de>
>> 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:[<ffffffff8028d2f8>] [<ffffffff8028d2f8>] 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
next prev parent reply other threads:[~2011-04-05 14:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 12:14 Kernel bug message and missing data on libusb_interrupt_transfer Oncaphillis
2011-04-04 13:06 ` [Libusb-devel] " Xiaofan Chen
2011-04-04 13:31 ` Oncaphillis
2011-04-05 9:29 ` Oncaphillis
2011-04-05 14:13 ` Alan Stern
2011-04-05 14:21 ` Oncaphillis
2011-04-05 14:42 ` Alan Stern
2011-04-06 10:37 ` Oncaphillis
2011-04-08 9:07 ` Oncaphillis
2011-04-08 10:09 ` Xiaofan Chen
2011-04-08 14:37 ` Alan Stern
2011-04-05 14:54 ` Segher Boessenkool [this message]
2011-04-05 15:15 ` Oncaphillis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56341.94.211.195.167.1302015286.squirrel@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=libusb-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oncaphillis@snafu.de \
--cc=xiaofanc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.