Gentlemen,
I believe I've found the root cause of the issue.
USB is absolutely not to blame in this case. Problems were caused by the
udisksd daemon that sent ATA IDENTIFY DEVICE pass through command with
the SECTOR_COUNT field set to 0 (cdb[6] = 0). I first noticed it when I
compared the str
Christian,
Douglas, Hannes: I believe we are definitely on to something. I do
_not_ run smartd but this may be caused by something in my Gnome3 GUI
environment. I have noticed that when I am not logged in to Gnome and
work just in the text console, plugging in the USB drive and
accessing it w
Peter Palúch wrote:
Gentlemen,
First of all, thank you very much for looking into this issue.
Alan, for the sake of keeping the thread tidy in archives, I am not
going to change the $SUBJECT of this e-mail but I wholeheartedly agree
that this is not an xHCI issue. Mea culpa; I did not know th
Gentlemen,
First of all, thank you very much for looking into this issue.
Alan, for the sake of keeping the thread tidy in archives, I am not
going to change the $SUBJECT of this e-mail but I wholeheartedly agree
that this is not an xHCI issue. Mea culpa; I did not know that at the
time I fir
On 14-01-17 02:35 AM, Hannes Reinecke wrote:
On 01/16/2014 09:48 PM, Alan Stern wrote:
It's now clear that this is _not_ an XHCI issue, contrary to what
$SUBJECT says.
On Thu, 16 Jan 2014, Peter Palúch wrote:
Alan,
I am attaching the usbmon trace after the drive has been plugged into
the USB
On 01/16/2014 09:48 PM, Alan Stern wrote:
> It's now clear that this is _not_ an XHCI issue, contrary to what
> $SUBJECT says.
>
> On Thu, 16 Jan 2014, Peter Palúch wrote:
>
>> Alan,
>>
>> I am attaching the usbmon trace after the drive has been plugged into
>> the USB-2 port. Record of the dri
It's now clear that this is _not_ an XHCI issue, contrary to what
$SUBJECT says.
On Thu, 16 Jan 2014, Peter Palúch wrote:
> Alan,
>
> I am attaching the usbmon trace after the drive has been plugged into
> the USB-2 port. Record of the drive in stall should occur around the
> file offset 8780
Alan,
I am attaching the usbmon trace after the drive has been plugged into
the USB-2 port. Record of the drive in stall should occur around the
file offset 87808 (decimal). The log was done on the 3.12.7 kernel
without CONFIG_PM. Should I do a usbmon trace on my regular kernel with
CONFIG_PM
On Wed, 15 Jan 2014, Peter Palúch wrote:
> The interesting thing is that the same happens even if the drive is
> plugged into an USB 2.0 port in the same notebook:
That is an important point.
> root@bach:~# dmesg -c
> usb 3-1.1: new high-speed USB device number 5 using ehci-pci
> usb 3-1.1: New
Hi Alan,
Thank you for your response.
I have just tried the drive with 3.12.7 without CONFIG_PM (the config.gz
is attached just in case I misconfigured the kernel in some way I could
correct) - unfortunately, no change whatsoever:
!!!
!!! The drive is plugged in:
!!!
root@bach:~# dmesg -c
u
On Tue, 14 Jan 2014, Peter Palúch wrote:
> Dear friends,
>
> So far, there has been no response to this issue report. I understand
> this is not a help desk with guaranteed replies but the fact that there
> was no response whatsoever is surprising to me.
This means that nobody who has looked a
Dear friends,
So far, there has been no response to this issue report. I understand
this is not a help desk with guaranteed replies but the fact that there
was no response whatsoever is surprising to me.
I would like to at least kindly ask that someone looks at the traces and
tells me if thi
Greetings,
Regarding the issue with WD MyBook 1230 stalling and being reset when
connected to an HP EliteBook 8560p, I have tested the 3.13-rc7 kernel
from kernel.org to no avail - the drive still stalls and is reset after
a couple of seconds. I am attaching a dmesg output (relevant lines
reg
Peter Palúch writes:
>
> Hi Andrej,
>
> > Same problem here. HP elitebook 8560w. Running on Arch linux, kernel:
> > 3.12.5. Attaching WD Elements 1TB.no
>
> Thanks for confirming that the issue also occurs with HP EliteBook
> 8560w. Do you believe you could also create the usbmon capture trac
Hi Andrej,
Same problem here. HP elitebook 8560w. Running on Arch linux, kernel:
3.12.5. Attaching WD Elements 1TB.no
Thanks for confirming that the issue also occurs with HP EliteBook
8560w. Do you believe you could also create the usbmon capture trace
plus the outputs of dmesg, lspci and l
Same problem here. HP elitebook 8560w. Running on Arch linux, kernel:
3.12.5. Attaching WD Elements 1TB.no
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.
16 matches
Mail list logo
