Hi,
If I try to copy some file from usb stick to hard disk or other way
around there is big chance process will after some time hang forever
with buch of kernel messages about cam in console.
The only workaround I found is to use tools like rsync to limit transfer speed.
It happens with 2 differ
On Thu, Feb 24, 2011 at 2:31 PM, Bruce Cran wrote:
> Hi,
>
> I've been having various issues with my DVD writer on 9-CURRENT. It's a:
>
> cd0: Removable CD-ROM SCSI-0 device
>
> Firstly I noticed that sometimes FreeBSD puts it into some mode where
> the access light flashes continuously, but I ca
2010/11/19 Hans Petter Selasky :
> On Friday 19 November 2010 16:55:27 Lev Serebryakov wrote:
>> Hello, Freebsd-usb.
>>
>> I've implemented driver (ucom-subdriver) for MosChip 7820 and 7840
>> USB2COM multiport bridges. I have two questions:
>>
>
> Hi,
>
>> (1) How should I specify modu
On 9/29/10, Alexander Leidinger wrote:
> Hi,
>
> every half an hour I get two log entries in /var/log/messages. They
> look like this:
> ---snip---
> Sep 28 23:30:00 M87 root: Unknown USB device: vendor 0x1941 product
> 0x8021 bus uhub1
> Sep 28 23:30:00 M87 root: Unknown USB device: vendor 0x1941
On 3/30/10, Andrew Thompson wrote:
> On 30 March 2010 23:11, Arseny Nasokin wrote:
>> On 30 Mar 2010, at 08:00, Andrew Thompson wrote:
>>
>>> The following reply was made to PR usb/145184; it has been noted by
>>> GNATS.
>>>
>>> From: Andrew Thompson
>>> To: Gnats
>>> Cc: Eir Nym
>>> Subject:
On Sat, Mar 13, 2010 at 1:56 PM, Alexander Best wrote:
> Hans Petter Selasky schrieb am 2010-03-13:
>> On Saturday 13 March 2010 13:21:10 Paul B Mahol wrote:
>> > On 3/13/10, Alexander Best wrote:
>> > > Paul B Mahol schrieb am 2010-03-13:
>> > >> On
On 3/13/10, Alexander Best wrote:
> Paul B Mahol schrieb am 2010-03-13:
>> On 3/13/10, Alexander Best wrote:
>> > i'm sorry to hijack this thread, but i've been having similar
>> > issues as
>> > Vinicius with his PS3 controller with my logitech
On 3/13/10, Alexander Best wrote:
> i'm sorry to hijack this thread, but i've been having similar issues as
> Vinicius with his PS3 controller with my logitech cordless gamepad. this is
> the attach message:
>
> ugen3.3: at usbus3
> uhid0: addr
> 3> on usbus3
>
> the output of `usbhidctl -f /dev
->driver_ivar;
sc = (struct ndis_softc *)dummy;
sc->ndis_dev = self;
--
Paul B Mahol
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-u
On 10/21/09, Dan Langille wrote:
> bump
>
> On Wed, Jun 10, 2009 at 2:18 PM, Dan Langille
> wrote:
>
>> I'm running FreeBSD 7.2-STABLE from Tue May 26.
>>
>> I have an MS keyboard and mouse, both of which are wireless and
>> operate through the same USB transceiver. The keyboard works. The
>> mo
On 10/18/09, Alexander Best wrote:
> posted this to freebsd-questions@ a while ago and got no answer.
Similar to sound devices, they are created in /dev on request - when being used.
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mail
On 4/30/09, Gustau Pérez wrote:
>
>>> I think this is right place to post, if it is not, please let me know.
>>>
>> It is not usb fault, it is driver side fault.
>>
>>
>Thank you. I thought it was not an usb fault, because with stable
> (old usb stack) it shows the same behaviour.
>
>I p
On 4/26/09, Gustau Perez wrote:
>
> Hi,
>
> I think this is right place to post, if it is not, please let me know.
It is not usb fault, it is driver side fault.
>I'm experiencing problems with two different devices using if_rum.
> One is a Hercules Guillemot and the other is a Linksys Cis
On 4/5/09, Lars Eighner wrote:
> Somebody broke umass. All I am asking of that person is: when did
> you break umass, so I can downgrade to just before that.
I wished many times that, but unfortunately for you and
me that doesnt work in that way.
Could you remmember date of last working kernel?
On 4/3/09, Luchezar Georgieff wrote:
> Few more symptoms:
> If a station is assotiated and there is no traffiic load (ping only) I
> can destroy interface using ifconfig wlan0 destroy, but if I put some
> traffic on link and it hangs, after destroying interface get:
> Fatal trap 18: integer divide
On 2/16/09, Hans Petter Selasky wrote:
> Hi,
>
> As long as there are locking mechanisms like this:
>
> void
> KeAcquireSpinLockAtDpcLevel(kspin_lock *lock)
> {
> while (atomic_cmpset_acq_int((volatile u_int *)lock, 0, 1) == 0)
> /* sit and spin */;
>
> return;
> }
>
> in
On 2/10/09, Thomas Sparrevohn wrote:
> Reintroduced panics when the device is used heavily - it also reports the
> "needs callback" in dmesg - Unless this is known I can post a dmesg
"needs callback" is proper behaviour, previous versions wrongly
assumed that code should do nothing when such ca
On 11/9/08, Hans Petter Selasky <[EMAIL PROTECTED]> wrote:
> On Saturday 08 November 2008, Paul B. Mahol wrote:
>> On 11/7/08, Hans Petter Selasky <[EMAIL PROTECTED]> wrote:
>> > On Friday 07 November 2008, Paul B. Mahol wrote:
>> >> On 11/7/08
On 11/7/08, Hans Petter Selasky <[EMAIL PROTECTED]> wrote:
> On Friday 07 November 2008, Paul B. Mahol wrote:
>> On 11/7/08, M. Warner Losh <[EMAIL PROTECTED]> wrote:
>
>> > : > After some time it will appear but will start attaching and
>> > : >
On 11/7/08, M. Warner Losh <[EMAIL PROTECTED]> wrote:
> In message: <[EMAIL PROTECTED]>
> "Paul B. Mahol" <[EMAIL PROTECTED]> writes:
> : On 11/7/08, Paul B. Mahol <[EMAIL PROTECTED]> wrote:
> : > On 11/7/08, Paul B. Mahol <[EM
On recent CURRENT when attaching rum card, strange bug appear:
usb2_alloc_device:1417: set address 2 failed (ignored)
usb2_alloc_device:1452: getting device descriptor at addr 2 failed!
uhub_reattach_port:401: could not allocate new device!
uhub_reattach_port:355: port 5 reset failed, error=USB_E
On 11/7/08, Paul B. Mahol <[EMAIL PROTECTED]> wrote:
> On 11/7/08, Paul B. Mahol <[EMAIL PROTECTED]> wrote:
>> On recent CURRENT when attaching rum card, strange bug appear:
>>
>> usb2_alloc_device:1417: set address 2 failed (ignored)
>> usb2_alloc_device:14
On 11/7/08, Paul B. Mahol <[EMAIL PROTECTED]> wrote:
> On recent CURRENT when attaching rum card, strange bug appear:
>
> usb2_alloc_device:1417: set address 2 failed (ignored)
> usb2_alloc_device:1452: getting device descriptor at addr 2 failed!
> uhub_reattach_port:401: c
On 7/15/08, Paul Schmehl <[EMAIL PROTECTED]> wrote:
> --On Tuesday, July 15, 2008 11:23:09 +0200 "Paul B. Mahol"
> <[EMAIL PROTECTED]>
> wrote:
>>
>> Look in Developers handbook for more info
>> /usr/share/doc/en/books/developers-handbook/index.html
On 7/14/08, Paul Schmehl <[EMAIL PROTECTED]> wrote:
> I'd like to work with someone to provide useful information about this
> problem.
> Ever since upgrading my workstation to 7.0 STABLE, I cannot boot with my
> umass
> device connected. Once the system is up and running, I can mount the
> device
On 7/5/08, VVD <[EMAIL PROTECTED]> wrote:
> The following reply was made to PR usb/125264; it has been noted by GNATS.
>
> From: "VVD" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>,
> <[EMAIL PROTECTED]>
> Cc:
> Subject: Re: usb/125264: [patch] sysctl for set usb mouse rate (very useful
> f
{ USB_VENDOR_CISCOLINKSYS, USB_PRODUCT_CISCOLINKSYS_WUSB54GC },
is in if_rum.c
and in rum man page it is written with few letters more (dunno why).
So what is your problem?
On 6/24/08, Harry Matthiesen Jensen <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 24, 2008 at 10:27:29AM +020
That USB dongle is listed in rum man page.
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Look usb/124758, I think it is already known problem.
On 6/23/08, Thomas Sparrevohn <[EMAIL PROTECTED]> wrote:
> Hi
>
>
>
> Before I send a pr in - I just wanted to check whether the issue is known
>
>
>
> A seemly random period time after I plugin the rum0 device the kernel
> crashes
>
>
>
> rum0
29 matches
Mail list logo
