linux-kernel - 2.6.23-mm1 s390 driver problem

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071018200148.GA14234@vino.hallyn.com>
Date:	Thu, 18 Oct 2007 15:01:48 -0500
From:	"Serge E. Hallyn" <serge@...lyn.com>
To:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Cc:	cornelia.huck@...ibm.com, heiko.carstens@...ibm.com,
	sam@...nborg.org, schwidefsky@...ibm.com
Subject: 2.6.23-mm1 s390 driver problem

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

Please append a correct "root=" boot option; here are the available partitions:
...
5e0c 7211520 dasdd driver: dasd-eckd
...
5e0e 6949296 dasdd2

Will keep looking at it, but maybe the fix is obvious to someone
in this cc: list?

thanks,
-serge
-
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/