public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, cornelia.huck@de.ibm.com,
	heiko.carstens@de.ibm.com, sam@ravnborg.org
Subject: Re: 2.6.23-mm1 s390 driver problem
Date: Fri, 19 Oct 2007 09:47:16 +0200	[thread overview]
Message-ID: <1192780036.25150.7.camel@localhost> (raw)
In-Reply-To: <20071018203151.GA15382@vino.hallyn.com>

On Thu, 2007-10-18 at 15:31 -0500, Serge E. Hallyn wrote:
> Quoting Christian Borntraeger (borntraeger@de.ibm.com):
> > Am Donnerstag, 18. Oktober 2007 schrieb Serge E. Hallyn:
> > > Sigh, well this turned out less informative than I'd liked.
> > > After bisecting 2.6.23 to 2.6.23-mm1, I found that
> > > git-s390.patch is the one breaking my s390 boot :(
> > > (Frown bc it's a conglomeration of patches0
> > > 
> > > Symptom is:
> > > 	"Cannot open root device "dasdd2" or unknown-block(94,14)"
> > > even though dasdd2 appeared to be found earlier in the boot.  I also
> > > get
> > 
> > Can you post the full console output from IPL to the unsuccessful end?
> 
> Yeah, sorry, appended below.
> 
> I had thought that the line
> 	sysctl table check failed: /sunrpc/transports .7249.14 Missing strategy
> meant that the fix referenced in http://lkml.org/lkml/2007/10/11/48
> would fix it, but it appeared to have no effect.

This is the vmlinux.lds.S problem. The cleanup patch from Sam Ravnborg
moved the __initramfs_start and __initramfs_end symbols into
the .init.ramfs section. This is in itself not a problem, but it
surfaced a bug: there is no *(.init.initramfs), that needs to be
*(init.ramfs). I corrected this in the upstream patch but 2.6.23-mm1 has
the older one that still causes the "Cannot open root device". For
2.6.23-mm1 use the patch below.

-- 
blue skies,
  Martin.

"Reality continues to ruin my life." - Calvin.

---
diff -urpN linux-2.6/arch/s390/kernel/vmlinux.lds.S linux-2.6-patched/arch/s390/kernel/vmlinux.lds.S
--- linux-2.6/arch/s390/kernel/vmlinux.lds.S	2007-10-19 09:41:57.000000000 +0200
+++ linux-2.6-patched/arch/s390/kernel/vmlinux.lds.S	2007-10-19 09:42:29.000000000 +0200
@@ -128,7 +128,7 @@ SECTIONS
 	. = ALIGN(0x100);
 	.init.ramfs : {
 		__initramfs_start = .;
-		*(.init.initramfs)
+		*(.init.ramfs)
 		. = ALIGN(2);
 		__initramfs_end = .;
 	}



  reply	other threads:[~2007-10-19  7:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 20:01 2.6.23-mm1 s390 driver problem Serge E. Hallyn
2007-10-18 20:15 ` Christian Borntraeger
2007-10-18 20:31   ` Serge E. Hallyn
2007-10-19  7:47     ` Martin Schwidefsky [this message]
2007-10-19  9:16       ` Cedric Le Goater
2007-10-19  9:20         ` Martin Schwidefsky
2007-10-19 11:06           ` Cedric Le Goater
2007-10-19  9:27         ` Andrew Morton
2007-10-19 11:17           ` Cedric Le Goater
2007-10-19 11:25             ` Martin Schwidefsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1192780036.25150.7.camel@localhost \
    --to=schwidefsky@de.ibm.com \
    --cc=akpm@osdl.org \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=serge@hallyn.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox