From: Michael Tokarev <mjt@tls.msk.ru>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
Alan Piszcz <ap@solarrain.com>
Subject: Re: 2.6.33: Xorg+khubd lockup (D-state) BUG / ioctl EVIOCGNAME failed: Inappropriate ioctl for device / PreInit returned NULL
Date: Fri, 26 Mar 2010 00:14:45 +0300 [thread overview]
Message-ID: <4BABD245.8050300@msgid.tls.msk.ru> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1003251646170.1808-100000@iolanthe.rowland.org>
Alan Stern wrote:
> On Thu, 25 Mar 2010, Justin Piszcz wrote:
Actually this very message - ioctl EVIOCGNAME...NULL - is quite
common since some time - since either some of X or kernel.
But usually it does not come together with a freeze, and
it is not necessary about USB to start with -- for example,
my synaptics touchpad stopped working, and that's exactly
what's shown in the Xorg.log file -- EVIOCGNAME..NULL, when
it tries to init the touchpad... JFYI.
/mjt
next prev parent reply other threads:[~2010-03-25 21:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 12:29 2.6.33: Xorg+khubd lockup (D-state) BUG / ioctl EVIOCGNAME failed: Inappropriate ioctl for device / PreInit returned NULL Justin Piszcz
2010-03-25 12:35 ` Justin Piszcz
2010-03-25 13:40 ` Justin Piszcz
2010-03-25 14:17 ` Alan Stern
2010-03-25 14:47 ` Justin Piszcz
2010-03-25 15:53 ` Alan Stern
2010-03-25 16:45 ` Justin Piszcz
2010-03-25 21:02 ` Alan Stern
2010-03-25 21:14 ` Michael Tokarev [this message]
2010-03-29 11:45 ` Justin Piszcz
2010-03-29 15:33 ` Alan Stern
2010-03-29 16:26 ` Justin Piszcz
2010-03-29 16:38 ` Justin Piszcz
2010-03-29 16:58 ` Alan Stern
2010-03-29 18:44 ` Justin Piszcz
2010-03-30 12:58 ` Justin Piszcz
2010-03-30 17:40 ` Alan Stern
2010-03-30 18:02 ` Justin Piszcz
2010-03-30 23:19 ` Tiago Vignatti
2010-03-31 11:08 ` Justin Piszcz
2010-03-31 18:25 ` Justin Piszcz
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=4BABD245.8050300@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=ap@solarrain.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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