Bug#647424: Código aviso: ID67565434.

2012-07-26 Thread Webmail © 2012 Atualização da equipe
Caro Webmail / Conta de Usuário E-mail

Estamos atualizando nosso banco de dados e e-mail centro conta. Estamos a 
excluir todas as contas de webmail não utilizados e criar mais espaço para 
novas contas. Para garantir que você não experimenta interrupção do serviço 
durante este período, por favor clique no link Validation E-mail:
 
Link de validação

https://docs.google.com/a/ib.usp.br/spreadsheet/viewform?formkey=dHd4SFFsX3VOalJwOFNxa2VhN3dmT1E6MQ


Depois de ter preenchido o formulário com sucesso, você terá que clicar em 
ENVIAR.

Webmail © 2012 Atualização da equipe
Código aviso: ID67565434.


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/256001893.286801.1343286314795.javamail.r...@unifenas.br



Bug#629865: xen-linux-system-2.6.26-2-xen-amd64 causes system crash when using aacraid driver

2012-07-26 Thread idjik
Does this message mean Adaptec drivers are one big miserable piece of crap and 
can't be used on virtualized platforms? Does this mean RAID hardware products 
supplied by Adaptec / PMC are faulty and won't work on any Linux virtual 
platform at all? 

I'm just trying to bring this to attention of PMC sales and clarify this moment 
because we've recently purchased such adapters and getting absolutely similar 
errors:

PCI-DMA: Out of SW-IOMMU space for 65536 bytes at device :04:00.0
--- [cut here ] - [please bite here ] -
Kernel BUG at .../BUILD/aacraid-kmod-1.1.7/_kmod_build_xen/aachba.c:5502
invalid opcode:  [1] SMP
...
Pid: 3046, comm: kjournald Tainted: G  2.6.18-308.8.2.el5.xen #1
RIP: e030:[880b8f9a]  [880b8f9a] 
:aacraid:aac_build_sgraw+0x47/0x17b
...
Call Trace:
 IRQ  [880ba686] :aacraid:aac_write_raw_io+0x90/0xed
 [880b8bc4] :aacraid:aac_scsi_cmd+0xf8c/0x131b
 [80263929] _spin_lock_irqsave+0x9/0x14
 [8023f468] lock_timer_base+0x1b/0x3c
 [880b65fd] :aacraid:aac_queuecommand+0x72/0x82


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/6d7b863c-323e-43b3-a4fa-89b05bc70...@googlegroups.com



Bug#682709: NFS4 krb5 mounts hang under nfs-utils 1.2.6-3

2012-07-26 Thread Nicolas Bourdaud
severity 682709 grave
thanks

Hi,

I am affected by the same bug. I have raised the severity of the bug to
grave because it makes NFSv4 mount with kerberos unusable.

Cheers,

Nicolas



signature.asc
Description: OpenPGP digital signature


Processed: Re: NFS4 krb5 mounts hang under nfs-utils 1.2.6-3

2012-07-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 682709 grave
Bug #682709 [nfs-kernel-server] nfs-kernel-server: NFS4 krb5 mounts hang under 
nfs-utils 1.2.6-3
Severity set to 'grave' from 'important'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
682709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.134331251323232.transcr...@bugs.debian.org



Bug#682709: NFS4 krb5 mounts hang under nfs-utils 1.2.6-3

2012-07-26 Thread Nicolas Bourdaud
severity 682709 important
thanks

For a reason I don't understand, after the last reboot of the server and
client, everything works again. I suspect the last configuration changes
(before my previous email) did not propagate correctly because of some
caching (or some other reason that would go beyond my understanding).

Since the bug does not seem to be as systematic as I originally thought,
I set the severity back to the one set by the bug reporter.

Sorry for the noise.

Nicolas



signature.asc
Description: OpenPGP digital signature


Processed: Re: NFS4 krb5 mounts hang under nfs-utils 1.2.6-3

