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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 22 Dec 2011 15:38:43 -0800 From: Tejun Heo <tj@...nel.org> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, linux-scsi@...r.kernel.org, Jens Axboe <axboe@...nel.dk>, linux-ide@...r.kernel.org, x86@...nel.org Subject: Re: linux-next: Tree for Dec 21 On Thu, Dec 22, 2011 at 03:24:27PM -0800, Andrew Morton wrote: > > Hmmm... probably cic allocation failure? > > Dunno, it's an 8Gb 8 CPU x86_64 box. > > > It's just that those cases happened infrequently > > enough that nobody really noticed (or at least tracked it down). How > > can you reproduce the problem? > > Easily. One time it got to a login prompt and hung quickly during a > make. Every other time (ten times, maybe) it hung during initscripts. Weird, I can't reproduce the problem on block/for-3.3/core. Trying linux-next... hmmm, it works there too. Can you please share .config? Thanks. -- tejun -- 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/
Powered by blists - more mailing lists