On Tue, 26 Mar 2013, Noone Nowhere wrote:
> Hello again Alan, we read that the patch broke.
What patch? The one that works around the Intel/AMD hardware problem?
Yes, it had a mistake, which has now been fixed. (Although the fix has
not yet been released in a 3.8.stable kernel.)
> Damn, ou
Hello again Alan, we read that the patch broke. Damn, our fear was
justified. If we are right, it will break again because it affects
various
devices using different busses, each one with its limitations and
defects. That's why we wrote to Sarah(and got no reply yet) that
vendors
should fix their h
On Tue, 19 Mar 2013, Noone Nowhere wrote:
> > That depends on where the bug is. If it is in the stick then testing
> > a different brand of flash drive would help.
>
> Does it need an unusual dev entry to limit max sectors? It is the
> first USB stick that arrived here back in 2003(?) and uses S
On Mon, 18 Mar 2013, Noone Nowhere wrote:
> > I can't fix the block count issue. That's not a bug in the program;
> > it's a bug somewhere else.
>
> Who can fix it? Should we test another stick?
That depends on where the bug is. If it is in the stick then testing
a different brand of flash dr
On Fri, Mar 15, 2013 at 11:08:12AM -0400, Alan Stern wrote:
> On Fri, 15 Mar 2013, Noone Nowhere wrote:
>
> > Hello Alan again, we will clear things up. Sorry for the late reply,
> > dark forces delayed us.
> >
> >
> > > Intel probably doesn't care, because they don't make the affected
> > > chi
On Fri, 15 Mar 2013, Noone Nowhere wrote:
> Hello ,here are the logs from the failing EHCI hosts(chipset-SL
> Spec/revision@mainboard-system):
>
>
> ICH4-SL66K@FIC VC37
> 00:1d.7 USB Controller [0c03]: Intel Corporation 82801DB/DBM
> (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 01) (prog-
On Fri, 15 Mar 2013, Noone Nowhere wrote:
> USB stick on 12 different EHCI USB hosts. On VT8235M it took ages to
> go to 1000. A human readable timestamp could be used.
Evidently the VT8235M is very slow for some of the operations used by
the test program.
> To sum up printing a start up messag
On Fri, 15 Mar 2013, Noone Nowhere wrote:
> Hello Alan again, we will clear things up. Sorry for the late reply,
> dark forces delayed us.
>
>
> > Intel probably doesn't care, because they don't make the affected
> > chipsets any more. I don't know what AMD is currently making. Do you?
>
> Ye
Hello ,here are the logs from the failing EHCI hosts(chipset-SL
Spec/revision@mainboard-system):
ICH4-SL66K@FIC VC37
00:1d.7 USB Controller [0c03]: Intel Corporation 82801DB/DBM
(ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 01) (prog-if 20
[EHCI])
Subsystem: FIRST INTERNATIONAL Comp
Hello Alan again, we will clear things up. Sorry for the late reply,
dark forces delayed us.
> Intel probably doesn't care, because they don't make the affected
> chipsets any more. I don't know what AMD is currently making. Do you?
Yes we do. One of our ICH5 board uses ICH5 with SL7YC SL spec
On Mon, 11 Mar 2013, Noone Nowhere wrote:
> Hello Alan this is VoRTeX from the linux kernel ata wiki, greetings
> from the occupied Greece...Nick uses UNIX since 2003 (FreeBSD back
> then...5.2.1) and after all these years
> is an expert in Linux and in HDDs. In 2008 a repeated silent data
> corru
On Fri, 8 Mar 2013, Roger Quadros wrote:
> On 03/04/2013 05:36 AM, Ming Lei wrote:
> > On Tue, Feb 26, 2013 at 4:54 AM, Alan Stern
> > wrote:
> >
> >>
> >> I'd be interested to hear the results of testing on a variety of
> >> controllers. (This computer also has an NEC EHCI controller, and tha
On 03/04/2013 05:36 AM, Ming Lei wrote:
> On Tue, Feb 26, 2013 at 4:54 AM, Alan Stern wrote:
>
>>
>> I'd be interested to hear the results of testing on a variety of
>> controllers. (This computer also has an NEC EHCI controller, and that
>> one does not have the bug.) Do the EHCI controllers o
Hi Matthieu,
On 3/5/2013 16:52, Matthieu CASTET wrote:
Do you know which vendor did the ehci IP that is in your atmel SOC.
I am sorry, I don't know the vendor of the ehci IP.
Best Regards,
Bo Shen
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a messag
On Tue, 5 Mar 2013, Lan Tianyu wrote:
> Ok apply it. Retest. No problem.
>
> The following log only takes place When I stop ehci-test or unplug
> device during test.
> [ 140.871303] ehci-pci :00:1a.0: shutdown urb 88014545f0c0 ep1in-bulk
> [ 140.878231] ehci-pci :00:1a.0: shutdown u
Bo Shen a écrit :
> Hi Alan,
>
> On 3/4/2013 23:16, Alan Stern wrote:
>> On Mon, 4 Mar 2013, Bo Shen wrote:
>>
>>> Hi Alan,
>>>
>>> On 02/26/2013 04:54 AM, Alan Stern wrote:
Sarah (and anyone else who's interested):
A while ago I wrote about a hardware bug in my Intel ICH5 and ICH8
Hi Alan,
On 3/4/2013 23:16, Alan Stern wrote:
On Mon, 4 Mar 2013, Bo Shen wrote:
Hi Alan,
On 02/26/2013 04:54 AM, Alan Stern wrote:
Sarah (and anyone else who's interested):
A while ago I wrote about a hardware bug in my Intel ICH5 and ICH8 EHCI
controllers. You pointed out that these are
On Mon, 4 Mar 2013, [ISO-8859-1] Frank Sch�fer wrote:
> Here is the result of your test procedure (fix applied, running kernel
> 3.9-rc1) for the following device:
>
> 00:02.1 USB controller [0c03]: NVIDIA Corporation MCP61 USB 2.0
> Controller [10de:03f2] (rev a2) (prog-if 20 [EHCI])
> S
Am 25.02.2013 21:54, schrieb Alan Stern:
> Sarah (and anyone else who's interested):
>
> A while ago I wrote about a hardware bug in my Intel ICH5 and ICH8 EHCI
> controllers. You pointed out that these are rather old components, not
> being used in current systems, which is quite true.
>
> Now I
On Mon, 4 Mar 2013, Lan Tianyu wrote:
> Test on the Sandybridge platform.
> At the first time, I get following output. But after that, I was
> hard to get any output. And test on the v3.8.
You have to unplug the flash drive after running the test each time.
By the way, be sure to apply Clemens L
On Mon, 4 Mar 2013, Bo Shen wrote:
> Hi Alan,
>
> On 02/26/2013 04:54 AM, Alan Stern wrote:
> > Sarah (and anyone else who's interested):
> >
> > A while ago I wrote about a hardware bug in my Intel ICH5 and ICH8 EHCI
> > controllers. You pointed out that these are rather old components, not
> >
On Mon, 4 Mar 2013, Ming Lei wrote:
> On Tue, Feb 26, 2013 at 4:54 AM, Alan Stern wrote:
>
> >
> > I'd be interested to hear the results of testing on a variety of
> > controllers. (This computer also has an NEC EHCI controller, and that
> > one does not have the bug.) Do the EHCI controllers
2013/2/26 Alan Stern :
> Sarah (and anyone else who's interested):
>
> A while ago I wrote about a hardware bug in my Intel ICH5 and ICH8 EHCI
> controllers. You pointed out that these are rather old components, not
> being used in current systems, which is quite true.
>
> Now I have figured out a
Hi Alan,
On 02/26/2013 04:54 AM, Alan Stern wrote:
Sarah (and anyone else who's interested):
A while ago I wrote about a hardware bug in my Intel ICH5 and ICH8 EHCI
controllers. You pointed out that these are rather old components, not
being used in current systems, which is quite true.
I te
On Tue, Feb 26, 2013 at 4:54 AM, Alan Stern wrote:
>
> I'd be interested to hear the results of testing on a variety of
> controllers. (This computer also has an NEC EHCI controller, and that
> one does not have the bug.) Do the EHCI controllers on current Intel
> chipsets pass the test? What
On Sat, 2 Mar 2013, Clemens Ladisch wrote:
> > At any rate, if you're interested in finding out what the problem might
> > be, the best place to start would be with a usbmon trace.
>
> ehci-test:
> 8801e96c06c0 2335244662 S Bo:1:018:1 -115 31 = 55534243 6500 0400
> 0a28
Alan Stern wrote:
> On Sat, 2 Mar 2013, Clemens Ladisch wrote:
>> But the "timed out" messages come regularly every two seconds, which
>> appears to indicate that the test program doesn't manage to do what it
>> wants to do.
>
> Possibly. The program uses a 2-second timeout, which explains the
> r
On Sat, 2 Mar 2013, Bjørn Mork wrote:
> Alan Stern writes:
>
> > A while ago I wrote about a hardware bug in my Intel ICH5 and ICH8 EHCI
> > controllers. You pointed out that these are rather old components, not
> > being used in current systems, which is quite true.
>
> Just tested on my (al
On Sat, 2 Mar 2013, Clemens Ladisch wrote:
> >> Transcend JetFlash:
> >>
> >> ./ehci-test /dev/bus/usb/001/007
> >> URB timed out; bug may be present
> >> URB timed out; bug may be present
> >> URB timed out; bug may be present
> >> URB timed out; bug may be present
...
> All three devices on th
Alan Stern writes:
> A while ago I wrote about a hardware bug in my Intel ICH5 and ICH8 EHCI
> controllers. You pointed out that these are rather old components, not
> being used in current systems, which is quite true.
Just tested on my (almost as old) laptop with Intel ICH9 EHCI
controllers
Alan Stern wrote:
> On Sat, 2 Mar 2013, Clemens Ladisch wrote:
>> Alan Stern wrote:
>>> Then plug in an ordinary USB flash drive and run the attached
>>> program (as root), giving it the device path for the flash
>>> drive as the single command-line argument. For example:
>>>
>>>
On Sat, 2 Mar 2013, Clemens Ladisch wrote:
> Alan Stern wrote:
> > Then plug in an ordinary USB flash drive and run the attached
> > program (as root), giving it the device path for the flash
> > drive as the single command-line argument. For example:
> >
> > sudo ./ehci-t
Alan Stern wrote:
> Then plug in an ordinary USB flash drive and run the attached
> program (as root), giving it the device path for the flash
> drive as the single command-line argument. For example:
>
> sudo ./ehci-test /dev/bus/usb/002/003
>
> The program won't d
On Mon, Feb 25, 2013 at 03:54:22PM -0500, Alan Stern wrote:
> Sarah (and anyone else who's interested):
>
> A while ago I wrote about a hardware bug in my Intel ICH5 and ICH8 EHCI
> controllers. You pointed out that these are rather old components, not
> being used in current systems, which is q
34 matches
Mail list logo
