gdm crashed (fatal x error) on Jaunty Beta

[Ruben Verweij]

Binary package hint: gdm

The X Server crashed unexpectedly while using Jaunty Beta. I don't know how to reproduce this bug, though I found this in the system log: gdm[4153]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0.
Once the X Server was restarted, I could login and continue without problems. If there's more information needed I'd be happy to provide it.

[Jon Charge (seropith)]

Hello,

Thank you for your information. If you could, what video card, and driver are you using.

Thank you for your interest.

Jon

[Chris Coulson (chrisccoulson)]

This is not a GDM bug. This is most likely a xorg or video driver problem. Please attach your /var/log/Xorg.0.log and /var/log/Xorg.0.log.old after you experience this problem.

[Bryce Harrington (bryce)]

Please collect a full backtrace - see http://wiki.ubuntu.com/X/Backtracing for directions.

Also, you need to attach your Xorg.0.log and the output of `lspci -vvnn` whenever reporting Xorg bugs. An easy way to do this is to run `apport-collect 350548` from the affected machine.

[Jon Charge (seropith)]

Assigned to JonCharge -> Nobody

Deassigning. I must have assigned it inadvertently.

[Ruben Verweij (ruben-verweij)]

Sorry, I forgot to mention the video card etc. I have a nVidia GeForce 6200 with two displays attached. My driver version is 180.37.
lspci -vvnn:
01:00.0 VGA compatible controller [0300]: nVidia Corporation NV44A [GeForce 6200] [10de:0221] (rev a1)
 Subsystem: ASUSTeK Computer Inc. Device [1043:820c]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 248 (1250ns min, 250ns max)
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at de000000 (32-bit, non-prefetchable) [size=16M]
 Region 1: Memory at e0000000 (32-bit, prefetchable) [size=256M]
 Region 2: Memory at dd000000 (32-bit, non-prefetchable) [size=16M]
 [virtual] Expansion ROM at dffe0000 [disabled] [size=128K]
 Capabilities: <access denied>
 Kernel driver in use: nvidia
 Kernel modules: nvidia, nvidiafb
I'm not sure how to collect a backtrace - I don't really know how to reproduce the problem; it just happened suddenly.
I will attach the to log files.

[Ruben Verweij (ruben-verweij)]

01:00.0 VGA compatible controller [0300]: nVidia Corporation NV44A [GeForce 6200] [10de:0221] (rev a1)
 Subsystem: ASUSTeK Computer Inc. Device [1043:820c]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 248 (1250ns min, 250ns max)
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at de000000 (32-bit, non-prefetchable) [size=16M]
 Region 1: Memory at e0000000 (32-bit, prefetchable) [size=256M]
 Region 2: Memory at dd000000 (32-bit, non-prefetchable) [size=16M]
 [virtual] Expansion ROM at dffe0000 [disabled] [size=128K]
 Capabilities: [60] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [44] AGP version 3.0
  Status: RQ=256 Iso- ArqSz=0 Cal=3 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
  Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
 Kernel driver in use: nvidia
 Kernel modules: nvidia, nvidiafb
Sorry, I forgot to sudo. :)

[Chris Coulson (chrisccoulson)]

There doesn't seem to be any evidence of a crash in your logs. DId you manage to obtain a backtrace, following the instructions given earlier by Bryce?

Thanks

[Ruben Verweij (ruben-verweij)]

No, because, as I mentioned earlier, I wasn't able to reproduce the bug.

[Thiago Figueiro (thiagocsf)]

I'm not sure if I have the same issue. My backtrace for a similar crash is:

Backtrace:
0: /usr/X11R6/bin/X(xorg_backtrace+0x26) [0x4f1b66]
1: /usr/X11R6/bin/X(xf86SigHandler+0x41) [0x485a61]
2: /lib/libc.so.6 [0x7fd7a470c040]
3: /usr/lib/xorg/modules/extensions//libglx.so [0x7fd7a34c9ecf]

I have installed nVidia's latest driver (180.51) and the same crash happened less than an hour after.

It seems to happen more often when the screensaver is running. That being said, it also happens when I'm working (nothing too exciting running: firefox, some terminals, maybe openoffice).

I've installed the dbg packages and will try to post a more complete backtrace. In the mean time I've attached the logs from the last crash.

[Thiago Figueiro (thiagocsf)]

Since my last comment I have disabled XScreensaver.

While I don't think XScreensaver is at fault it has many OpenGL intensive applications. I suspect one of them is triggering the bug. Unfortunately I can't say which one yet.

[Thiago Figueiro (thiagocsf)]

No crashes since I changed XScreensaver to "Blank Screen".

I have now removed the Ubuntu nvidia driver (v 180) and manually installed nVidia's latest (v 185).

I have also re-enabled the OpenGL screensavers. Will post the results after a few days.

[Thiago Figueiro (thiagocsf)]

No crashes since I installed the updated nVidia driver:

http://www.nvidia.com/object/linux_display_amd64_185.18.14.html

My machine was crashing several times a day. I have re-enabled the OpenGL screensavers and so far so good.

[Bryce Harrington (bryce)]

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[Thiago Figueiro (thiagocsf)]

I have previously downloaded and installed nVidia's driver version 185
and I haven't had xorg crash after that.

When I get to work on Monday I'll give your packaged driver a go.

Cheers,
Thiago

2009/6/26 Bryce Harrington <email address hidden>:
>
> I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
> would you mind testing it either on Jaunty or Karmic and see if it
> resolves this bug?
>
> Get nvidia-graphics-drivers-180 - 185.18.14 here:
>
>  https://edge.launchpad.net/~xorg-edgers/+archive/ppa
>
>
> ** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
>       Status: Confirmed => New
>
> ** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
>       Status: New => Incomplete
>
> --
> gdm crashed (fatal x error) on Jaunty Beta
> https://bugs.launchpad.net/bugs/350548
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “nvidia-graphics-drivers-180” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: gdm
>
> The X Server crashed unexpectedly while using Jaunty Beta. I don't know how to reproduce this bug, though I found this in the system log: gdm[4153]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0.
> Once the X Server was restarted, I could login and continue without problems. If there's more information needed I'd be happy to provide it.
>

[Bryce Harrington (bryce)]

Thanks for letting us know the issue is resolved.

[hkais (r-2)]

I have the same issue and it isn't solved with the new version. Marked it duplicate