LKML Archive on
help / color / mirror / Atom feed
From: Alan Stern <>
To: Florin Iucha <>
Cc: Jiri Kosina <>,
	Linux Kernel Mailing List <>,
	Adrian Bunk <>,
	Trond Myklebust <>
Subject: Re: heavy nfs[4]] causes fs badness Was: 2.6.20-rc4: known unfixed regressions (v2)
Date: Wed, 24 Jan 2007 14:07:14 -0500 (EST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, 23 Jan 2007, Florin Iucha wrote:

> > It would be nice to learn exactly why the keyboard stopped working.  Try
> > using the usbmon facility (instructions in Documentation/usb/usbmon.txt)
> > to see what happens when you type on the dead keyboard.  Be sure to turn
> > on CONFIG_USB_DEBUG as well.  And also check /proc/interrupts; each time
> > you hit a key the USB controller should get an interrupt.
> Attached is the output from usbmon, unfortunately this kernel did not
> have CONFIG_USB_DEBUG set.  This is kernel 2.6.20-rc5.
> So, the bus sees some traffic when the keyboard is used, but gdm does
> not receive any keystrokes.

So it's possible that the USB drivers are working correctly but the 
keystrokes are getting lost somewhere in the X server.  Can you switch to 
a VT (or kill the X server entirely) and see if the keyboard works then?

Alan Stern

  reply	other threads:[~2007-01-24 19:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2007-01-14 22:57   ` [linux-usb-devel] " Florin Iucha
2007-01-14 23:58     ` heavy nfs[4]] causes fs badness Was: " Florin Iucha
2007-01-15  0:14       ` Jiri Kosina
2007-01-15  2:02         ` Florin Iucha
2007-01-15 15:58           ` Alan Stern
2007-01-24  3:04             ` Florin Iucha
2007-01-24 19:07               ` Alan Stern [this message]
2007-01-15  0:14       ` Trond Myklebust
2007-01-15  2:11       ` Horst H. von Brand
2007-01-15 15:46         ` Florin Iucha

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:

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

  git send-email \ \ \ \ \ \ \ \ \
    --subject='Re: heavy nfs[4]] causes fs badness Was: 2.6.20-rc4: known unfixed regressions (v2)' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).