2012-07-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 severity 682709 important
Bug #682709 [nfs-kernel-server] nfs-kernel-server: NFS4 krb5 mounts hang under 
nfs-utils 1.2.6-3
Severity set to 'important' from 'grave'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
682709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.134331590912539.transcr...@bugs.debian.org



[bts-link] source package src:linux

2012-07-26 Thread bts-link-upstream
#
# bts-link upstream status pull for source package src:linux
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #680707 (http://bugs.debian.org/680707)
# Bug title: Asus P5NSLI: lockup on resume from suspend
#  * http://bugzilla.kernel.org/show_bug.cgi?id=43641
#  * remote status changed: RESOLVED - CLOSED
usertags 680707 - status-RESOLVED
usertags 680707 + status-CLOSED

thanks


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120726164104.19418.22805.btsl...@busoni.debian.org



[bts-link] source package linux-2.6

2012-07-26 Thread bts-link-upstream
#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #584830 (http://bugs.debian.org/584830)
# Bug title: linux-image-2.6.32-5-amd64: USB 3.0 / xhci prevents suspend
#  * http://bugzilla.kernel.org/show_bug.cgi?id=16153
#  * remote status changed: NEW - RESOLVED
#  * remote resolution changed: (?) - CODE-FIX
#  * closed upstream
tags 584830 + fixed-upstream
usertags 584830 - status-NEW
usertags 584830 + status-RESOLVED resolution-CODE-FIX

thanks


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120726164104.19418.91358.btsl...@busoni.debian.org



Bug#682709: NFS4 krb5 mounts hang under nfs-utils 1.2.6-3

2012-07-26 Thread Luk Claes
On 07/26/2012 05:18 PM, Nicolas Bourdaud wrote:

 Since the bug does not seem to be as systematic as I originally thought,
 I set the severity back to the one set by the bug reporter.

Even if that was not the case, NFS is not only about NFS4 or use with
krb5, so anything above important is wrong as long as these other use
cases still work.

Btw, there are quite some NFS4+krb5 bugs open as none of its maintainers
use it that way, would you be willing to help out?

Cheers

Luk


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50117732.3070...@debian.org



Bug#681354: Re (2): Bug#681354: linux-image-2.6.32: Complaint from firewire driver at system startup.

2012-07-26 Thread peasthope
From: Ben Hutchings b...@decadent.org.uk
Date: Thu, 26 Jul 2012 03:06:05 +0100
 I didn't say the timeout was ignored; I said the time limit was
 increased.  If a driver sets a time limit for some hardware operation
 which is shorter than the hardware may require to complete it
 successfully, increasing the time limit may well be the correct fix.

OK; sorry; cynicism was dominating reason.

The delay I see is about 12 s.  The initialization is electronic 
switching with possibly a few disk writes?  I'd expect that to 
occur in less than 1 s.

Regards,   ... Peter E.

-- 
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Telephone 1 360 639 0202.  Bcc: peter at easthope.ca  
http://carnot.yi.org/  http://members.shaw.ca/peasthope/index.html#Itinerary 


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/171057594.39092.26165@cantor.invalid



Bug#682007: [squeeze-backports] NULL pointer dereference in __fscache_read_or_alloc_pages

2012-07-26 Thread Brian Kroth

Jonathan Nieder jrnie...@gmail.com 2012-07-20 11:25:

merge 682116 682007
quit

Hi,

Ben Hutchings b...@decadent.org.uk 2012-07-19 13:32:

On Thu, 2012-07-19 at 13:37 +0200, Bastian Blank wrote:



We don't support proprietary stuff. Please remove and try again.


To be clear, Bastian is referring to the proprietary kernel module
(nvidia).


I think this stance is too aggressive.  Testing without the modules we
do not support can certainly help, but in cases like this where the
proprietary module is not likely to be related, I'd rather hear about
problems earlier than have submitters wait until they have time to
reproduce without.

Luckily this has been reproduced without the nvidia module, so
merging.

Rhaoul writes:

This is reproducable using grep -r abc * inside a directory with
   9541 files (no sym- or hardlinks, no block or character special 
files) in
   1524 directories
(PHP MODX installation)


I downloaded the couple of files from that site [1] and unzipped them to 
hopefully create a similar test setup.  I had to make two copies of it 
to get that many files/dirs.


Right now I'm running this to see what happens:
# for i in {1..100}; do grep -r abc /cae/apps/data/testapp-1/tmp*  /dev/null; 
done

So far nothing much, but I just started.  


Some other points for comparison:
- does the cache need to be fresh?  I have a cron job that does this 
  from time to time (about once a month with some random splay between 
  machines) on these machines anyways (basically stop cachefilesd  rm 
  -rf the_cache_dir_contents  start cachefilesd)

- anything else in particular about the test I should look for?


I've also noticed that I can usually get cachefilesd to spin to 100% cpu 
if I do something like this:


# grep pattern /home/logs/some_multi_gb_large_readonly_logfile

I recall seeing patches for large file support, but wasn't sure on their 
status.  Anyways, that's digressing, so I'll leave that as a separate 
item for later.


Thanks,
Brian

[1] http://modx.com/download/


signature.asc
Description: Digital signature


Bug#682007: [squeeze-backports] NULL pointer dereference in __fscache_read_or_alloc_pages

2012-07-26 Thread Brian Kroth

Jonathan Nieder jrnie...@gmail.com 2012-07-21 12:04:

tags 682007 + upstream patch moreinfo
quit

Hi,

Brian Kroth wrote:


kernel BUG at 
/build/buildd-linux_3.2.20-1~bpo60+1-amd64-tQMw4f/linux-3.2.20/fs/buffer.c:3088!


This is

BUG_ON(!PagePrivate(page)); \

in

