[pkg-nvidia-devel] Bug#546455: Bug#546455: xserver always crashes shortly after boot

[Lennart Sorensen]

On Mon, Oct 19, 2009 at 04:29:18AM +0200, Sven Reckziegel wrote:
> I don't know whether it's important or not. After x server crash I
> found these informations in .xsession-errors:
> 
> 
> Xsession: X session started for zorronte at Sun Oct 18 23:55:56 CEST 2009
> XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
> 
>       after 250 requests (223 known processed) with 0 events remaining.
> 
> XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
> 
>       after 440 requests (440 known processed) with 0 events remaining.
> 
> XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
> 
>       after 365 requests (365 known processed) with 0 events remaining.
> 
> XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
> 
>       after 1398 requests (1397 known processed) with 4 events remaining.
> 
> xterm:  fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar)
> or KillClient on X server ":0.0"
> 
> xterm:  fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar)
> or KillClient on X server ":0.0"
> 
> xterm:  fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar)
> or KillClient on X server ":0.0"
> 
> firefox-bin: Fatal IO error 11 (Die Ressource ist zur Zeit nicht
> verfügbar) on X server :0.0.
> xterm:  fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar)
> or KillClient on X server ":0.0"
> 
> xterm:  fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar)
> or KillClient on X server ":0.0"
> 
> xterm:  fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar)
> or KillClient on X server ":0.0"
> 
> xterm:  fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar)
> or KillClient on X server ":0.0"
> 
> Xsession: X session started for zorronte at Sun Oct 18 23:56:33 CEST 2009
> 
> 
> 
> The crash occurs always with an character input and Martin - I will
> test your fix,

Does this still happen with the current driver version in unstable?

-- 
Len Sorensen