From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PaCRU-0002qq-Pp for garchives@archives.gentoo.org; Tue, 04 Jan 2011 19:21:13 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 765E2E0741; Tue, 4 Jan 2011 19:19:25 +0000 (UTC) Received: from r00tworld.com (r00tworld.com [212.85.137.150]) by pigeon.gentoo.org (Postfix) with ESMTP id 1BA5EE0741 for ; Tue, 4 Jan 2011 19:19:24 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by r00tworld.com (8.13.1/8.13.1) with ESMTP id p04JJNcP015383 for ; Tue, 4 Jan 2011 20:19:23 +0100 Received: from r00tworld.com ([127.0.0.1]) by localhost (r00tworld.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 11685-04 for ; Tue, 4 Jan 2011 20:19:22 +0100 (CET) Received: from [192.168.11.1] (x.r00tworld.com [212.85.137.150]) by r00tworld.com (8.13.1/8.13.1) with ESMTP id p04JJKFw015374 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 4 Jan 2011 20:19:20 +0100 From: pageexec@freemail.hu To: gentoo-hardened@lists.gentoo.org Date: Tue, 04 Jan 2011 20:18:46 +0200 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-hardened@lists.gentoo.org Reply-to: gentoo-hardened@lists.gentoo.org MIME-Version: 1.0 Subject: Re: [gentoo-hardened] Disappearing root on 2.6.36-hardened-r6 upgrade Message-ID: <4D237296.27258.60A935CD@pageexec.freemail.hu> Priority: normal In-reply-to: References: <4D16E7BA.3030508@orlitzky.com>, <4D235D07.24046.6055002F@pageexec.freemail.hu>, X-mailer: Pegasus Mail for Windows (4.52) Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: Quoted-printable Content-description: Mail message body X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.12 (r00tworld.com [212.85.137.150]); Tue, 04 Jan 2011 20:19:21 +0100 (CET) X-Virus-Scanned: r00tworld Anti-Virus System X-Archives-Salt: e003aca2-67e4-490c-be63-dddf6043508d X-Archives-Hash: cfa27b523bccececeb5b7c3b2caabb7b On 4 Jan 2011 at 19:38, "T=F3th Attila" wrote: > Would it be possible that the CPU itself is actually failing (opcode 000= 0)? not in this case, always look at the first problem, everything else may ve= ry well be just collateral damage. and that's a BUG_ON so it's the kernel tha= t detects some bad condition. and since that code and condition are fs relat= ed, it's probably best to let the fs guys debug it but they'll deal with it on= ly if you can reproduce it with vanilla.