Bug 1003181 - Unable to type reliably on remote systems via SSH after kernel update
Summary: Unable to type reliably on remote systems via SSH after kernel update
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-31 14:40 UTC by Steven Stern
Modified: 2013-09-18 21:08 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-18 21:08:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Steven Stern 2013-08-31 14:40:20 UTC
Description of problem:
Using SSH to access files on remote system (but local to my LAN).  Using arrow key to scroll through files or up/down in bash_history or left or right in current command.  

Works fine with 3.10.7-200.  

When using kernel 3.10.9-200, cursor stops moving and characters are either not being transmitted or are not echoing back.  Have to wait for 3-5 seconds to be able to continue typing.


Version-Release number of selected component (if applicable):
3.10.9-200

How reproducible:
SSH to another system. vi into a file.  Press down-arrow and hold it.  Response will stop after 10-15 lines.

Fedora 19 64 bit fully up-to-date as of 2013-08-31

Comment 1 Harald Reindl 2013-08-31 14:57:18 UTC
i can't confirm this

worked the last days hard on a testserver running F19 to debug upstream-software using SSH and fuse.sshfs and 3.10.9-200 was running from the build-day until yesterday 3.10.10-200.fc19.x86_64 was built on koji

Comment 2 Josh Boyer 2013-09-18 20:46:40 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 3 Steven Stern 2013-09-18 21:08:54 UTC
Seems to be OK now on 3.10.11-200.fc19.x86_64


Note You need to log in before you can comment on or make changes to this bug.