linux-kernel - Re: [BUG] 3.2-rcX radeon KMS system freeze

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] [day] [month] [year] [list]

Message-ID: <20111125230012.GA4014@gherkin.frus.com>
Date:	Fri, 25 Nov 2011 17:00:12 -0600
From:	Bob Tracy <rct@...rkin.frus.com>
To:	linux-kernel@...r.kernel.org
Cc:	airlied@...ux.ie
Subject: Re: [BUG] 3.2-rcX radeon KMS system freeze

On Fri, Nov 25, 2011 at 02:33:51PM -0600, Bob Tracy wrote:
> Apologies for the less-than-useful bug report.  If there's anything I
> can do to generate/capture more diagnostic info, please don't hesitate
> to let me know.  I'll be able to try a 3.2-rc3 kernel later today.

Update for 3.2-rc3.  Logged-in via the kdm-greeter screen, and just as
soon as the kde session initialization started, I toggled back to a
virtual console to see if any error messages were being written there.
The only suspicious thing I saw was *many* messages in syslog of the
form:

<date> <hostname> kernel: do_entUnaUser: 836779 callbacks suppressed

as "virtuoso-t" started running.  I decided to chance switching to the
X11 session, and it ran for a little while before the system froze.  The
freeze "feels" like an out-of-memory condition, which could explain the
lack of error messages.  Things got really slow just before the system
became completely unresponsive.

--Bob
--
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/