On Sun, 30 Sep 2012, Adrian Sandu wrote:
> > We are working with computers. Weird stuff is not supposed to happen. But
> > it does. Occasionally, this needs to be remembered, as it does
> > occasionally cause real-world problems and is often the likely explanation
> > for what is otherwise inexp
Adrian Sandu wrote:
> I wouldn't of expected this from WD ..
Like with Theodore's problem you don't really know for sure where the
problem was in your setup.
Any combination of USB controller hardware in PC, cable, and
electronics in drive enclosure can have caused your problem.
External disk dr
> We are working with computers. Weird stuff is not supposed to happen. But
> it does. Occasionally, this needs to be remembered, as it does
> occasionally cause real-world problems and is often the likely explanation
> for what is otherwise inexplicable. Thus, sooner or later some old geezer
> com
On Sat, 29 Sep 2012, Adrian Sandu wrote:
> > The only solution I see is to buy something else, like an Asus
> > EB1501P-B057E .. I need something small and fast enough .. :| Maybe
> > any other recommendations ? ( other root chipset / atom cpu .. small
> > powered .. etc. )
>
> DON'T KILL ME !
> The only solution I see is to buy something else, like an Asus
> EB1501P-B057E .. I need something small and fast enough .. :| Maybe
> any other recommendations ? ( other root chipset / atom cpu .. small
> powered .. etc. )
DON'T KILL ME ! .. I got the best cables I could get my hands on (
doubl
The only solution I see is to buy something else, like an Asus
EB1501P-B057E .. I need something small and fast enough .. :| Maybe
any other recommendations ? ( other root chipset / atom cpu .. small
powered .. etc. )
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the b
>
> Adrian,
>
> I think that the suggestion about checking the power supply, the cabling,
> the grounding screws, and anything of like nature that has been omitted
> from this list is a very good idea. If successful it would eliminate
> the problem for you, as well as resolving the mystery. Unresol
Adrian,
I think that the suggestion about checking the power supply, the cabling,
the grounding screws, and anything of like nature that has been omitted
from this list is a very good idea. If successful it would eliminate
the problem for you, as well as resolving the mystery. Unresolved
myst
> They're the same chipset. There's minor differences in the PCI
> capabilities, but not much else. It could be something electrically
> wrong with the AsRock system, I suppose. That's possible if you see
> the errors popping up erratically.
>
> Any chance you can exchange the AsRock system?
No
On Thu, Sep 27, 2012 at 10:02:22PM +0300, Adrian Sandu wrote:
> > Since you are using the same live CD on both computers, this has to be
> > caused by a difference in the hardware. What do "lspci -vvv" and
> > "lspci -vvv -n" show on the two computers?
>
> http://d3xt3r01.tk/~dexter/usbmon/asrock
> Since you are using the same live CD on both computers, this has to be
> caused by a difference in the hardware. What do "lspci -vvv" and
> "lspci -vvv -n" show on the two computers?
http://d3xt3r01.tk/~dexter/usbmon/asrock_lspci
http://d3xt3r01.tk/~dexter/usbmon/vaio_lspci
--
To unsubscribe fr
On Thu, 27 Sep 2012, Adrian Sandu wrote:
> >> Adrian Sandu wrote:
> >>> I tried with a 3.3.8 , same thing happened. I don't understand why my
> >>> gentoo (asrock) fails and fedora(laptop) didn't ! :|
>
> Tried to use the live cd on my laptop, can't reproduce it in any way
> on my computer ..
> U
>> Adrian Sandu wrote:
>>> I tried with a 3.3.8 , same thing happened. I don't understand why my
>>> gentoo (asrock) fails and fedora(laptop) didn't ! :|
Tried to use the live cd on my laptop, can't reproduce it in any way
on my computer ..
Using the same live cd I can reproduce the problem on the
> Adrian Sandu wrote:
>> I tried with a 3.3.8 , same thing happened. I don't understand why my
>> gentoo (asrock) fails and fedora(laptop) didn't ! :|
>
> Try what Alan suggested, start the Gentoo userland with the Fedora
> kernel.
I tried booting a Fedora-17-x86_64-Live-Desktop.iso .. same thing
Adrian Sandu wrote:
> I tried with a 3.3.8 , same thing happened. I don't understand why my
> gentoo (asrock) fails and fedora(laptop) didn't ! :|
Try what Alan suggested, start the Gentoo userland with the Fedora
kernel.
Do you have some crazy USE flags for your toolchain?
If the Fedora kernel
On Thu, 27 Sep 2012, Adrian Sandu wrote:
> I tried with a 3.3.8 , same thing happened. I don't understand why my
> gentoo (asrock) fails and fedora(laptop) didn't ! :|
Come to think of it, you could try running the same kernel on both
computers to see what happens. For example, boot both of the
On Thu, 27 Sep 2012, Adrian Sandu wrote:
> >> I tried with a 3.3.8 , same thing happened. I don't understand why my
> >> gentoo (asrock) fails and fedora(laptop) didn't ! :|
> >> Why ? What causes it to shutdown ? It can copy to/from drives ( in the
> >> hub or directly in the root hub ) .. but wh
>> I tried with a 3.3.8 , same thing happened. I don't understand why my
>> gentoo (asrock) fails and fedora(laptop) didn't ! :|
>> Why ? What causes it to shutdown ? It can copy to/from drives ( in the
>> hub or directly in the root hub ) .. but what makes it fail sometimes
>> :|
>
> If we knew th
On Thu, 27 Sep 2012, Adrian Sandu wrote:
> >> Anything else I can help with ? :| I'm stuck .. dunno what to test
> >> more or what else helpfull info I could give ya' guys ..
> >
> > You could run a test with a 3.3 kernel, as Sarah asked earlier. Other
> > than that, I can't think of anything. M
>> Anything else I can help with ? :| I'm stuck .. dunno what to test
>> more or what else helpfull info I could give ya' guys ..
>
> You could run a test with a 3.3 kernel, as Sarah asked earlier. Other
> than that, I can't think of anything. Maybe Sarah will come up with a
> patch for you to tr
Please trim unnecessary junk from your emails. There's no reason to
send all the stuff at the end of those messages to everybody on the
mailing list.
On Thu, 27 Sep 2012, Adrian Sandu wrote:
> Anything else I can help with ? :| I'm stuck .. dunno what to test
> more or what else helpfull info
On Wed, Sep 26, 2012 at 8:16 PM, Adrian Sandu wrote:
> 2012-09-26T20:13:09.700606+03:00 d3xt3r01 kernel: [ 2466.455403] usb
> 3-1.1: reset SuperSpeed USB device number 14 using xhci_hcd
> 2012-09-26T20:13:09.713629+03:00 d3xt3r01 kernel: [ 2466.468373]
> xhci_hcd :04:00.0: xHCI xhci_drop_endpo
2012-09-26T20:13:09.700606+03:00 d3xt3r01 kernel: [ 2466.455403] usb
3-1.1: reset SuperSpeed USB device number 14 using xhci_hcd
2012-09-26T20:13:09.713629+03:00 d3xt3r01 kernel: [ 2466.468373]
xhci_hcd :04:00.0: xHCI xhci_drop_endpoint called with disabled ep
88011aea1300
2012-09-26T20:13:
On Wed, Sep 26, 2012 at 5:50 PM, Alan Stern wrote:
> On Tue, 25 Sep 2012, Sarah Sharp wrote:
>
>> Alan, I'm wondering if the xHCI ring expansion is causing issues with
>> USB hard drives under xHCI. Testing with a Buffalo USB 3.0 hard drive
>> with an NEC uPD720200 xHCI host, I see that the usb-s
On Tue, 25 Sep 2012, Sarah Sharp wrote:
> Alan, I'm wondering if the xHCI ring expansion is causing issues with
> USB hard drives under xHCI. Testing with a Buffalo USB 3.0 hard drive
> with an NEC uPD720200 xHCI host, I see that the usb-storage and SCSI
> initialization produces I/O errors on ra
25 matches
Mail list logo
