From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 194843] [amdgpu] oops [drm:gfx_v8_0_priv_reg_irq] *ERROR* Illegal register access in command stream
Date: Mon, 24 Apr 2017 14:23:05 +0000 [thread overview]
Message-ID: <bug-194843-2300-wibl8eaQp8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194843-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=194843
--- Comment #9 from Johannes Hirte (johannes.hirte@datenkhaos.de) ---
(In reply to Johannes Hirte from comment #8)
> (In reply to Michel Dänzer from comment #7)
> > I wonder if there might be memory corruption going on, in which case
> > enabling CONFIG_KASAN for the kernel build might give more clues.
>
> I was testing the last days with KASAN enabled and didn't hit one hang or
> other BUG message in the logs.
I have to correct this. Found in the logs three use-after-free from
find_cpio_data
The most detailed was this one:
Apr 23 11:55:16 probook kernel: smpboot: Booting Node 0 Processor 1 APIC 0x11
Apr 23 11:55:16 probook kernel:
==================================================================
Apr 23 11:55:16 probook kernel: BUG: KASAN: use-after-free in
find_cpio_data+0x4d8/0x570 at addr ffff880037991000
Apr 23 11:55:16 probook kernel: Read of size 1 by task swapper/1/0
Apr 23 11:55:16 probook kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted
4.11.0-rc7-00006-g3e06d0af3e4b #164
Apr 23 11:55:16 probook kernel: Hardware name: HP HP ProBook 645 G2/80FE, BIOS
N77 Ver. 01.07 11/01/2016
Apr 23 11:55:16 probook kernel: Call Trace:
Apr 23 11:55:16 probook kernel: dump_stack+0x4f/0x66
Apr 23 11:55:16 probook kernel: kasan_object_err+0x1c/0x70
Apr 23 11:55:16 probook kernel: kasan_report+0x252/0x510
Apr 23 11:55:16 probook kernel: ? find_cpio_data+0x4d8/0x570
Apr 23 11:55:16 probook kernel: ? put_dec+0xb0/0xb0
Apr 23 11:55:16 probook kernel: __asan_report_load1_noabort+0x14/0x20
Apr 23 11:55:16 probook kernel: find_cpio_data+0x4d8/0x570
Apr 23 11:55:16 probook kernel: ? dump_stack+0x66/0x66
Apr 23 11:55:16 probook kernel: ? snprintf+0x87/0xb0
Apr 23 11:55:16 probook kernel: ? vsprintf+0x20/0x20
Apr 23 11:55:16 probook kernel: find_microcode_in_initrd+0x229/0x3c0
Apr 23 11:55:16 probook kernel: ? get_builtin_firmware+0x5e/0x120
Apr 23 11:55:16 probook kernel: __load_ucode_amd+0x11c/0x240
Apr 23 11:55:16 probook kernel: ? clockevents_program_event+0x1a2/0x2c0
Apr 23 11:55:16 probook kernel: ? apply_microcode_amd+0x3d0/0x3d0
Apr 23 11:55:16 probook kernel: ? pick_next_task_fair+0x7a3/0xfe0
Apr 23 11:55:16 probook kernel: ? pick_next_task_fair+0x7a3/0xfe0
Apr 23 11:55:16 probook kernel: load_ucode_amd_ap+0x90/0x100
Apr 23 11:55:16 probook kernel: ? load_ucode_amd_ap+0x90/0x100
Apr 23 11:55:16 probook kernel: ? __load_ucode_amd+0x240/0x240
Apr 23 11:55:16 probook kernel: ? flat_send_IPI_mask+0x2b/0x40
Apr 23 11:55:16 probook kernel: ? sched_clock_cpu+0x1b/0x1e0
Apr 23 11:55:16 probook kernel: ? default_send_IPI_single+0x77/0xa0
Apr 23 11:55:16 probook kernel: load_ucode_ap+0x80/0x90
Apr 23 11:55:16 probook kernel: cpu_init+0x7dc/0xd40
Apr 23 11:55:16 probook kernel: ? smp_call_function_single+0xf7/0x340
Apr 23 11:55:16 probook kernel: ? syscall_init+0x140/0x140
Apr 23 11:55:16 probook kernel: ? debug_smp_processor_id+0x17/0x20
Apr 23 11:55:16 probook kernel: ? native_play_dead+0xf2/0x120
Apr 23 11:55:16 probook kernel: ? arch_cpu_idle_dead+0x28/0x40
Apr 23 11:55:16 probook kernel: ? do_idle+0x206/0x2d0
Apr 23 11:55:16 probook kernel: start_secondary+0x12/0x2c0
Apr 23 11:55:16 probook kernel: ? start_secondary+0x12/0x2c0
Apr 23 11:55:16 probook kernel: start_cpu+0x14/0x14
Apr 23 11:55:16 probook kernel: Object at ffff880037990f00, in cache
kmalloc-512 size: 512
Apr 23 11:55:16 probook kernel: Allocated:
Apr 23 11:55:16 probook kernel: PID = 4012
Apr 23 11:55:16 probook kernel: save_stack_trace+0x16/0x20
Apr 23 11:55:16 probook kernel: save_stack+0x46/0xd0
Apr 23 11:55:16 probook kernel: kasan_kmalloc+0xad/0xe0
Apr 23 11:55:16 probook kernel: kasan_slab_alloc+0x12/0x20
Apr 23 11:55:16 probook kernel: __kmalloc_node_track_caller+0xfe/0x290
Apr 23 11:55:16 probook kernel: __kmalloc_reserve.isra.36+0x2c/0xc0
Apr 23 11:55:16 probook kernel: __alloc_skb+0xd0/0x560
Apr 23 11:55:16 probook kernel: alloc_skb_with_frags+0x8d/0x4c0
Apr 23 11:55:16 probook kernel: sock_alloc_send_pskb+0x587/0x6f0
Apr 23 11:55:16 probook kernel: unix_stream_sendmsg+0x57d/0x880
Apr 23 11:55:16 probook kernel: sock_sendmsg+0xb5/0xf0
Apr 23 11:55:16 probook kernel: sock_write_iter+0x1e0/0x3b0
Apr 23 11:55:16 probook kernel: __do_readv_writev+0x2b7/0x350
Apr 23 11:55:16 probook kernel: do_readv_writev+0x79/0xb0
Apr 23 11:55:16 probook kernel: vfs_writev+0x37/0x50
Apr 23 11:55:16 probook kernel: do_writev+0x4d/0xd0
Apr 23 11:55:16 probook kernel: SyS_writev+0xb/0x10
Apr 23 11:55:16 probook kernel: entry_SYSCALL_64_fastpath+0x13/0x94
Apr 23 11:55:16 probook kernel: Freed:
Apr 23 11:55:16 probook kernel: PID = 4281
Apr 23 11:55:16 probook kernel: save_stack_trace+0x16/0x20
Apr 23 11:55:16 probook kernel: save_stack+0x46/0xd0
Apr 23 11:55:16 probook kernel: kasan_slab_free+0x73/0xc0
Apr 23 11:55:16 probook kernel: kfree+0x91/0x1c0
Apr 23 11:55:16 probook kernel: skb_free_head+0x6a/0x90
Apr 23 11:55:16 probook kernel: skb_release_data+0x279/0x330
Apr 23 11:55:16 probook kernel: skb_release_all+0x3d/0x50
Apr 23 11:55:16 probook kernel: consume_skb+0x62/0x180
Apr 23 11:55:16 probook kernel: unix_stream_read_generic+0x1493/0x1b50
Apr 23 11:55:16 probook kernel: unix_stream_recvmsg+0x8a/0xa0
Apr 23 11:55:16 probook kernel: sock_recvmsg+0xc2/0x100
Apr 23 11:55:16 probook kernel: ___sys_recvmsg+0x227/0x590
Apr 23 11:55:16 probook kernel: __sys_recvmsg+0xbe/0x140
Apr 23 11:55:16 probook kernel: SyS_recvmsg+0xd/0x20
Apr 23 11:55:16 probook kernel: entry_SYSCALL_64_fastpath+0x13/0x94
Apr 23 11:55:16 probook kernel: Memory state around the buggy address:
Apr 23 11:55:16 probook kernel: ffff880037990f00: fb fb fb fb fb fb fb fb fb
fb fb fb fb fb fb fb
Apr 23 11:55:16 probook kernel: ffff880037990f80: fb fb fb fb fb fb fb fb fb
fb fb fb fb fb fb fb
Apr 23 11:55:16 probook kernel: >ffff880037991000: fb fb fb fb fb fb fb fb fb
fb fb fb fb fb fb fb
Apr 23 11:55:16 probook kernel: ^
Apr 23 11:55:16 probook kernel: ffff880037991080: fb fb fb fb fb fb fb fb fb
fb fb fb fb fb fb fb
Apr 23 11:55:16 probook kernel: ffff880037991100: fc fc fc fc fc fc fc fc fc
fc fc fc fc fc fc fc
Apr 23 11:55:16 probook kernel:
==================================================================
Apr 23 11:55:16 probook kernel: Disabling lock debugging due to kernel taint
THe other two entries don't have the Allocated/Freed part.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-24 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 20:34 [Bug 194843] New: [amdgpu] oops [drm:gfx_v8_0_priv_reg_irq] *ERROR* Illegal register access in command stream bugzilla-daemon
2017-03-10 20:40 ` [Bug 194843] " bugzilla-daemon
2017-03-10 21:05 ` bugzilla-daemon
2017-03-10 21:05 ` bugzilla-daemon
2017-03-10 21:08 ` bugzilla-daemon
2017-03-12 11:26 ` bugzilla-daemon
2017-04-18 19:40 ` bugzilla-daemon
2017-04-19 3:23 ` bugzilla-daemon
2017-04-24 12:49 ` bugzilla-daemon
2017-04-24 14:23 ` bugzilla-daemon [this message]
2017-06-21 19:04 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-194843-2300-wibl8eaQp8@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.