From: Tiago Vignatti <vignatti@freedesktop.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
xorg@lists.freedesktop.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: Wed, 31 Mar 2010 02:19:17 +0300 [thread overview]
Message-ID: <4BB286F5.9060706@freedesktop.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1003250935030.21591@p34.internal.lan>
Justin Piszcz wrote:
>
>
> On Thu, 25 Mar 2010, Justin Piszcz wrote:
>
>>
>>
>> On Thu, 25 Mar 2010, Justin Piszcz wrote:
>>
>> The same problem has been reported by another person, he says his
>> entire system freezes, which, it appears to do unless you can SSH into
>> the box:
>> http://www.openoffice.org/issues/show_bug.cgi?id=76797
>>
>> Look at his lspci listing.
>> james@dv6105us:~$ lspci
>> 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
>> 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
>> 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
>>
>> Here is mine:
>> $ lspci
>> 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
>> 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
>> 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
>> 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
>>
>> Looks like the bug may be in the USB subsystem for this chipset.
>>
>> Justin.
>>
>>
>
> Hi,
>
> And there it goes again *LOCK*
> root 2190 0.5 1.5 37832 31424 tty7 Ds+ 09:00 0:12
> /usr/bin/X :0 vt7 -nolisten tcp -auth
> /var/lib/xdm/authdir/authfiles/A:0-N5V00o
running X server with -nosilk helps something?
Tiago
next prev parent reply other threads:[~2010-03-30 23:54 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
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 [this message]
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=4BB286F5.9060706@freedesktop.org \
--to=vignatti@freedesktop.org \
--cc=ap@solarrain.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=xorg@lists.freedesktop.org \
/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