Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754859Ab2E1QrE (ORCPT ); Mon, 28 May 2012 12:47:04 -0400 Received: from mail-ey0-f174.google.com ([209.85.215.174]:34576 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754318Ab2E1QrC (ORCPT ); Mon, 28 May 2012 12:47:02 -0400 Date: Mon, 28 May 2012 18:46:26 +0200 (CEST) From: Eldad Zack X-X-Sender: eldad@debianer To: "Rafael J. Wysocki" cc: Alan Stern , James Bottomley , Dan Williams , David Miller , mroos@linux.ee, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, Arjan van de Ven Subject: Re: 3.4.0-02580-g72c04af regression on sparc64 - partitions not recognized In-Reply-To: <201205252127.21436.rjw@sisk.pl> Message-ID: References: <201205252127.21436.rjw@sisk.pl> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1153 Lines: 30 On Fri, 25 May 2012, Rafael J. Wysocki wrote: > On Friday, May 25, 2012, Alan Stern wrote: > > On Fri, 25 May 2012, James Bottomley wrote: > > > > Whether or not the boot kernel can have modular drivers isn't clear to me; > > It can, but then the code in question is irrelevant and the resume has to > be triggered in a different way. For example, by writing to > /sys/power/resume from the initrd boot scripts. > > > I don't know when the check for a valid image in the swap area is carried > > out in relation to starting up the initramfs task. > > This particular one is carried out before the initrd is loaded. I just got hit by this one too, but on x86 qemu. There's no initrd, and all the modules are built in. With commit a7a20d103994fd760766e6c9d494daa569cbfe06 the kernel doesn't get to the point where it reads the partition table. If it's of any help, I can provide more details. Eldad -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/