Alan Stern wrote:
On Fri, 19 Mar 2004, Brad Campbell wrote:
Funny you should mention that, It's exactly what I spent all morning doing
After more investigation it comes down to 4 bytes that cross the sector boundary
bklaptop:~>hexdump lf3
000
*
1f
This message was created automatically by mail delivery software (Exim).
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[EMAIL PROTECTED]
SMTP error from remote mailer after end of data:
host
Am Friday 19 March 2004 18:53 schrieb Pete Zaitcev:
> On Fri, 19 Mar 2004 16:14:56 +0100
> Oliver Neukum <[EMAIL PROTECTED]> wrote:
>
> > open() is (for char devices) still called under BKL, so this is
> > just uselessly eating cycles. And, more importantly, locking
> > is not thought through. It
Hi,
there's a race in how open handles multiple openers.
You implement exclusive opening and wait for close
in case of further openers. However if there are more than one
waiter, only one of them must be allowed to proceed.
Regards
Oliver
You can import this changeset int
Hallo List, maybe special to Alan Stern,
i also have problems with the genesys adapter in an external box and
read the thread in here.
First i wrote to linux-usb-users list, perhaps the wrong place. Now i
will try to summarize my experiences here. If it's double, please excuse.
For Information: i
Hello,
with 2.6.4 if I do rmmod uhci_hcd and then modprobe uhci_hcd while running
X server with USB mouse connected to UHCI USB I got:
uhci_hcd :00:1d.2: USB bus 3 deregistered
slab error in kmem_cache_destroy(): cache `uhci_urb_priv': Can't free all object
s
Call Trace:
[] kmem_cache_destroy
This message was created automatically by mail delivery software (Exim).
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[EMAIL PROTECTED]
SMTP error from remote mailer after RCPT TO:<[EMAIL PROTEC
On Fri, Mar 19, 2004, Pete Zaitcev <[EMAIL PROTECTED]> wrote:
> On Fri, 19 Mar 2004 17:07:04 -0500 (EST)
> Alan Stern <[EMAIL PROTECTED]> wrote:
>
> > This patch introduces a major simplification into the UHCI driver by
> > replacing its multiple spinlocks with a single one. []
>
> About time! I
On Fri, Mar 19, 2004 at 09:03:15AM +0300, Andrew Zabolotny wrote:
> On Thu, 18 Mar 2004 19:19:05 +0530 (IST)
> "navtez" <[EMAIL PROTECTED]> wrote:
>
> > i have just started work on USB IrDA. the device on whih i m working has
> > bulk in end pt: 82 and bulk out end pt: 1.
> A bit off-topic: is the
Stephen Hemminger wrote:
I got this crash (twice) on 2.6.4 with IRDA dongle; the driver does a lot
link/unlink and this is an SMP box, so this looks like a race.
See if the attached patch helps. I've done 24+ hours of abusive SMP unlink
testing on OHCI ... but that included this patch.
Also, this
Alan Stern <[EMAIL PROTECTED]> writes:
> It would help to know what gphoto2 is doing. There should be more
> debugging in the usbfs driver, without it we're sort of in the dark.
> However, you can try using strace on the gphoto2 program; that will give
> us some idea of what's going on.
gpho
On Fri, 19 Mar 2004 17:07:04 -0500 (EST)
Alan Stern <[EMAIL PROTECTED]> wrote:
> This patch introduces a major simplification into the UHCI driver by
> replacing its multiple spinlocks with a single one. []
About time! I cannot resist to observe that Georg Archer and I
did this in usb-uhci long
On Fri, 19 Mar 2004, Sean Neakums wrote:
> Here are the results with 2.6.5-rc1-mm2 on the laptop:
>
> Plug in:
> Mar 19 17:02:55 revox kernel: uhci_hcd :00:1d.0: wakeup_hc
> Mar 19 17:02:55 revox kernel: uhci_hcd :00:1d.0: port 1 portsc 0083
> Mar 19 17:02:55 revox kernel: hub
On Fri, 19 Mar 2004, Max Zaitsev wrote:
> > Maybe not. If you haven't already, take a look at this thread:
> >
> > http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107962180123336&w=2
> >
> > You should see if your device behaves in the same way.
> >
> it does not crash with that short sequence
On Fri, 19 Mar 2004, Max Zaitsev wrote:
> I couldn't crash my drive with the byte sequence given. However, it crashes if
> I try to transfer 1GB of zeroes:
>
> dd if=/dev/zero of=/dev/sda8 bs=16M count=1G
>
> kills the device with a 100% probability. With regard to Windows -- I've
> managed to
On Fri, 19 Mar 2004, Jens Benecke wrote:
> Well, my question was if the USB attempts can generate spurious writes and
> trash the partition table. If I cannot access the partition table via USB
> because the USB controller is broken, that's bad, but it's not fatal. But
> if the connection attem
Greg:
This patch simplies the way the UHCI driver handles short control
transfers. When a transfer is short the HC will stop handling that
endpoint, and it's necessary to get it going again so that the status
stage of the control transfer can take place. Currently the driver does
this by allocat
Greg:
This patch introduces a major simplification into the UHCI driver by
replacing its multiple spinlocks with a single one. The protected area of
code is slightly larger and there's more possibilities for contention on
an SMP system, but I think that shouldn't be a problem. Stephen Hemming
Greg:
This patch makes some simple changes to the way the UHCI driver does short
packet detection. The current implementation is incorrect in several
ways:
The Short-Packet-Detect flag is set for OUT transfers, which
yields undefined behavior according to the UHCI spec.
Greg:
This is a very minor point, unlikely ever to come up. But just in case...
It's conceivable that a device might transmit different values for a
configuration descriptor's wTotalLength the first time we ask for it (in
order to get the length) and the second time (to get the entire
descrip
I got this crash (twice) on 2.6.4 with IRDA dongle; the driver does a lot
link/unlink and this is an SMP box, so this looks like a race.
SMP
CPU:0
EIP:0060:[]Not tainted
EFLAGS: 00210086 (2.6.4-tcp)
EIP is at urb_free_priv+0xe/0x40 [ohci_hcd]
eax: f5f5d800 ebx: e7b5c800 ecx:
I would like to submit a patch that adds support for EHCI
root hubs with a transaction translator. The root hub on ARC
International's EHCI controller has a built in transaction
translator. This allows the EHCI controller to communicate
with low and full speed devices without the use of a USB1
Am Friday 19 March 2004 20:52 schrieb Pete Zaitcev:
> On Fri, 19 Mar 2004 19:10:35 +0100
> Oliver Neukum <[EMAIL PROTECTED]> wrote:
>
> > > What do you think about the attached patch?
> >
> > Much, much better :-)
> > Except that you forgot to initialise the semaphore.
>
> You are right. I suppo
On Fri, 19 Mar 2004 19:10:35 +0100
Oliver Neukum <[EMAIL PROTECTED]> wrote:
> > What do you think about the attached patch?
>
> Much, much better :-)
> Except that you forgot to initialise the semaphore.
You are right. I suppose just replacing it with DECLARE_MUTEX ought
to do the trick.
I take
On Fri, 19 Mar 2004 19:10:35 +0100
Oliver Neukum <[EMAIL PROTECTED]> wrote:
> Except that you forgot to initialise the semaphore.
Now actually with a patch for 2.4.
--- linux-2.4.26-pre2/drivers/usb/printer.c 2004-02-26 14:09:58.0 -0800
+++ linux-2.4.26-pre2-nip/drivers/usb/printer.c
On Fri, 19 Mar 2004 08:32:01 +0100
<[EMAIL PROTECTED]> wrote:
> Andrew Zabolotny <[EMAIL PROTECTED]> schrieb am 19.03.2004, 07:03:15:
> > can't help them. As far as I understand, USB IrDA dongles are seen
> > only as network interface or via ircomm, am I wrong?
> For me it works without problems.
Hallo List, maybe special to Alan Stern,
i also have problems with the genesys adapter in an external box and
read the thread in here.
First i wrote to linux-usb-users list, perhaps the wrong place. Now i
will try to summarize my experiences here. If it's double, please excuse.
For Information: i
On Fri, 19 Mar 2004 16:14:56 +0100
Oliver Neukum <[EMAIL PROTECTED]> wrote:
> open() is (for char devices) still called under BKL, so this is
> just uselessly eating cycles. And, more importantly, locking
> is not thought through. It is correct by accident currently.
I wouldn't touch it before a
Hallo Max Zaitsev ,
>>> Actually, another sanity check was to try to operate the device from
>>> within vmware. And it worked! Slow, but worked. I think vmware uses EHCI
i made some experience with Windows-XP in vmware. Could burn with about
1500kb/s to the usb-device. See my posting for
"agai
Hallo List, maybe special to Alan Stern,
just happend:
>I tried difference things, especially because the 4081 also can use
>DVD-RAM. It was possible to copy files to the BOX on dvd-ram with
>mc without problems.
i tried to copy a 1GB file with cp to dvd-ram, and got also the break
bulk:timeou
Matthew Dharm wrote:
On Thu, Mar 18, 2004 at 08:17:00PM -0800, David Brownell wrote:
Pat LaVarre wrote:
Agreed, shattering a read/ write stream into miniscule pieces improves
interop at small cost to typical usage of much storage.
It improves interop, yes ... but that cost would only be small
for
Alan Stern <[EMAIL PROTECTED]> writes:
> On Thu, 18 Mar 2004, Sean Neakums wrote:
>
>> On one machine (a Dell Inspiron 4100 laptop), with 2.6.5-rc1-mm2 and
>> 2.6.5-rc1-mm1, but not with 2.6.5-rc1, gphoto2 hangs trying to talk to
>> my camera:
>>
>> $ ps -C gphoto2 -o comm,s,wchan
>> COMM
> Maybe not. If you haven't already, take a look at this thread:
>
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=107962180123336&w=2
>
> You should see if your device behaves in the same way.
>
it does not crash with that short sequence (see my other post)
> > Actually, another sanity check
I couldn't crash my drive with the byte sequence given. However, it crashes if
I try to transfer 1GB of zeroes:
dd if=/dev/zero of=/dev/sda8 bs=16M count=1G
kills the device with a 100% probability. With regard to Windows -- I've
managed to copy 30-40 GB of media files to the drive and did not
On Fri, 19 Mar 2004, David Brownell wrote:
> Alan Stern wrote:
>
> >It sure looks as though usbmodules could stand a little rewriting. The
>
> Better still, it could be eliminated for 2.6 based distros,
> given code to handle "coldplug" by scanning sysfs.
Apparently, the newer hotplug code as
Alan Stern wrote:
It sure looks as though usbmodules could stand a little rewriting. The
Better still, it could be eliminated for 2.6 based distros,
given code to handle "coldplug" by scanning sysfs.
18-byte call is Get_Device_Descriptor, and the 9- and 32-byte calls are
Get_Configuration_Desc
[Removed Andrew Morton and LKML from CC: list]
On Thu, 18 Mar 2004, Sean Neakums wrote:
> On one machine (a Dell Inspiron 4100 laptop), with 2.6.5-rc1-mm2 and
> 2.6.5-rc1-mm1, but not with 2.6.5-rc1, gphoto2 hangs trying to talk to
> my camera:
>
> $ ps -C gphoto2 -o comm,s,wchan
> COMMA
On Fri, 19 Mar 2004, Brad Campbell wrote:
> Funny you should mention that, It's exactly what I spent all morning doing
>
> After more investigation it comes down to 4 bytes that cross the sector boundary
>
> bklaptop:~>hexdump lf3
> 000
> *
> 1f0 0
On Fri, 19 Mar 2004, Matthias Andree wrote:
> > On Thu, 18 Mar 2004, David Brownell wrote:
> >
> > > Software that tries to change the device configuration would
> > > certainly cause lots of hotplugging. Basically that's a bad
> > > idea. There's a call to just _reset_ the configuration, that
On Thu, 18 Mar 2004, Matthias Andree wrote:
> Some questions:
>
> 1. Should configuration changes be locked out while bulk transfers are
>in progress?
That's not a simple question. The short answer is that configuration
changes are already locked out while an individual bulk transfer is in
Am Freitag, 19. März 2004 16:05 schrieb Alan Stern:
> > Oops. I have only used this disk from the Firewire connector before.
> > Is it entirely possible that connecting it via USB might have trashed
> > contents on the disk?
> That's very unlikely.
Thank you. Also for your help. :)
> > Yesterda
On Thu, 18 Mar 2004, Urban Borstnik wrote:
> The 2.6.4 and 2.6.3 (and possibly some earlier) kernels log the
> following message when I plug in a Lexar CompactFlash Reader:
>
> usb-storage: This device (05dc,b002,0113 S 06 P 50) has unneeded
> SubClass and Protocol entries in unusual_devs.h
>
Hi,
open() is (for char devices) still called under BKL, so this is
just uselessly eating cycles. And, more importantly, locking
is not thought through. It is correct by accident currently.
Regards
Oliver
You can import this changeset into BK by piping this whole message
On Fri, 19 Mar 2004, Max Zaitsev wrote:
> Hi folks,
>
> I've tried the described experiment and what I've seen seem to tell me that
> it's really the device controller, who dies rather than anything in the host.
> First of all, when the controller dies the "connection" LED on the USB hub
> goe
On Fri, 19 Mar 2004, Jens Benecke wrote:
> > It looks like it's a problem with the drive. Each time the system tries
> > to read the extended partition table, it says it was just reset. That
> > reset flag (technically called Unit Attention) is supposed to be cleared
> > when the device sends it
On Thu, 18 Mar 2004, Pat LaVarre wrote:
> Agreed, shattering a read/ write stream into miniscule pieces improves
> interop at small cost to typical usage of much storage.
>
> Sorry I mistook the words "I wonder if we shouldn't reduce max_sectors
> permanently" as a disavowal of your cogent disc
Hi folks,
I've tried the described experiment and what I've seen seem to tell me that
it's really the device controller, who dies rather than anything in the host.
First of all, when the controller dies the "connection" LED on the USB hub
goes down. Secondly, the other USB2 device (usb-stick) c
Alan Stern wrote:
> On Thu, 18 Mar 2004, Jens Benecke wrote:
>
>> I have an external HDD (200G) in a case that has both FW and USB2
>> outputs. FW work great since 2.6.2, connecting the USB to a machine
>> running 2.4.23 instantly rebooted the machine, and in 2.6 (currently
>> 2.6.5rc1bk2) it
Alan Stern wrote:
On Thu, 18 Mar 2004, Brad Campbell wrote:
G'day all,
I have been beating this GeneSys adaptor to death and have found out it
appears to be a certain data sequence/packet that kills it.
Attached it a gzipped 1024 byte file. (It's gzipped just to add a crc to
it, it's out of an .
Thanks for your help Alan, it's much appreciated.
I'll report if I get any further.
Malcolm.
Alan Stern wrote:
That certainly looks like things go wrong just at the time the full-speed
bandwidth reclamation gets turned on. Why should FSBR cause any problems?
The only thing that occurs to me n
Andrew Zabolotny <[EMAIL PROTECTED]> schrieb am 19.03.2004, 07:03:15:
> can't help them. As far as I understand, USB IrDA dongles are seen
> only as network interface or via ircomm, am I wrong?
For me it works without problems.
modprobe
modprobe ircomm_tty
irattach irda0 -s
and then start minico
51 matches
Mail list logo
