Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Radeon related kernel bug??

  1. #1
    Join Date
    Jan 2009
    Posts
    1,603

    Default Radeon related kernel bug??

    Got this:

    Code:
    Mar 30 23:15:13 mainland kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
    Mar 30 23:15:13 mainland kernel: IP: [<ffffffffa006f019>] ttm_dma_unpopulate+0x1c9/0x350 [ttm]
    Mar 30 23:15:13 mainland kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Mar 30 23:15:13 mainland kernel: CR2: 0000000000000008 CR3: 000000030aaca000 CR4: 00000000001407e0
    Mar 30 23:15:13 mainland kernel: Stack:
    Mar 30 23:15:13 mainland kernel:  ffff8800dcfe9b58 ffff8800dcfe9b00 ffffffffa01b9240 ffff88030b71c700
    Mar 30 23:15:13 mainland kernel:  0000000000000000 ffff8800dc070848 ffff88030aefbd40 ffffffffa00b13af
    Mar 30 23:15:13 mainland kernel:  ffff8800dcfe9b00 ffffffffa01b9240 ffff88030b64fe08 ffff88030aefbd58
    Mar 30 23:15:13 mainland kernel: Call Trace:
    Mar 30 23:15:13 mainland kernel:  [<ffffffffa00b13af>] radeon_ttm_tt_unpopulate+0xcf/0xe0 [radeon]
    Mar 30 23:15:13 mainland kernel:  [<ffffffffa006606a>] ttm_tt_destroy+0x6a/0x70 [ttm]
    Mar 30 23:15:13 mainland kernel:  [<ffffffffa00669ef>] ttm_bo_cleanup_memtype_use+0x3f/0x80 [ttm]
    Mar 30 23:15:13 mainland kernel:  [<ffffffffa0067896>] ttm_bo_cleanup_refs_and_unlock+0x196/0x280 [ttm]
    Mar 30 23:15:13 mainland kernel:  [<ffffffffa0067a26>] ttm_bo_delayed_delete+0xa6/0x220 [ttm]
    Mar 30 23:15:13 mainland kernel:  [<ffffffffa0067bbb>] ttm_bo_delayed_workqueue+0x1b/0x40 [ttm]
    Mar 30 23:15:13 mainland kernel:  [<ffffffff8107c4f7>] process_one_work+0x167/0x420
    Mar 30 23:15:13 mainland kernel:  [<ffffffff8107cec1>] worker_thread+0x121/0x3a0
    Mar 30 23:15:13 mainland kernel:  [<ffffffff8107cda0>] ? manage_workers.isra.23+0x2a0/0x2a0
    Mar 30 23:15:13 mainland kernel:  [<ffffffff810835b2>] kthread+0xd2/0xf0
    Mar 30 23:15:13 mainland kernel:  [<ffffffff810834e0>] ? kthread_create_on_node+0x180/0x180
    Mar 30 23:15:13 mainland kernel:  [<ffffffff81521abc>] ret_from_fork+0x7c/0xb0
    Mar 30 23:15:13 mainland kernel:  [<ffffffff810834e0>] ? kthread_create_on_node+0x180/0x180
    Mar 30 23:15:13 mainland kernel: Code: c6 4d 8d 7d 71 e8 38 af 4a e1 4c 8b 63 58 4c 3b 65 d0 4d 8b 34 24 75 5a e9 c5 fe ff ff 0f 1f 44 00 00 49 8b 14 24 49 8b 44 24 08 <48> 89 42 08 48 89 10 48 b8 00 01 10 00 00 00 ad de 49
    Mar 30 23:15:13 mainland kernel: RIP  [<ffffffffa006f019>] ttm_dma_unpopulate+0x1c9/0x350 [ttm]
    Mar 30 23:15:13 mainland kernel:  RSP <ffff88030aefbce8>
    Mar 30 23:15:13 mainland kernel: CR2: 0000000000000008
    Mar 30 23:15:13 mainland kernel: ---[ end trace edc2ead1aea86ee9 ]---
    Mar 30 23:15:13 mainland kernel: BUG: unable to handle kernel paging request at ffffffffffffffd8
    Code:
    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD BARTS
    OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.0
    OpenGL core profile shading language version string: 3.30
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 3.0 Mesa 10.1.0
    OpenGL shading language version string: 1.30
    OpenGL context flags: (none)
    OpenGL extensions:
    Code:
    Linux mainland 3.13.7-1-ARCH #1 SMP PREEMPT Mon Mar 24 20:06:08 CET 2014 x86_64 GNU/Linux


    Any ideas.

  2. #2
    Join Date
    Oct 2012
    Posts
    181

    Default

    Google says you'd need to check your system to check for problems, for example, by running memtest or by using other distros/OSes.
    The first thing I always do when I find problems is to google them and check for similar things. If there aren't any, the problem is probably in my side... in this case: http://www.google.com/search?q=%22un...22&btnG=Search I can't find similar patterns. Anyway, you didn't provide any contexts on when and how it crashes, so I don't have enough info to say anything.
    If you are able to reproduce and you are confident that the problem is not in your system, you report it in https://bugzilla.kernel.org/ .

  3. #3
    Join Date
    Jan 2009
    Posts
    1,603

    Default

    Code:
    Jun 09 21:57:33 mainland kernel: perf samples too long (2502 > 2500), lowering kernel.perf_event_max_sample_rate to 50100
    Jun 09 23:02:41 mainland kernel: general protection fault: 0000 [#1] PREEMPT SMP
    Jun 09 23:02:41 mainland kernel: Modules linked in: vboxdrv(O) usb_storage hid_generic mousedev hid_logitech_dj usbhid hid w83627ehf hwmon_vid snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hd
    Jun 09 23:02:41 mainland kernel:  usbcore usb_common sr_mod cdrom sd_mod crc_t10dif crct10dif_common ahci libahci libata scsi_mod radeon hwmon i2c_algo_bit drm_kms_helper ttm drm i2c_core [last unloaded:
    Jun 09 23:02:41 mainland kernel: CPU: 7 PID: 368 Comm: X Tainted: G           O 3.14.6-1-ARCH #1
    Jun 09 23:02:41 mainland kernel: Hardware name:                  /DZ77BH-55K, BIOS BHZ7710H.86A.0094.2012.1101.1115 11/01/2012
    Jun 09 23:02:41 mainland kernel: task: ffff88030b39a740 ti: ffff8800df7d8000 task.ti: ffff8800df7d8000
    Jun 09 23:02:41 mainland kernel: RIP: 0010:[<ffffffff8119c597>]  [<ffffffff8119c597>] kmem_cache_alloc_trace+0x77/0x220
    Jun 09 23:02:41 mainland kernel: RSP: 0018:ffff8800df7d9930  EFLAGS: 00010282
    Jun 09 23:02:41 mainland kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000026bc1887
    Jun 09 23:02:41 mainland kernel: RDX: 0000000026bc1807 RSI: ffff88031edd74a0 RDI: ffff880312003b00
    Jun 09 23:02:41 mainland kernel: RBP: ffff8800df7d9968 R08: 00000000000174a0 R09: ffff880312003c00
    Jun 09 23:02:41 mainland kernel: R10: ffffffffa0070df1 R11: ffff88030bb1c7a8 R12: 00ffffff00ffffff
    Jun 09 23:02:41 mainland kernel: R13: 00000000000000d0 R14: ffff880312003b00 R15: ffff880312003b00
    Jun 09 23:02:41 mainland kernel: FS:  00007fc4e535a880(0000) GS:ffff88031edc0000(0000) knlGS:0000000000000000
    Jun 09 23:02:41 mainland kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Jun 09 23:02:41 mainland kernel: CR2: 00007f95d2170000 CR3: 00000000df63b000 CR4: 00000000001427e0
    Jun 09 23:02:41 mainland kernel: Stack:
    Jun 09 23:02:41 mainland kernel:  ffff88030b739240 0000000000000028 0000000000000000 0000000000000000
    Jun 09 23:02:41 mainland kernel:  ffff8802e1d6ab00 0000000000000000 ffff88030b739240 ffff8800df7d9a58
    Jun 09 23:02:41 mainland kernel:  ffffffffa0070df1 ffff88030b39a740 ffff88030b7392a4 ffff88030b739268
    Jun 09 23:02:41 mainland kernel: Call Trace:
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa0070df1>] ttm_dma_populate+0x581/0xa10 [ttm]
    Jun 09 23:02:41 mainland kernel:  [<ffffffff8119cc36>] ? __kmalloc+0x236/0x290
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa00b97af>] radeon_ttm_tt_populate+0x21f/0x240 [radeon]
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa0067050>] ttm_tt_bind+0x40/0x80 [ttm]
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa006950f>] ttm_bo_handle_move_mem+0x5bf/0x650 [ttm]
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa0069d09>] ? ttm_bo_mem_space+0x179/0x370 [ttm]
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa006a455>] ttm_bo_validate+0x265/0x280 [ttm]
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa006a6b5>] ttm_bo_init+0x245/0x3a0 [ttm]
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa00ba4ef>] radeon_bo_create+0x16f/0x230 [radeon]
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa00ba190>] ? radeon_mmap+0x100/0x100 [radeon]
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa00cda76>] radeon_gem_object_create+0xb6/0x1a0 [radeon]
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa00cdf71>] radeon_gem_create_ioctl+0x71/0x180 [radeon]
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa0011cf2>] drm_ioctl+0x4f2/0x600 [drm]
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa00cdf00>] ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon]
    Jun 09 23:02:41 mainland kernel:  [<ffffffff812a00c0>] ? timerqueue_add+0x60/0xb0
    Jun 09 23:02:41 mainland kernel:  [<ffffffffa009c04f>] radeon_drm_ioctl+0x4f/0x90 [radeon]
    Jun 09 23:02:41 mainland kernel:  [<ffffffff811cd860>] do_vfs_ioctl+0x2d0/0x4b0
    Jun 09 23:02:41 mainland kernel:  [<ffffffff811d7d0e>] ? __fget+0x6e/0xb0
    Jun 09 23:02:41 mainland kernel:  [<ffffffff811cdac1>] SyS_ioctl+0x81/0xa0
    Jun 09 23:02:41 mainland kernel:  [<ffffffff81517b29>] system_call_fastpath+0x16/0x1b
    Jun 09 23:02:41 mainland kernel: Code: 0f 84 c6 00 00 00 4c 8b 26 4d 85 e4 0f 84 62 01 00 00 48 83 7e 10 00 0f 84 57 01 00 00 49 63 47 20 48 8d 8a 80 00 00 00 4d 8b 07 <49> 8b 1c 04 4c 89 e0 65 49 0f c7
    Jun 09 23:02:41 mainland kernel: RIP  [<ffffffff8119c597>] kmem_cache_alloc_trace+0x77/0x220
    Jun 09 23:02:41 mainland kernel:  RSP <ffff8800df7d9930>
    Jun 09 23:02:41 mainland kernel: ---[ end trace e3b055a1f662e536 ]---
    Jun 09 23:03:04 mainland kernel: general protection fault: 0000 [#2] PREEMPT SMP
    Jun 09 23:03:04 mainland kernel: Modules linked in: vboxdrv(O) usb_storage hid_generic mousedev hid_logitech_dj usbhid hid w83627ehf hwmon_vid snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hd
    Jun 09 23:03:04 mainland kernel:  usbcore usb_common sr_mod cdrom sd_mod crc_t10dif crct10dif_common ahci libahci libata scsi_mod radeon hwmon i2c_algo_bit drm_kms_helper ttm drm i2c_core [last unloaded:
    Jun 09 23:03:04 mainland kernel: CPU: 7 PID: 2939 Comm: EMT Tainted: G      D    O 3.14.6-1-ARCH #1
    Jun 09 23:03:04 mainland kernel: Hardware name:                  /DZ77BH-55K, BIOS BHZ7710H.86A.0094.2012.1101.1115 11/01/2012
    Jun 09 23:03:04 mainland kernel: task: ffff8802ff51b110 ti: ffff8802e1646000 task.ti: ffff8802e1646000
    Jun 09 23:03:04 mainland kernel: RIP: 0010:[<ffffffff8119ca92>]  [<ffffffff8119ca92>] __kmalloc+0x92/0x290
    Jun 09 23:03:04 mainland kernel: RSP: 0018:ffff8802e1647db8  EFLAGS: 00010282
    Jun 09 23:03:04 mainland kernel: RAX: 0000000000000000 RBX: 0000000080000000 RCX: 0000000026bc1887
    Jun 09 23:03:04 mainland kernel: RDX: 0000000026bc1807 RSI: ffff88031edd74a0 RDI: 0000000000000007
    Jun 09 23:03:04 mainland kernel: RBP: ffff8802e1647df0 R08: 00000000000174a0 R09: ffff880312003b00
    Jun 09 23:03:04 mainland kernel: R10: ffffffffa04d2d89 R11: 0000000000000246 R12: 00ffffff00ffffff
    Jun 09 23:03:04 mainland kernel: R13: 00000000000000d0 R14: 0000000000000040 R15: ffff880312003b00
    Jun 09 23:03:04 mainland kernel: FS:  00007f705e893700(0000) GS:ffff88031edc0000(0000) knlGS:0000000000000000
    Jun 09 23:03:04 mainland kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Jun 09 23:03:04 mainland kernel: CR2: 00007f95d2170000 CR3: 000000030a9f3000 CR4: 00000000001427e0
    Jun 09 23:03:04 mainland kernel: Stack:
    Jun 09 23:03:04 mainland kernel:  ffffc90006127000 ffffffffa04d2d89 0000000080000000 0000000000000040
    Jun 09 23:03:04 mainland kernel:  0000000000000000 0000000000000030 0000000000000030 ffff8802e1647e48
    Jun 09 23:03:04 mainland kernel:  ffffffffa04d2d89 00007f705e892ce0 ffff8802e1647e58 ffff8802e1647e38
    Jun 09 23:03:04 mainland kernel: Call Trace:
    Jun 09 23:03:04 mainland kernel:  [<ffffffffa04d2d89>] ? rtR0MemAllocEx+0x1c9/0x2c0 [vboxdrv]
    Jun 09 23:03:04 mainland kernel:  [<ffffffffa04d2d89>] rtR0MemAllocEx+0x1c9/0x2c0 [vboxdrv]
    Jun 09 23:03:04 mainland kernel:  [<ffffffffa04d0927>] VBoxHost_RTMemAllocTag+0x27/0x60 [vboxdrv]
    Jun 09 23:03:04 mainland kernel:  [<ffffffffa04c44a5>] VBoxDrvLinuxIOCtl_4_3_12+0xf5/0x1e0 [vboxdrv]
    Jun 09 23:03:04 mainland kernel:  [<ffffffff811cd860>] do_vfs_ioctl+0x2d0/0x4b0
    Jun 09 23:03:04 mainland kernel:  [<ffffffff811d7d0e>] ? __fget+0x6e/0xb0
    Jun 09 23:03:04 mainland kernel:  [<ffffffff811cdac1>] SyS_ioctl+0x81/0xa0
    Jun 09 23:03:04 mainland kernel:  [<ffffffff81517b29>] system_call_fastpath+0x16/0x1b
    Jun 09 23:03:04 mainland kernel: Code: 0f 84 03 01 00 00 4c 8b 26 4d 85 e4 0f 84 77 01 00 00 48 83 7e 10 00 0f 84 6c 01 00 00 49 63 47 20 48 8d 8a 80 00 00 00 4d 8b 07 <49> 8b 1c 04 4c 89 e0 65 49 0f c7
    Jun 09 23:03:04 mainland kernel: RIP  [<ffffffff8119ca92>] __kmalloc+0x92/0x290
    Jun 09 23:03:04 mainland kernel:  RSP <ffff8802e1647db8>
    Jun 09 23:03:04 mainland kernel: ---[ end trace e3b055a1f662e537 ]---
    This is getting stupid.

  4. #4
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,994

    Default

    It's clearly not radeon when vbox is causing it too. Your system is hosed. Run memtest.

  5. #5
    Join Date
    Jan 2009
    Posts
    1,603

    Default

    Quote Originally Posted by curaga View Post
    It's clearly not radeon when vbox is causing it too. Your system is hosed. Run memtest.

    Did it on various occasions. No errors.

  6. #6
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,994

    Default

    How long? One pass is not nearly enough, I've seen systems where the errors only showed up on the fifth pass.

  7. #7
    Join Date
    Jun 2012
    Posts
    293

    Default

    Quote Originally Posted by curaga View Post
    How long? One pass is not nearly enough, I've seen systems where the errors only showed up on the fifth pass.
    I've seen systems where memtests would not find anything at all while running with faulty RAM. However, decompressing huge ZIP files would eventually give CRC errors even if ZIP file is okay (key thing is to keep ZIP decompressing data for about 10 minutes or so). It looks like if ZIP memory access pattern is more localized and can increase themperature of particular IC/module higher than memtest patterns would normally do. So it can be very strange case where memtests does not detects any trouble, but some rare localized system loads still can cause memory corruption. Such cases are really hard to pinpoint. And btw, bugged driver or some wrong hardware actions (e.g. bad DMA transaction) can also corrupt system memory in really strange ways.

    P.S. on side note, ECC RAM is a really good thing in this regard. Special thanks are going to AMD, who makes it possible on desktop hardware at sane price tags. This way I can be more or less *sure* RAM works reliably.

  8. #8
    Join Date
    Jan 2009
    Posts
    1,603

    Default

    Quote Originally Posted by curaga View Post
    How long? One pass is not nearly enough, I've seen systems where the errors only showed up on the fifth pass.
    3 passes no errors.

    3.12 kernel and maybe early 3.13 were much more stable. Not that it happens frequently.

  9. #9
    Join Date
    Jan 2009
    Posts
    1,603

    Default

    3.15 fun

    Code:
    Jul 23 22:14:46 mainland kernel: general protection fault: 0000 [#1] PREEMPT SMP
    Jul 23 22:14:46 mainland kernel: Modules linked in: mousedev hid_logitech_dj hid_generic usbhid hid snd_hda_codec_realtek w83627ehf hwmon_vid snd_hda_codec_generic snd_hda_codec_hdmi coretemp nls_iso8859_1 nls_cp437 vfat fat intel_rapl x
    Jul 23 22:14:46 mainland kernel:  sr_mod cdrom usbcore usb_common sd_mod crc_t10dif crct10dif_common ahci libahci libata scsi_mod radeon hwmon i2c_algo_bit drm_kms_helper ttm drm i2c_core
    Jul 23 22:14:46 mainland kernel: CPU: 0 PID: 388 Comm: X Not tainted 3.15.5-2-ARCH #1
    Jul 23 22:14:46 mainland kernel: Hardware name:                  /DZ77BH-55K, BIOS BHZ7710H.86A.0094.2012.1101.1115 11/01/2012
    Jul 23 22:14:46 mainland kernel: task: ffff88030b4bb2f0 ti: ffff88030c18c000 task.ti: ffff88030c18c000
    Jul 23 22:14:46 mainland kernel: RIP: 0010:[<ffffffff81198aff>]  [<ffffffff81198aff>] kmem_cache_alloc_trace+0x6f/0x170
    Jul 23 22:14:46 mainland kernel: RSP: 0018:ffff88030c18f940  EFLAGS: 00010282
    Jul 23 22:14:46 mainland kernel: RAX: 0000000000000000 RBX: ffff88015f77a7c0 RCX: 00000000ab3f9980
    Jul 23 22:14:46 mainland kernel: RDX: 00000000ab3f9900 RSI: 00000000000000d0 RDI: ffffffffa0077e91
    Jul 23 22:14:46 mainland kernel: RBP: ffff88030c18f970 R08: 0000000000017520 R09: 0000000000000002
    Jul 23 22:14:46 mainland kernel: R10: 0000000000003919 R11: 000000000000001f R12: fe111213fe111213
    Jul 23 22:14:46 mainland kernel: R13: 00000000000000d0 R14: 0000000000000003 R15: ffff880312003b00
    Jul 23 22:14:46 mainland kernel: FS:  00007fe7ba345880(0000) GS:ffff88031ec00000(0000) knlGS:0000000000000000
    Jul 23 22:14:46 mainland kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Jul 23 22:14:46 mainland kernel: CR2: 00007fe7ad448000 CR3: 000000007fabb000 CR4: 00000000001407f0
    Jul 23 22:14:46 mainland kernel: Stack:
    Jul 23 22:14:46 mainland kernel:  0000000000000028 ffff88015f77a7c0 0000000000000003 ffff8803005103e0
    Jul 23 22:14:46 mainland kernel:  0000000000000003 ffff88030b0739c0 ffff88030c18fa60 ffffffffa0077e91
    Jul 23 22:14:46 mainland kernel:  ffff88030b4bb2f0 ffff88030b073a24 ffff88030b0739e8 ffff88030c877098
    Jul 23 22:14:46 mainland kernel: Call Trace:
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa0077e91>] ttm_dma_populate+0x581/0xa10 [ttm]
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa006e4b4>] ? ttm_dma_tt_init+0xf4/0x120 [ttm]
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa00c2b5f>] radeon_ttm_tt_populate+0x21f/0x240 [radeon]
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa006e050>] ttm_tt_bind+0x40/0x80 [ttm]
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa007050f>] ttm_bo_handle_move_mem+0x5bf/0x650 [ttm]
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa0070d09>] ? ttm_bo_mem_space+0x179/0x370 [ttm]
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa0071455>] ttm_bo_validate+0x265/0x280 [ttm]
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa00716b5>] ttm_bo_init+0x245/0x3a0 [ttm]
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa00c3954>] radeon_bo_create+0x164/0x210 [radeon]
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa00c35d0>] ? radeon_update_memory_usage.isra.3+0x60/0x60 [radeon]
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa00d5cd6>] radeon_gem_object_create+0xb6/0x1a0 [radeon]
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa00d61ce>] radeon_gem_create_ioctl+0x6e/0x180 [radeon]
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa0017b9f>] drm_ioctl+0x1df/0x680 [drm]
    Jul 23 22:14:46 mainland kernel:  [<ffffffff811b59cd>] ? do_readv_writev+0x1bd/0x250
    Jul 23 22:14:46 mainland kernel:  [<ffffffffa00a504c>] radeon_drm_ioctl+0x4c/0x80 [radeon]
    Jul 23 22:14:46 mainland kernel:  [<ffffffff811c7680>] do_vfs_ioctl+0x2d0/0x4b0
    Jul 23 22:14:46 mainland kernel:  [<ffffffff811d1d8e>] ? __fget+0x6e/0xb0
    Jul 23 22:14:46 mainland kernel:  [<ffffffff811c78e1>] SyS_ioctl+0x81/0xa0
    Jul 23 22:14:46 mainland kernel:  [<ffffffff81515fa9>] system_call_fastpath+0x16/0x1b
    Jul 23 22:14:46 mainland kernel: Code: 0f 84 c6 00 00 00 4c 8b 20 4d 85 e4 0f 84 da 00 00 00 48 83 78 10 00 0f 84 cf 00 00 00 49 63 47 20 48 8d 8a 80 00 00 00 4d 8b 07 <49> 8b 1c 04 4c 89 e0 65 49 0f c7 08 0f 94 c0 84 c0 74 a2 49 63
    Jul 23 22:14:46 mainland kernel: RIP  [<ffffffff81198aff>] kmem_cache_alloc_trace+0x6f/0x170

  10. #10
    Join Date
    Jun 2011
    Posts
    837

    Default

    I'm with the others on this probably being memory going bad, compiling large code bases are actually another good test, basically if GCC sigsevs you know you've got memory issues.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •