All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vadim Girlin <vadimgirlin@gmail.com>
To: dri-devel@lists.freedesktop.org
Subject: Re: radeon: 4.2-rc1 warning when unplugging DVI
Date: Tue, 7 Jul 2015 01:15:24 +0300	[thread overview]
Message-ID: <559AFDFC.8000501@gmail.com> (raw)
In-Reply-To: <559AFC37.4090507@gmail.com>

On 07/07/2015 01:07 AM, Vadim Girlin wrote:
> On 07/06/2015 11:56 PM, Alex Deucher wrote:
>> On Mon, Jul 6, 2015 at 3:19 PM, Dave Jones <davej@codemonkey.org.uk>
>> wrote:
>>> I wanted to switch my LCD to a different machine momentarily.
>>> When I plugged the cable back in, this was on the screen..
>>
>> Is this readily reproducible?  Did it happen with 4.1?  If it also
>> happens with 4.1 does reverting
>> 39fa10f7e21574a70cecf1fed0f9b36535aa68a0 help?  If it doesn't happen
>> with 4.1, can you bisect?
>
> That issue is reproducible for me with the changes after 4.1, but 4.1 is

By issue I mean the "don't has a mapping" flood, not sure if the thread 
is discussing something else already. I usually hit it after resume, and 
I typically had to reboot, that solves it.


> stable for me, I'm using it right now for that reason, radeon is pretty
> much broken for me after 4.1, doesn't resume etc (CIK/hawaii gpu).
>
> I'll test it with that patch reverted. Please let me know what
> additional info do you need, dmesg etc...
>
>>
>> Alex
>>
>>>
>>> WARNING: CPU: 1 PID: 209 at kernel/locking/mutex.c:526
>>> __mutex_lock_slowpath+0x322/0x340()
>>> DEBUG_LOCKS_WARN_ON(l->magic != l)
>>> CPU: 1 PID: 209 Comm: kworker/1:3 Not tainted 4.2.0-rc1-gelk-debug+ #1
>>> Workqueue: events radeon_hotplug_work_func [radeon]
>>>   0000000000000009 ffff8800b160bc78 ffffffff9969fad4 0000000080000001
>>>   ffff8800b160bcc8 ffff8800b160bcb8 ffffffff9907689a 00000000000086be
>>>   ffff8800a24182b8 ffff8800a24182c0 ffff8800b086adc0 ffff8800a24182b8
>>> Call Trace:
>>>   [<ffffffff9969fad4>] dump_stack+0x4f/0x7b
>>>   [<ffffffff9907689a>] warn_slowpath_common+0x8a/0xc0
>>>   [<ffffffff99076916>] warn_slowpath_fmt+0x46/0x50
>>>   [<ffffffff996a54f2>] __mutex_lock_slowpath+0x322/0x340
>>>   [<ffffffff996a553c>] mutex_lock+0x2c/0x40
>>>   [<ffffffffc02895e6>] radeon_hotplug_work_func+0x26/0x80 [radeon]
>>>   [<ffffffff9908eba7>] process_one_work+0x147/0x420
>>>   [<ffffffff9908f209>] worker_thread+0x69/0x470
>>>   [<ffffffff990a02b3>] ? preempt_count_sub+0xa3/0xf0
>>>   [<ffffffff9908f1a0>] ? rescuer_thread+0x320/0x320
>>>   [<ffffffff990941e7>] kthread+0x107/0x120
>>>   [<ffffffff990940e0>] ? kthread_create_on_node+0x1b0/0x1b0
>>>   [<ffffffff996a7b1f>] ret_from_fork+0x3f/0x70
>>>   [<ffffffff990940e0>] ? kthread_create_on_node+0x1b0/0x1b0
>>> ---[ end trace 859b3faf9cb20dd3 ]---
>>> Oops: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
>>> CPU: 1 PID: 209 Comm: kworker/1:3 Tainted: G        W
>>> 4.2.0-rc1-gelk-debug+ #1
>>> Workqueue: events radeon_hotplug_work_func [radeon]
>>> task: ffff8800b086adc0 ti: ffff8800b1608000 task.ti: ffff8800b1608000
>>> RIP: 0010:[<ffffffff9932ffef>]  [<ffffffff9932ffef>]
>>> __list_add+0x1f/0xc0
>>> RSP: 0018:ffff8800b160bcf8  EFLAGS: 00010046
>>> RAX: ffff8800a24182d8 RBX: ffff8800b160bd38 RCX: 0000000000000000
>>> RDX: ffff8800a24182d8 RSI: 0000000000000000 RDI: ffff8800b160bd38
>>> RBP: ffff8800b160bd18 R08: 0000000000000000 R09: 0000000000000fcb
>>> R10: 0000000000000353 R11: 00000000ffffffff R12: ffff8800a24182d8
>>> R13: 0000000000000000 R14: 00000000ffffffff R15: 0000000000000246
>>> FS:  0000000000000000(0000) GS:ffff8800bf700000(0000)
>>> knlGS:0000000000000000
>>> CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
>>> CR2: 0000000000000000 CR3: 00000000a25d3000 CR4: 00000000000007e0
>>> Stack:
>>>   ffff8800b160bd18 ffff8800a24182b8 ffff8800a24182c0 ffff8800b086adc0
>>>   ffff8800b160bd88 ffffffff996a5291 ffff8800b160bd58 ffff8800a24182d8
>>>   ffff8800b160bd38 ffff8800b160bd38 1111111111111111 ffff8800b160bd38
>>> Call Trace:
>>>   [<ffffffff996a5291>] __mutex_lock_slowpath+0xc1/0x340
>>>   [<ffffffff996a553c>] mutex_lock+0x2c/0x40
>>>   [<ffffffffc02895e6>] radeon_hotplug_work_func+0x26/0x80 [radeon]
>>>   [<ffffffff9908eba7>] process_one_work+0x147/0x420
>>>   [<ffffffff9908f209>] worker_thread+0x69/0x470
>>>   [<ffffffff990a02b3>] ? preempt_count_sub+0xa3/0xf0
>>>   [<ffffffff9908f1a0>] ? rescuer_thread+0x320/0x320
>>>   [<ffffffff990941e7>] kthread+0x107/0x120
>>>   [<ffffffff990940e0>] ? kthread_create_on_node+0x1b0/0x1b0
>>>   [<ffffffff996a7b1f>] ret_from_fork+0x3f/0x70
>>>   [<ffffffff990940e0>] ? kthread_create_on_node+0x1b0/0x1b0
>>> Code: c3 66 2e 0f 1f 84 00 00 00 00 00 90 55 48 89 e5 41 55 49 89 f5
>>> 41 54 49 89 d4 53 48 89 fb 48 83 ec 08 4c 8b 42 08 49 39 f0 75 2e
>>> <4d> 8b 45 00 4d 39 c4 75 4e 4c 39 e3 74 6b 4c 39 eb 74 66 49 89
>>>
>>>
>>> radeon is an RV370.
>>>
>>>          Dave
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>>
>

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-07-06 22:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 16:23 4.2rc0 "bo don't have a message" flood Dave Jones
2015-07-03 17:56 ` Christian König
2015-07-03 19:14   ` Alex Deucher
2015-07-06 19:19     ` radeon: 4.2-rc1 warning when unplugging DVI Dave Jones
2015-07-06 20:56       ` Alex Deucher
2015-07-06 21:28         ` Dave Jones
2015-07-06 22:07         ` Vadim Girlin
2015-07-06 22:15           ` Vadim Girlin [this message]
2015-07-07  2:55             ` Michel Dänzer
2015-07-07 13:18           ` Alex Deucher

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=559AFDFC.8000501@gmail.com \
    --to=vadimgirlin@gmail.com \
    --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.