From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758850Ab2DYC5k (ORCPT ); Tue, 24 Apr 2012 22:57:40 -0400 Received: from smtp.syd.comcen.com.au ([203.23.236.77]:4768 "EHLO smtp.syd.comcen.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758832Ab2DYC5j (ORCPT ); Tue, 24 Apr 2012 22:57:39 -0400 X-Greylist: delayed 456 seconds by postgrey-1.27 at vger.kernel.org; Tue, 24 Apr 2012 22:57:39 EDT Date: Wed, 25 Apr 2012 12:49:25 +1000 From: Chris Jones To: Linux Kernel Mailing List Subject: 3.1+ kernels unbootable Message-ID: <20120425124925.267056b5@ubuntu> X-Mailer: Claws Mail 3.7.4 (GTK+ 2.22.0; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-comcen-MailScanner-Information: Please contact the ISP for more information X-comcen-MailScanner: Found to be clean X-MailScanner-From: chrisjones@spin.net.au Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I understand this mailing list is not a support list. But I am curious as to what could make the Linux kernel non-bootable from 3.1+ kernels? My 3.0 kernel boots just fine with my current system. Regards Chris Jones