Well, I can confirm this on Ubuntu 10.10. Unfortunately I did not notice
before now that this bug report is about savage. It seems most 3D usage
will make xorg crash, with the same stack trace as you have in your
kern.log:
Xorg: page allocation failure. order:8, mode:0xc0d0
Pid: 15953, comm: Xorg Not tainted 2.6.35-20-generic #29-Ubuntu
Call Trace:
[<c05c5fc7>] ? printk+0x2d/0x36
[<c01dfbba>] __alloc_pages_slowpath+0x47a/0x4b0
[<c01dfd5f>] __alloc_pages_nodemask+0x16f/0x1c0
[<c0106c52>] dma_generic_alloc_coherent+0x62/0xc0
[<e0a429ba>] drm_pci_alloc+0x12a/0x1b0 [drm]
[<c0106bf0>] ? dma_generic_alloc_coherent+0x0/0xc0
[<e0a39b7c>] drm_addmap_core+0x12c/0x7f0 [drm]
[<c0186415>] ? swsusp_read+0xb5/0x140
[<c0186415>] ? swsusp_read+0xb5/0x140
[<e0a3a289>] drm_addmap_ioctl+0x49/0x80 [drm]
[<e0a3ba8c>] drm_ioctl+0x2ac/0x430 [drm]
[<c0186415>] ? swsusp_read+0xb5/0x140
[<e0a3a240>] ? drm_addmap_ioctl+0x0/0x80 [drm]
[<c01f4566>] ? handle_mm_fault+0x146/0x400
[<c05cbf5d>] ? do_page_fault+0x1cd/0x440
[<c0186415>] ? swsusp_read+0xb5/0x140
[<c0226652>] vfs_ioctl+0x32/0xb0
[<e0a3b7e0>] ? drm_ioctl+0x0/0x430 [drm]
[<c0226ee9>] do_vfs_ioctl+0x79/0x2d0
[<c02183e0>] ? do_sync_write+0x0/0xe0
[<c02271a7>] sys_ioctl+0x67/0x80
[<c0186415>] ? swsusp_read+0xb5/0x140
[<c05c8c04>] syscall_call+0x7/0xb
[<c0186415>] ? swsusp_read+0xb5/0x140
[<c0186415>] ? swsusp_read+0xb5/0x140
[<c05c0000>] ? identify_cpu+0xc4/0x229
** Package changed: xscreensaver (Ubuntu) => mesa (Ubuntu)
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
** Summary changed:
- Everytime Xorg screensavers everything crashes.
+ [savage] Xorg page allocation failure when using drm
--
[savage] Xorg page allocation failure when using drm
https://bugs.launchpad.net/bugs/637059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
