Xorg crashed with SIGABRT in WakeupHandler()

[Adam Bruce]

Maarten requested I post a new crash report for bug 1127023

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-core 2:1.13.3-0ubuntu2b1
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.9.2-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Mar 20 09:01:23 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.2.8, 3.8.0-12-generic, x86_64: installed
 virtualbox, 4.2.8, 3.8.0-13-generic, x86_64: installed
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0446]
 NVIDIA Corporation GF108 [GeForce GT 540M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0446]
InstallationDate: Installed on 2013-03-13 (7 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130210)
MachineType: Dell Inc. Dell System XPS 15Z
MarkForUpload: True
ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=33e9c3b1-77e1-4f0a-97e2-269a6fa599b4 ro acpi_backlight=vendor dell_laptop.backlight=0 quiet splash
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 ?? () from /usr/lib/xorg/modules/drivers/nouveau_drv.so
 WakeupHandler ()
 WaitForSomething ()
 ?? ()
 ?? ()
Title: Xorg crashed with SIGABRT in WakeupHandler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

XorgLogOld:

dmi.bios.date: 09/07/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 060G42
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPS15Z:pvr:rvnDellInc.:rn060G42:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS 15Z
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.9~daily13.03.08-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.42-0ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu2b1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1b1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.4-0ubuntu1b1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3b1

[Adam Bruce (brucey-99-deactivatedaccount)]

This is the Xorg log from that boot

I noticed that sometimes the ubuntu logo would pop up for a moment, then go to a black screen. And sometimes it would go into low graphics mode. This is a crash report of it going into the low graphics made

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1050494, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Maarten Lankhorst (mlankhorst)]

oooh ohhh oohh can you do 'sudo udevadm trigger --action=add --subsystem-match=drm' ? I bet it breaks! :D

At least this is what I get, anyway..

==2422== Invalid write of size 8
==2422== at 0x161118: AttachOutputGPU (list.h:132)
==2422== by 0x1D9E85: xf86AutoConfigOutputDevice (xf86Crtc.c:3293)
==2422== by 0x1C1FCF: xf86platformAddDevice (xf86platformBus.c:473)
==2422== by 0x1C6929: NewGPUDeviceRequest (lnx_platform.c:173)
==2422== by 0x1C3389: config_udev_odev_setup_attribs (udev.c:441)
==2422== by 0x1C379C: device_added (udev.c:103)
==2422== by 0x1C3EE7: wakeup_handler (udev.c:310)
==2422== by 0x164DCA: WakeupHandler (dixutils.c:423)
==2422== by 0x2B5713: WaitForSomething (WaitFor.c:224)
==2422== by 0x160860: Dispatch (dispatch.c:357)
==2422== by 0x14F5C9: main (main.c:298)
==2422== Address 0x93183c8 is 1,256 bytes inside a block of size 1,352 free'd
==2422== at 0x4C2BA6C: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==2422== by 0x1C21BD: xf86platformRemoveDevice (xf86platformBus.c:512)
==2422== by 0x1C6A07: DeleteGPUDeviceRequest (lnx_platform.c:206)
==2422== by 0x1C3389: config_udev_odev_setup_attribs (udev.c:441)
==2422== by 0x1C3DE4: device_removed (udev.c:274)
==2422== by 0x1C3EDF: wakeup_handler (udev.c:309)
==2422== by 0x164DCA: WakeupHandler (dixutils.c:423)
==2422== by 0x2B5713: WaitForSomething (WaitFor.c:224)
==2422== by 0x160860: Dispatch (dispatch.c:357)
==2422== by 0x14F5C9: main (main.c:298)
==2422==
xf86: found device 2
==2422== Invalid read of size 4
==2422== at 0x8BD23C5: drm_wakeup_handler (drmmode_display.c:1567)
==2422== by 0x164DCA: WakeupHandler (dixutils.c:423)
==2422== by 0x2B5713: WaitForSomething (WaitFor.c:224)
==2422== by 0x160860: Dispatch (dispatch.c:357)
==2422== by 0x14F5C9: main (main.c:298)
==2422== Address 0x92d8370 is 592 bytes inside a block of size 3,896 free'd
==2422== at 0x4C2BA6C: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==2422== by 0x8BCFA96: RADEONFreeRec (radeon_kms.c:180)
==2422== by 0x1A9B53: xf86DeleteScreen (xf86Helper.c:237)
==2422== by 0x1C21CA: xf86platformRemoveDevice (xf86platformBus.c:514)
==2422== by 0x1C6A07: DeleteGPUDeviceRequest (lnx_platform.c:206)
==2422== by 0x1C3389: config_udev_odev_setup_attribs (udev.c:441)
==2422== by 0x1C3DE4: device_removed (udev.c:274)
==2422== by 0x1C3EDF: wakeup_handler (udev.c:309)
==2422== by 0x164DCA: WakeupHandler (dixutils.c:423)
==2422== by 0x2B5713: WaitForSomething (WaitFor.c:224)
==2422== by 0x160860: Dispatch (dispatch.c:357)
==2422== by 0x14F5C9: main (main.c:298)
==2422==
==2422== Invalid read of size 4
==2422== at 0x8BD23D0: drm_wakeup_handler (drmmode_display.c:1567)
==2422== by 0x164DCA: WakeupHandler (dixutils.c:423)
==2422== by 0x2B5713: WaitForSomething (WaitFor.c:224)
==2422== by 0x160860: Dispatch (dispatch.c:357)
==2422== by 0x14F5C9: main (main.c:298)
==2422== Address 0x92d8370 is 592 bytes inside a block of size 3,896 free'd
==2422== at 0x4C2BA6C: free (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==2422== by 0x8BCFA96: RADEONFreeRec (radeon_...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Maarten Lankhorst (mlankhorst)]

Does the bug go away if you edit /etc/init/udevtrigger.conf ?

Change

exec udevadm trigger --action=add

to

exec udevadm trigger --action=add --subsystem-nomatch=drm

[Adam Bruce (brucey-99-deactivatedaccount)]

I ran sudo udevadm trigger --action=add --subsystem-match=drm and it went black and logged me out. On returning I had a crash report, let me know if you want me to report it (It had the same title as this report)

I edited udevtrigger.conf and it did not fix the bug.

For the first time I have noticed a lightdm crash.. I tried to report it but it says

"This problem report is damaged and cannot be processed.

ValueError('Report does not contain "ProblemType" field',)"

I willl attach it here

[Adam Bruce (brucey-99-deactivatedaccount)]

Maybe not, it's 0bytes in size

[Adam Bruce (brucey-99-deactivatedaccount)]

here is also the crash report from when the ubuntu logo pops up for a split second and then it just goes black: bug 1157819

(with your that edit to udevtrigger applied)

[Adam Bruce (brucey-99-deactivatedaccount)]

Here is the lightdm crash. I notice is says I have the 'sleep 5' applied to lightdm.conf, so I guess this means it crashed when I was booting in successfully as thats the work around I use to login.

Is it to do with the edit I made to udevtrigger?

I can't report it as I have an obsolete package (but it says no available updates)

[Maarten Lankhorst (mlankhorst)]

It should probably check if the device is already added, instead of blindly re-adding. :-)

I understand the drmmode part now.

It goes wrong in 3 places at the moment:

* bugs in xorg-server
  - Fix 1: drm_device_keep_trying.patch (pushed to debian git, proposed on mailing list)
  - Fix 2: unbinding hybrid drivers doesn't work correctly at the moment, detaching is not done correctly if it has outputs and rendering (in my local tree, need to amend the correct patch)
  - Fix 3: Ignore add events for devices we already have added, instead of removing/re-adding device.

* bugs in drivers:
  - all except modesetting: drmmode_init installs some handlers, and nothing cleans them up
  - all: the drm fd is never closed, so reopening a device will always fail.

Plus perhaps some more bugs in some places, but those were the obvious ones I found so far.

I fixed xserver-xorg-video-ati in upstream git, other drivers should be fixable in a similar way.

[Launchpad Janitor (janitor)]

This bug was fixed in the package xserver-xorg-video-ati - 1:7.1.0-0ubuntu2

---------------
xserver-xorg-video-ati (1:7.1.0-0ubuntu2) raring; urgency=low

  * Fix not removing socket and block handler on close (LP: #1157614)
    - fixup-close.patch
  * Handle drmModeGetConnector failure better.
    - drmmode-fail.patch
 -- Maarten Lankhorst <email address hidden> Wed, 20 Mar 2013 14:00:46 +0000

[Launchpad Janitor (janitor)]

This bug was fixed in the package xorg-server - 2:1.13.3-0ubuntu3

---------------
xorg-server (2:1.13.3-0ubuntu3) raring; urgency=low

  * Refresh autoconfig-fixup-tell-changed-so-randr-clients-can-t.patch
    - Unbind offload sink and render slave simultaneously.
      This prevents a use-after-free bug.
  * Add config-add-no-removal.patch (LP: #1157614)
    - Do not call device_remove when a device is hotplugged.
  * Refresh drm_device_keep_trying.patch
    - There is no need for drm master here. This might
      reopen LP #982889, but I do not think spinning here
     :is the correct answer.
 -- Maarten Lankhorst <email address hidden> Thu, 21 Mar 2013 15:40:42 +0100

[Adam Bruce (brucey-99-deactivatedaccount)]

Still crashes :/

Do you want me to report it as a bug, or can you get all the info you need from the .crash file?

[Adam Bruce (brucey-99-deactivatedaccount)]

Oh it is because I'm using nouveau?

[Maarten Lankhorst (mlankhorst)]

Can you boot with plymouth debugging information? Add 'plymouth:debug' to command line, then attach /var/log/plymouth-debug.log here.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Maarten Lankhorst (mlankhorst)]

Also a new xorg.0.log from 2:1.13.3-0ubuntu3 would be nice if intiialization still goes wrong. The last log I have is from 2b1.

[Launchpad Janitor (janitor)]

This bug was fixed in the package xserver-xorg-video-nouveau - 1:1.0.6-0ubuntu4

---------------
xserver-xorg-video-nouveau (1:1.0.6-0ubuntu4) raring; urgency=low

  * Clean up (forced) device close (LP: #1157614)
    - 102-fixup-close.diff
 -- Maarten Lankhorst <email address hidden> Mon, 25 Mar 2013 14:01:46 +0100

[Adam Bruce (brucey-99-deactivatedaccount)]

With the latest updates I have booted by computer 10 times and seen no crashes.

A few times, however, I see a black screen with just my mouse

Here is xorg and plymouth debug from successful boot

[Adam Bruce (brucey-99-deactivatedaccount)]

Plymouth debug

[Adam Bruce (brucey-99-deactivatedaccount)]

Most of the time these files came out as 0Bytes. but many retries later and I have plymouth-debug and Xorg from a boot that goes to black screen with mouse.

I hope it's helpful

[Adam Bruce (brucey-99-deactivatedaccount)]

plymouth-debug

[Maarten Lankhorst (mlankhorst)]

Where's the fun in succesful boots?

Anyhow just append 'and started plymouth-splash' to the start on line in /etc/init/lightdm.conf, after the 'and started dbus' line.

This should fix the race between plymouth show-splash and lightdm starting.

[Adam Bruce (brucey-99-deactivatedaccount)]

Like this?

start on ((filesystem
           and runlevel [!06]
           and started dbus
    and started plymouth-splash
           and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1
                or stopped udev-fallback-graphics))
          or runlevel PREVLEVEL=S)

I'm still getting the black screen sometimes. I can show you Xorg, but the bug doesn't hit when I put in the plymouth:debug line

[Adam Bruce (brucey-99-deactivatedaccount)]

If so, this is the Xorg

[Maarten Lankhorst (mlankhorst)]

Well, it looks like Xorg loading is sane there, so it would appear you are hitting a different bug. Perhaps backlight related? Can you file a separate bug against xserver-xorg-video-intel for this?

[Abu Aaisha (ctgcma-b)]

I went through all the comments and could not find any solution. Considering that many people have started using ubuntu, requesting you all to be more precise while posting solutions. everyone is not master of ubuntu/linux.