Re: [Libusb-devel] Kernel bug message and missing data on libusb_interrupt_transfer

[Oncaphillis <oncaphillis@snafu.de>]

On 04/05/2011 04:54 PM, Segher Boessenkool wrote:
>>> 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.
>
>

Thanks -- Didn't know anything about the 'G D' convention. Although
/proc/modules is empty (I don't have lsmod on the target system).

  We already have tried 2.6.36.x coming up with the same error.
Alan Stern recommended testing 2.6.3(8|9-rc1) which I'm currently doing.

O.

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