public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grzegorz Nosek <root@localdomain.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	support@supermicro.com
Subject: Re: EHCI software retries break Supermicro IPKVM
Date: Mon, 30 Apr 2012 23:29:10 +0200	[thread overview]
Message-ID: <4F9F0426.6040603@localdomain.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1204301707060.1558-100000@iolanthe.rowland.org>

W dniu 30.04.2012 23:12, Alan Stern pisze:
> It isn't a software issue.  You've got a hardware problem; either the
> IPKVM itself, or the connecting cable, or your computer's EHCI
> controller is bad.  The only reason the device worked without the retry
> logic is because it failed so completely that the kernel was forced to
> run it at full speed (12 Mb/s) instead of high speed (480 Mb/s).  With
> the retry logic present, the device was barely workable at high speed
> (but it probably didn't work well enough to be very useful).

Oh. Thanks for the info. Is there a way to force the device into 12Mb/s 
mode? I don't care about performance as the bottleneck is my Internet 
link on the client, anyway. The retry logic rendered the console 
unusable (not just slow, completely no keyboard or redirected media).

> Have you tried plugging the IPKVM into a different computer to see if
> it behaves any better?

Nope. The IPKVM is a proprietary addon card without any cables (plugs 
into a dedicated slot on the motherboard). Another identical machine is 
misbehaving the exact same way (retry messages in dmesg), so either I'm 
just unlucky, or it's a wider issue. Still, a few others are working 
fine (no retry messages; though I did not check the KVM recently). All 
the machines are in a rather remote DC, so I'm unlikely to muck with the 
hardware any time soon.

Are there any diagnostics possible to determine what is broken (i.e. the 
KVM card or the controller)? IIRC plugging a physical USB-based KVM 
worked fine, although that might have been an older kernel, without the 
retry logic.

Best regards,
  Grzegorz Nosek

  reply	other threads:[~2012-04-30 21:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 15:29 EHCI software retries break Supermicro IPKVM Grzegorz Nosek
2012-04-19 17:40 ` Alan Stern
2012-04-29 13:42   ` Grzegorz Nosek
2012-04-30 21:12     ` Alan Stern
2012-04-30 21:29       ` Grzegorz Nosek [this message]
2012-05-01 14:24         ` Alan Stern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F9F0426.6040603@localdomain.pl \
    --to=root@localdomain.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=support@supermicro.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox