public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oncaphillis <oncaphillis@snafu.de>
To: Xiaofan Chen <xiaofanc@gmail.com>
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
	libusb-devel@lists.sourceforge.net
Subject: Re: [Libusb-devel] Kernel bug message and missing data on libusb_interrupt_transfer
Date: Mon, 04 Apr 2011 15:31:38 +0200	[thread overview]
Message-ID: <4D99C83A.2080807@snafu.de> (raw)
In-Reply-To: <BANLkTi=mU=v_6gH_5VCwZZmiX+UoqAVf+w@mail.gmail.com>

  Thanks for the reply.

I'm in an environment where we are
reluctant to switch between versions. I had a hard time to
argue for 0.1.x to 1.0.x transition. We saw the same bug (or at least
kernel freezes in 0.1.x) I'll give 1.0.8 a try and report back.
  Using a git pull isn't an option for us for political reasons.

Thanks

O.


On 04/04/2011 03:06 PM, Xiaofan Chen wrote:
> On Mon, Apr 4, 2011 at 8:14 PM, Oncaphillis<oncaphillis@snafu.de>  wrote:
>> Hi,
>>
>>   We are experiencing sporadic kernel bug messages and total
>> kernel freezes on usb communication via libusb-1.0.6.
> First thing first, why not try the latest release version which
> is libusb-1.08?
>
> Or better yet, try the latest git from libusb-stuge branch
> which has quite some fixes post 1.08.
> http://git.libusb.org/?p=libusb-stuge.git;a=summary;js=1
>
>
>>   We are currently under kernel 2.6.30.10 but have seen
>> it also under older and newer kernel (I think the newest was
>> a 2.6.36.x).
>>
>
>


  reply	other threads:[~2011-04-04 13:31 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 [this message]
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
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=4D99C83A.2080807@snafu.de \
    --to=oncaphillis@snafu.de \
    --cc=libusb-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --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