linux-kernel - Re: 2.6.39-rc2 boot crash

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]

Message-ID: <4DA44A73.3060801@trash.net>
Date:	Tue, 12 Apr 2011 14:49:55 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	Evgeniy Polyakov <zbr@...emap.net>
CC:	Eric B Munson <emunson@...bm.net>,
	David Miller <davem@...emloft.net>, dave@...ux.vnet.ibm.com,
	linux-kernel@...r.kernel.org, gregkh@...e.de,
	ksrinivasan@...ell.com, NetDev <netdev@...r.kernel.org>
Subject: Re: 2.6.39-rc2 boot crash

On 12.04.2011 00:06, Evgeniy Polyakov wrote:
> Hi.
> 
> On Mon, Apr 11, 2011 at 05:07:47PM -0400, Eric B Munson (emunson@...bm.net) wrote:
>>> I can't figure this out, the only thing that should have changed is the
>>> time the initial PROC_CN_MCAST_LISTEN message is received. Apparently
>>> at that point connector is not fully initialized yet. Please post your
>>> config and the full boot log. Thanks.
>>>
>>
>> I am still seeing this on Linus' tree, is there anything more I can do to help
>> track the problem?

Sorry, I had a hardware failure, I'm back working on this now.

> Patrick, do you need my assist on this bug?

Thanks, but I can meanwhile reproduce the problem, so I think I
should have a fix soon.

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