static int
drop_buffers(struct page *page, struct buffer_head **buffers_to_free)
{
struct buffer_head *head = page_buffers(page);

I suspect it's the same underlying problem, but maybe not.

Please test the attached patches, for example following the instructions
below:

0. prerequisites:

apt-get install git build-essential

1. get the kernel history, if you don't already have it:

git clone \
  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git


I take it then that this is a patch against the latest greatest kernel, 
not against the source for the backports kernel I'm currently running?



2. configure, build, test:

cd linux
git fetch origin
git checkout origin/master

cp /boot/config-$(uname -r) .config; # current configuration
scripts/config --disable DEBUG_INFO
make localmodconfig; # optional: minimize configuration
make deb-pkg; # optionally with -jnum for parallel build
dpkg -i ../name of package; # as root
reboot
... test test test ...

  Hopefully it reproduces the bug.  So


Oh, I see you want to compare two nearly identical kernels (both fairly 
recent) to isolate if just the patches are helpful rather than some mix 
between the two.



3. try the patches:

cd linux
git am -3sc $(ls -1 /path/to/patches/[01]*)
make deb-pkg; # maybe with -j4
dpkg -i ../name of package; # as root
reboot
... test test test ...

Thanks and hope that helps,
Jonathan


I can try and build/install this on one of our machines (I'd prefer not 
to push it everywhere yet), but without a reliably reproducible 
(on-demand that is) test case I'm not sure what it will show except that 
it perhaps doesn't introduce further blatant bugs.


Anyways, I'll wait on the results of my previous test first to see if we 
have a reliable test case from it before moving forward.


At this point the grep -r abc ... test is just hitting the cache over 
and over again, so it's not showing a whole lot.


One other thing I'd tried before was something like this run a couple of 
times in a row (hmm, I suppose I could try them in parallel too):


find /fsc_mounted_nfs -type f -exec cat {}  /dev/null \;

A couple of them paniced, but with inconsistent messages, so I had left 
them out for now.  Perhaps that's worth another shot ...


Thanks,
Brian


signature.asc
Description: Digital signature


Bug#679882: patches are now available upstream for kernel 3.2.24

2012-07-26 Thread Jeffrey Lerman


A series of 11 patches that fix the June 30 leapsecond issue, by John 
Stultz, Thomas Gleixner, and Richard Cochran, were committed to the 
3.2.24 kernel source on July 17.  Can this package be updated to include 
that version of the kernel - or can those patches be applied here?


Discussion at LKML seems to indicate that all kernels in the 2.6 and 3.x 
series that do not have these patches or their equivalent backports 
applied will have this issue.


Here are the relevant patch commits:

commit 0ad70925ab61c308d669d93f02c7bf1974a5158f
commit 7b9a231293995c1211d254a38d60f21980ed5d07
commit ec5806bcd08281a86e05b8e4eaf2f377bc8e5b24
commit d6a2a0400e36bcd2892272995a65b4bca029220f
commit a105e023adf852c9847e1fe7f0bc151ce0339914
commit 8a1ba973a23bd94a4ce34ffa543bf0e0d4ec13ff
commit 3c910e7e46810c73e21196867b7ec63d58a0a45c
commit b19f4db486601885ee4c40665f4e8509ec65b4d5
commit 09e66e8d71833a897a82ec18484b388e729b6548
commit 76117661ce2f9ecf7f969a4aeafd1c74802deae7
commit a57ccabee60519dd90051266c00d038055b93878

Thanks,
--Jeff Lerman


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5011976e.2030...@gmail.com



Re: Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works

2012-07-26 Thread Bjørn Mork
Vincent Lefevre vinc...@vinc17.net writes:
 On 2012-07-20 08:58:57 +0200, Vincent Lefevre wrote:
 So, it would seem that some part of the system would enable SlowKeys
 in my back for one of the keyboards (I recall that when this happens
 while I'm using the USB keyboard, only the USB keyboard is affected,
 not the laptop keyboard).
 
 If there a way to know whether SlowKeys is enabled, for each available
 keyboard? (Note: I'm not using GNOME, and even GNOME would be useless
 because according to what I see on this page, it cannot differentiate
 keyboards.)

 Additional information:

 * SlowKeys can be turned on and off by pressing the Shift key for
   at least 10 seconds:
 https://bugzilla.redhat.com/show_bug.cgi?id=816764
   I've tried and I confirm that this works. When several keyboards
   are attached, only the keyboard for which the Shift key is pressed
   is affected (I suppose that this is expected).

Thanks a lot for posting this.  I've now hit the bug several times
myself over the last few days, and without having read this thread first
I would never have known how to get out ot it.  And that would have been
really annoying given that this typically happens in the middle of some
heavy editing session. I would have hated to have to throw away the work
and reboot to get the system working again, and I don't think I ever
would have figured out the shift key trick.

BTW, is it only me, or do you have to hold down the key significantly
longer to turn the feature off than to turn it on?  It certainly feels
like it.

 * When the bug occurred in my case, I don't think I've pressed Shift
   for 10 seconds (well, when I do this, this is in combination with
   another key like PageUp / PageDown, but in this case, SlowKeys
   switching isn't triggered), at least in most of the cases.

In my case it seems to happen most often when I do cut and paste,
combining mouse selection with shift + del.  I often end up holding down
the shift key while selecting and bam...


IMNSHO, the hotkey choice is too generic to be acceptable at
all. Holding down any single key to silently enable a feature like this
is not going to do.  I find it somwhat surprising in light of the
Ctrl+Alt+Backspace disabling

Why couldn't they have used *both* shift keys as a trigger?  That would
have eliminated all false positives with no drawbacks AFAICS.

Anyway, please disable this extremely annoying feature until some safer
trigger can be found.


Bjørn


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87r4ryjp3z@nemi.mork.no



Re: Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works

2012-07-26 Thread Vincent Lefevre
On 2012-07-26 21:31:44 +0200, Bjørn Mork wrote:
 BTW, is it only me, or do you have to hold down the key significantly
 longer to turn the feature off than to turn it on?  It certainly feels
 like it.

No, it seems 10 seconds in both cases.

  * When the bug occurred in my case, I don't think I've pressed Shift
for 10 seconds (well, when I do this, this is in combination with
another key like PageUp / PageDown, but in this case, SlowKeys
switching isn't triggered), at least in most of the cases.
 
 In my case it seems to happen most often when I do cut and paste,
 combining mouse selection with shift + del.  I often end up holding down
 the shift key while selecting and bam...

Yes, while SlowKeys isn't turned on with Shift + non-modifier key,
if you hold Shift for 10 seconds while using the mouse, it will be
turned on.

 IMNSHO, the hotkey choice is too generic to be acceptable at
 all.

I completely agree.

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120727001159.gf4...@xvii.vinc17.org



Re: Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works

2012-07-26 Thread Wookey
+++ Vincent Lefevre [2012-07-20 08:58 +0200]:
 On 2012-07-20 08:31:19 +0200, Julien Cristau wrote:
  Sounds like you have slowkeys enabled.
  http://who-t.blogspot.fr/2012/06/xkb-slowkeys.html
 
 So, it would seem that some part of the system would enable SlowKeys
 in my back for one of the keyboards 

I hadn't seen this problem for weeks and thought maybe it was fixed,
and then it happened again (keyboard suddenly not responding, but
other keyboard working OK). Given the above message I tried holding
down shift for 10 seconds and lo and behold, the keyboard was back
working. So it does seem that the problem is the 'random but rare'
enabling of this feature without actually holding shift down for 10
seconds (or at least I'm fairly sure I didn't, but will keep an eye
out for doing it now).

A way to confirm if the slowkeys feature is currently engaged would
allow me to confirm this more directly next time. 

Wookey
-- 
Principal hats:  Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120727013914.ge16...@stoneboat.aleph1.co.uk



patch kernel 3.2.0-3 , add bluetooth 0489:e046 Foxconn / Hon Hai

2012-07-26 Thread koko Aborigines
patch kernel 3.2.0-3 , add bluetooth 0489:e046 Foxconn / Hon Hai

# uname -r
3.2.0-3-amd64

# lsb_release -a
Distributor ID:Debian
Description:Debian GNU/Linux testing (wheezy)
Release:testing
Codename:wheezy


# usb-devices
T:  Bus=03 Lev=02 Prnt=02 Port=02 Cnt=03 Dev#=  7 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0489 ProdID=e046 Rev=01.12
S:  Manufacturer=Broadcom Corp
S:  Product=BCM20702A0
S:  SerialNumber=C01885F67F9E
C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

thanks you


btusb.patch
Description: Binary data


Re: patch kernel 3.2.0-3 , add bluetooth 0489:e046 Foxconn / Hon Hai

2012-07-26 Thread koko Aborigines
sry forgot lsusb

# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 003: ID 1bcf:2c18 Sunplus Innovation Technology Inc.
Bus 003 Device 004: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 003 Device 007: ID 0489:e046 Foxconn / Hon Hai

thank you

On Fri, Jul 27, 2012 at 11:11 AM, koko Aborigines 7aborigin...@gmail.comwrote:

 patch kernel 3.2.0-3 , add bluetooth 0489:e046 Foxconn / Hon Hai

 # uname -r
 3.2.0-3-amd64

 # lsb_release -a
 Distributor ID:Debian
 Description:Debian GNU/Linux testing (wheezy)
 Release:testing
 Codename:wheezy


 # usb-devices
 T:  Bus=03 Lev=02 Prnt=02 Port=02 Cnt=03 Dev#=  7 Spd=12  MxCh= 0
 D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
 P:  Vendor=0489 ProdID=e046 Rev=01.12
 S:  Manufacturer=Broadcom Corp
 S:  Product=BCM20702A0
 S:  SerialNumber=C01885F67F9E
 C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
 I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
 I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
 I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
 I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

 thanks you