Re: 2.6.33: Xorg+khubd lockup (D-state) BUG / ioctl EVIOCGNAME failed:Inappropriate ioctl for device / PreInit returned NULL

[Tiago Vignatti]

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/