linux-kernel - Re: Bisecting radeon kms freeze bug: Almost there, please help with choosing next commit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 7 Sep 2010 14:34:25 -0400
From:	Alex Deucher <alexdeucher@...il.com>
To:	Martin Steigerwald <Martin@...htvoll.de>
Cc:	Dave Airlie <airlied@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: Bisecting radeon kms freeze bug: Almost there, please help with
 choosing next commit

On Tue, Sep 7, 2010 at 10:34 AM, Martin Steigerwald <Martin@...htvoll.de> wrote:
>
> Hello Alex and und Dave,
>
> please excuse typing errors. The machine is abysmally slow with that
> kernel.
>
> I am almost there with bisecting Bug 16376, random - possibly Radeon DRM
> KM related - freezes. I think I found the merge where is issue has been
> introduced and I am now testing
>
> martin@...mbhala:~/Computer/Shambhala/Kernel/2.6.33-2.6.34-
> bisect/linux-2.6> git log | head
> commit 6ad86c311a8b8a6d856527a1b6ba21790ab7054b
> Author: Alex Deucher <alexdeucher@...il.com>
> Date:   Thu Feb 11 10:47:52 2010 -0500
>
>    drm/radeon/kms: remove HDP flushes from fence emit (v2)
>
>    r600_ioctl_wait_idle() now handles this.
>
>    v2: update blit fence counts
>
> Unfortunately it has some other issues that has been fixed later on prior
> to 2.6.34 already:
>
> 7.9.2010 - 2.6.32-tp42-00514-g6ad86c3
> 6ad86c311a8b8a6d856527a1b6ba21790ab7054b
> - Sluggy desktop. Short pauses, locks of about a second.
> - Slow scroll performance on tty.
> - No complete freeze yet.
> - Much CPU time used in system:70-90%
>
> You know the changes in that merge better than me. Can you recommend which
> commits to test next? Som commits may require other ones and thus it might
> be wise to choose the next commits with that in mind. Maybe you already
> have an idea which one it could be. I thought about the memory controllr
> v2 changes, but I really don't have the foggiest.

This might be a duplicate of:
https://bugs.freedesktop.org/show_bug.cgi?id=28402
Does the patch there help?

Alex

>
>
> Here is excerpt from atop which shows ridicully high system CPU usage with
> that kernel.
>
> ATOP - shambhala          2010/09/07  16:11:22               10 seconds
> elapsed
> PRC | sys   8.66s | user   1.30s | #proc    195 | #zombie    0 | #exit
> 0 |
> CPU | sys     85% | user     11% | irq       4% | idle      0% | wait
> 0% |
> CPL | avg1   3.39 | avg5    3.80 | avg15   3.25 | csw    18458 | intr
> 11472 |
> MEM | tot    2.0G | free  543.1M | cache 759.6M | buff   95.0M | slab
> 37.8M |
> SWP | tot    3.8G | free    3.8G |              | vmcom   1.3G | vmlim
> 4.8G |
> DSK |         sda | busy      3% | read       1 | write     95 | avio    2
> ms |
>
> I wrote by mail since bugzilla has too many MySQL connections again. Maybe
> bug can be switched to mail?
>
> Rebooting and testing this kernel another time whether it hard freezes,
> --
> Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
> GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/