linux-kernel - Re: lockups shortly after booting in current git.

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

Date:	Thu, 29 Mar 2012 11:36:49 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dave Jones <davej@...hat.com>, "Theodore Ts'o" <tytso@....edu>,
	Wu Fengguang <fengguang.wu@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: lockups shortly after booting in current git.

On Thu, Mar 29, 2012 at 11:26 AM, Dave Jones <davej@...hat.com> wrote:
> On Thu, Mar 29, 2012 at 09:03:31AM -0700, Linus Torvalds wrote:
>  > Can you do sysrq-w (or whatever it is that does only the D-state
>  > processes)? That might give the more relevant process information without
>  > everything else making it unreadable...
>
> http://codemonkey.org.uk/junk/process-trace2.txt

Ok, this doesn't look all that different, but now it's not truncated
any more because the random "waits for children or poll" cases are
gone.

It's still basically all blocked on the ext4 journal. All writes as
far as I can see.

That said, there's that odd kworker/1:2 there that seems to be
constantly running. Can you get the EIP for that one (several times)
by doing sysrq-p (or maybe sysrq-l is better - that should give the
stack trace too).

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