> 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 oth
> > 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 stil
> 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
> 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:
> I will now try 2.6.11.8 on the embedded board and see what happens.
OK, did that.
And this definitely fails on the embedded part.
Any ideas on what to try next?
Dag
---
SF.Net
> 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
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.
>
>
> 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
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
the controller detected a PID check error. If I read the
Second boot of the SCSI-patched kernel gave me an oops.
But this time in a different part of the kernel
Dag
Jun 10 19:06:01 (none) syslog.info syslogd started: BusyBox v1.00
(2005.06.08-11:53+)
Jun 10 19:06:03 (none) kern.notice kernel: klogd started: BusyBox v1.00
(2005.06.08-11:53+)
J
Update:
Just bought another USB 2.0 stick, a Sandisk 512 MB.
This seems to work fine in the system.
So the problem is not 1.1/2.0, but something else.
The stick I am seeing problems with is a Fujitsu Siemens
giveaway with the text Memorybird L PQ-T64 on it.
Dag
-
> On Wed, 8 Jun 2005, Dag Nygren wrote:
>
> > There is also no swap available and 28 MB memory available only.
> > Does that make a difference
>
> It might, if you were to use up all the memory.
Yes, of course. But I am trying to use as little memory as possible
and so
Sorry,
forgot the attachment with the log.
Also forgot to mention that the thing seems to work perfectly
with a USB 1.1 stick.
Dag
Jun 9 19:45:08 (none) syslog.info syslogd started: BusyBox v1.00
(2005.06.08-11:53+)
Jun 9 19:45:10 (none) kern.notice kernel: klogd started: BusyBox v1.00
(
Finally got a chance to continue this thing.
> On Sun, 5 Jun 2005, Dag Nygren wrote:
> That's supposed to work. It could be there's something wrong with your
> OHCI host controller...
The controller is an integrated SGS Thompson USB controller used in
many laptops.
>
> On Sat, 4 Jun 2005, Dag Nygren wrote:
> > usb-storage: Status code -71; transferred 512/4096
> > usb-storage: -- unknown error
> > usb-storage: Bulk data transfer result 0x4
> > usb-storage: -- transport indicates error, resetting
> > usb-storage: usb_stor_
>
> Try turning on CONFIG_USB_STORAGE_DEBUG. The debugging log will provide
> information about what's going wrong.
OK, did that
here is the result:
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-sto
17 matches
Mail list logo
