On Tue, 5 Dec 2006 [EMAIL PROTECTED] wrote:
> On 12/5/06, David Brownell <[EMAIL PROTECTED]> wrote:
> > Which is further evidence that the bottleneck is either in the mass storage
> > protocol (it has no pipelining) or in the peripheral silicon ... since the
> > disks themselves are often capable
On Tuesday 05 December 2006 7:17 pm, [EMAIL PROTECTED] wrote:
> On 12/5/06, David Brownell <[EMAIL PROTECTED]> wrote:
> > Which is further evidence that the bottleneck is either in the mass storage
> > protocol (it has no pipelining) or in the peripheral silicon ... since the
> > disks themselves a
On 12/5/06, David Brownell <[EMAIL PROTECTED]> wrote:
> Which is further evidence that the bottleneck is either in the mass storage
> protocol (it has no pipelining) or in the peripheral silicon ... since the
> disks themselves are often capable of more than 50 MB/sec.
For short bursts, perhaps, b
On Tue, 5 Dec 2006 10:46:49 -0500 (EST)
Alan Stern wrote:
> On Tue, 5 Dec 2006, Oliver Neukum wrote:
>
> > > Stated differently, USB 2.0 has a theoretical max of 480Mbps,
> > > which is 60 MB/sec, but in actual practice only about 50% of that
> > > is attainable.
> >
> > That's not really fair.
On Tuesday 05 December 2006 4:11 am, David Relson wrote:
> Good info. So 28 is achievable and 33 is out of reach.
For mass storage devices, I've never seen 33. I've seen a bit over 30;
the primary bottleneck seems to be inside the mass-storage device, rather
than on the host side.
> Stated di
On Tue, 5 Dec 2006, Oliver Neukum wrote:
> > Stated differently, USB 2.0 has a theoretical max of 480Mbps, which is
> > 60 MB/sec, but in actual practice only about 50% of that is attainable.
>
> That's not really fair. The protocol itself makes reservations of bandwidth
> for control transfers a
Am Dienstag, 5. Dezember 2006 13:11 schrieb David Relson:
> On Mon, 4 Dec 2006 20:09:05 -0800
> David Brownell wrote:
>
> > On Sunday 03 December 2006 9:36 am, David Relson wrote:
> > > On Sun, 3 Dec 2006 12:31:56 -0500 (EST)
> >
> > > By the way, I had measured throughput to the USB drive and fo
On Mon, 4 Dec 2006 20:09:05 -0800
David Brownell wrote:
> On Sunday 03 December 2006 9:36 am, David Relson wrote:
> > On Sun, 3 Dec 2006 12:31:56 -0500 (EST)
>
> > By the way, I had measured throughput to the USB drive and found
> > I could transfer a 1GB file from internal HD to the USB in 57.9
On Sunday 03 December 2006 9:36 am, David Relson wrote:
> On Sun, 3 Dec 2006 12:31:56 -0500 (EST)
> By the way, I had measured throughput to the USB drive and found
> I could transfer a 1GB file from internal HD to the USB in 57.9
> seconds, which translates to 18.5 MB/sec. Would that be
> consid
On Sun, 3 Dec 2006, David Relson wrote:
> Hi Alan,
>
> Most of the patch applies fine, but there were several rejects. It
> seems that end_unlink_async () has change from 2 arguments (in 2.6.17)
> to 1 argument (in 2.6.19). I've made manual changes as best I can.
>
> However the patch does cau
On Sun, 3 Dec 2006 12:31:56 -0500 (EST)
Alan Stern wrote:
...[snip]
> In fact you've got a combination of two problems, which may or may
> not be related. First is the random disconnects; they would mess up
> your backups in any case. Second is the hang that occurs during the
> disconnect p
On Sat, 2 Dec 2006, David Relson wrote:
> On Sat, 2 Dec 2006 17:08:02 -0500 (EST)
> Alan Stern wrote:
>
> ...[snip]...
>
> > Remind me of the context again; it has slipped my mind. You were
> > getting random disconnects that sometimes (or always?) ended up
> > hanging the USB subsystem?
>
> G
On Sat, 2 Dec 2006 17:08:02 -0500 (EST)
Alan Stern wrote:
> On Sat, 2 Dec 2006, David Relson wrote:
[snip]
> Remind me of the context again; it has slipped my mind. You were
> getting random disconnects that sometimes (or always?) ended up
> hanging the USB subsystem?
>
> The logs you
On Sat, 2 Dec 2006 17:08:02 -0500 (EST)
Alan Stern wrote:
...[snip]...
> Remind me of the context again; it has slipped my mind. You were
> getting random disconnects that sometimes (or always?) ended up
> hanging the USB subsystem?
Good question. I'm using program BackupPC and a USB hard driv
On Sat, 2 Dec 2006, David Relson wrote:
> Hi Alan,
>
> I had another USB hang this morning. Attached are the relevant
> lines from /var/log/messages and the output of dmesg (after SYS-REQ-T).
> Unfortunately, CONFIG_LOG_BUF_SHIFT is 15 (a long story with which I
> shall not bore you) so all the
On Wednesday 11 August 2004 6:48 am, Alan Stern wrote:
> I'd be surprised if usb_kill_urb() turns out to be the problem. (Of
> course, as it's author I would say that!) After all, the "control timeout
> on ep0out" message comes from a handler that gets invoked only for URBs
> submitted using
On Tue, 10 Aug 2004, David Brownell wrote:
> On Tuesday 10 August 2004 2:12 pm, Russell King wrote:
> > Hi,
> >
> > While fiddling with 2.6.8-rc3 with a SA-based host, I came across
> > the following error message after unplugging and replugging a USB
> > pen drive (the swissbit thing that wa
On Tuesday 10 August 2004 4:17 pm, Randy.Dunlap wrote:
> On Tue, 10 Aug 2004 16:13:28 -0700 David Brownell wrote:
> | Is this the same device you had problems with there? And have
> | you verified that it works OK on some system (preferably Linux)?
>
> Mine works on a IBM ThinkPad A21m and Linux
On Tue, 10 Aug 2004 16:13:28 -0700 David Brownell wrote:
| On Tuesday 10 August 2004 2:12 pm, Russell King wrote:
| > Hi,
| >
| > While fiddling with 2.6.8-rc3 with a SA-based host, I came across
| > the following error message after unplugging and replugging a USB
| > pen drive (the swissbit
On Tuesday 10 August 2004 2:12 pm, Russell King wrote:
> Hi,
>
> While fiddling with 2.6.8-rc3 with a SA-based host, I came across
> the following error message after unplugging and replugging a USB
> pen drive (the swissbit thing that was at KernelSummit):
Is this the same device you had pro
Am Mittwoch, 2. Juni 2004 23:27 schrieb Ville Pätsi:
> These 0.3K bytes were from Oliver Neukum,
> > > > > device hangs. The program does not respond anymore and ps lists its
> > > > > state as DW. The device is completely hung up at this point, and refuses
> > > > Could you get a backtrace with sy
These 0.3K bytes were from Oliver Neukum,
> > > > device hangs. The program does not respond anymore and ps lists its
> > > > state as DW. The device is completely hung up at this point, and refuses
> > > Could you get a backtrace with sysreq of such a hung task?
> Please try with "acpi=off"
This
On Tue, 1 Jun 2004, Ville Pätsi wrote:
> I found these in syslog when looking for the Sysrq trace:
>
>
> Jun 1 12:15:30 meri kernel: irq 7: nobody cared!
> Jun 1 12:15:30 meri kernel: Call Trace:
> Jun 1 12:15:30 meri kernel: [] __report_bad_irq+0x2a/0x90
> Jun 1 12:15:30 meri kernel: [] n
These 0.3K bytes were from Oliver Neukum,
> Am Dienstag, 1. Juni 2004 12:41 schrieb Ville Pätsi:
> > Oliver Neukum,
> > > > device hangs. The program does not respond anymore and ps lists its
> > > > state as DW. The device is completely hung up at this point, and refuses
> > > Could you get a back
Am Dienstag, 1. Juni 2004 12:41 schrieb Ville Pätsi:
> Oliver Neukum,
> > > device hangs. The program does not respond anymore and ps lists its
> > > state as DW. The device is completely hung up at this point, and refuses
> > Could you get a backtrace with sysreq of such a hung task?
Please try w
Oliver Neukum,
> > device hangs. The program does not respond anymore and ps lists its
> > state as DW. The device is completely hung up at this point, and refuses
> Could you get a backtrace with sysreq of such a hung task?
Here:
VisualBoyAdva D 15223944 0 30964 30963 30965 (
On Mon, 31 May 2004, Ville Pätsi wrote:
> I suffer from the same application hang with usb devices that others
> seem to have encountered too. USB devices work fine after bootup, but
> after the system has been up a while any application accessing a usb
> device hangs. The program does not respond
These 0.5K bytes were from Oliver Neukum,
> Am Montag, 31. Mai 2004 15:54 schrieb Ville Pätsi:
> > I suffer from the same application hang with usb devices that others
> > seem to have encountered too. USB devices work fine after bootup, but
> > after the system has been up a while any application
Am Montag, 31. Mai 2004 15:54 schrieb Ville Pätsi:
> I suffer from the same application hang with usb devices that others
> seem to have encountered too. USB devices work fine after bootup, but
> after the system has been up a while any application accessing a usb
Accessing in which way?
> device
29 matches
Mail list logo
