From: Oncaphillis <oncaphillis@snafu.de>
To: Alan Stern <stern@rowland.harvard.edu>
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: Fri, 08 Apr 2011 11:07:08 +0200 [thread overview]
Message-ID: <4D9ED03C.2000706@snafu.de> (raw)
In-Reply-To: <4D9C4262.1010704@snafu.de>
On 04/06/2011 12:37 PM, Oncaphillis wrote:
> On 04/05/2011 04:42 PM, Alan Stern wrote:
>> On Tue, 5 Apr 2011, Oncaphillis wrote:
>>
>>> On 04/05/2011 04:13 PM, Alan Stern wrote:
>>>> On Tue, 5 Apr 2011, Oncaphillis wrote:
>>>>
>>>>> Now I get
>>>>>
>>>>> <snip>
>>>>> ------------[ cut here ]------------
>>>>> kernel BUG at mm/slub.c:2808!
>>>>> invalid opcode: 0000 [#2] SMP
>>>> Can you duplicate this using either a 2.6.37 or 2.6.38 kernel?
>>>>
>>>> Alan Stern
>>>>
>>> The highest kernel version we've tried (as far as i remember) was the
>>> 2.6.36. Have there been issues which might have been solved betwen 36
>>> and 3(7|8) ?
>> I don't know. But the core kernel developers always want to hear about
>> problems reported against the most recent version possible. If you
>> could test 2.6.39-rc1 (or -rc2, which should be released in a day or
>> so), that would be even better.
> Ok -- kernel 2.6.38.2 together with libusb-1.0.8 seems to behave well.
> This was only a minimal overnight test. Not the full functionality we
> are trying to implement. But it looks promising.
>
> Thank you
>
> O.
>
Just a short update,
It doesn't seem to have anything to do with the libsub-1.0.x) version but
with the --(enable|disable)-timerfd option of libusb configure. If
libusb was
configured with --disable-timerfd, which was the case for our 1.0.6 libusb
I get the kernel bug message in in slub.c module and eventually a
kernel freeze. This holds true for libusb-1.0.8 and kernel 2.6.38.2
O.
>>> I'll give it a try.
>> Thanks.
>>
>> Alan Stern
>>
>> --
>> 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/
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> Libusb-devel mailing list
> Libusb-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libusb-devel
next prev parent reply other threads:[~2011-04-08 9:07 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 [this message]
2011-04-08 10:09 ` Xiaofan Chen
2011-04-08 14:37 ` Alan Stern
2011-04-05 14:54 ` Segher Boessenkool
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=4D9ED03C.2000706@snafu.de \
--to=oncaphillis@snafu.de \
--cc=libusb-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox