> On Tue, 28 Jun 2005, Dag Nygren wrote:
> It's safe to assume the sticky was faulty all along -- since nobody can
> possibly prove the assumption is wrong! As for the other three sticks...
> Who knows? But I wouldn't recommend that brand to anybody.
Well, the other 3 failing ones were differen
On Tue, 28 Jun 2005, Dag Nygren wrote:
> What is the recommended version of gcc to use for kernel compiling
> nowadays?
> I am using 3.4.3.
I don't think any particular version is "recommended". People are still
adding workarounds for gcc 2.95, so you can go back as far as that if you
wish. I
> > On Mon, 27 Jun 2005, Dag Nygren wrote:
> Just tried that and now the stick refuses to show up at all.
> But there seems to be no difference between the HUB and the direct
> connection to the computer.
> Also rebooted, but nothing helps. That stick is gone.
> I can still see the -110 errors __so
> On Mon, 27 Jun 2005, Dag Nygren wrote:
>
> > Jun 27 21:30:26 dag kernel: ohci_hcd :02:08.0: urb c198f760 path 2.4
> > ep0in
> > 5fc2 cc 5 --> status -110
> > Jun 27 21:30:26 dag kernel: hub 1-2:1.0: port 4 not reset yet, waiting 10ms
> > Jun 27 21:30:26 dag kernel: usb 1-2.4: device de
On Mon, 27 Jun 2005, Dag Nygren wrote:
> OK, here we go,
> I cut the part from insertion of the stick to where the errors stopped.
> I also noticed that there are no -71 errors here, only -110.
>
> Dag
> Jun 27 21:30:26 dag kernel: ohci_hcd :02:08.0: urb c198f760 path 2.4
> ep0in
> 5fc2000
> We should try to find out what those failed messages are. Turn on
> CONFIG_USB_STORAGE_DEBUG and CONFIG_USB_DEBUG (if you haven't already done
> so) for the 2.6.11.8 kernel and see what you get. Also, try running with
> hald turned off -- it generates a lot of messages on its own for USB ma
On Mon, 27 Jun 2005, Dag Nygren wrote:
> > On Mon, 27 Jun 2005, Dag Nygren wrote:
> > > Now we really have to go hunting for a bug in the OHCI driver.
> >
> > Can you go back to 2.6.11.8 and verify that the stick does work? If you
> > can pinpoint a change in the software responsible for the br
> On Mon, 27 Jun 2005, Dag Nygren wrote:
> > Now we really have to go hunting for a bug in the OHCI driver.
>
> Can you go back to 2.6.11.8 and verify that the stick does work? If you
> can pinpoint a change in the software responsible for the breakage, that
> would help a lot.
OK, just did th
On Mon, 27 Jun 2005, Dag Nygren wrote:
>
> Just an update,
>
> I just plugged in the failing stick in my desktop computer which earlier
> did work with that stick, then on kernel version 2.6.11.8.
> This has now been updated to 2.6.12.1 and an additional USB hub
> has been added.
> But the inter
On Mon, 27 Jun 2005, Dag Nygren wrote:
> > I would guess that it is initialized to 0 along with everything else in
> > the TD at the time the memory for the TD is allocated and cleared.
>
> Is it cleared then? (Haven't checked yet)
I don't know either. I said I was guessing...
> > You could t
Just an update,
I just plugged in the failing stick in my desktop computer which earlier
did work with that stick, then on kernel version 2.6.11.8.
This has now been updated to 2.6.12.1 and an additional USB hub
has been added.
But the interesting thing is that I got exectly the same error here n
> On Mon, 27 Jun 2005, Dag Nygren wrote:
>
> I would guess that it is initialized to 0 along with everything else in
> the TD at the time the memory for the TD is allocated and cleared.
Is it cleared then? (Haven't checked yet)
> > Just tell me if I can help.
>
> You could try out the patch in
On Mon, 27 Jun 2005, Dag Nygren wrote:
> Well, I just checked a bit more and it seems like the OHCI device has already
> tried 3 times before it reports a failure. What is interesting though is that
> the OHCI
> specs states that a field called ErrorCount in the should be initialized to 0
> by t
> On Mon, 27 Jun 2005, Dag Nygren wrote:
>
> > All the problems seems to occur after a report back from the
> > USB controller with the cc register set at 6. This means that
> > the controller detected a PID check error. If I read the specs right
> > this transfer should then be retried (by the US
On Mon, 27 Jun 2005, Dag Nygren wrote:
> Hi again,
>
> remember me with the USB memory problems?
>
> Anyway I studied a little of the USB specs and have a question:
>
> All the problems seems to occur after a report back from the
> USB controller with the cc register set at 6. This means that
>
15 matches
Mail list logo
