Re: [-next Jan 18] Boot failure on s390 with DEVTMPFS=y
From: Greg KH
Date: Tue Jan 19 2010 - 16:18:36 EST
On Mon, Jan 18, 2010 at 03:31:09PM +0100, Kay Sievers wrote:
> On Mon, Jan 18, 2010 at 15:21, Sachin Sant <sachinp@xxxxxxxxxx> wrote:
> > Today next (next-20100118) failed to boot on a s390 box
> > with the following Oops :
> > Unable to handle kernel pointer dereference at virtual kernel address
> > 0000000000543000
> > <00000000001eb5da> shmem_fill_super+0x13a/0x25c
> > <0000000000228cfa> get_sb_single+0xbe/0xdc
> > <000000000034ffc0> dev_get_sb+0x2c/0x38
> > <000000000066c602> devtmpfs_init+0x46/0xc0
> > Previous next builds worked fine on the same box. The only difference
> > between configs of the two builds was CONFIG_DEVTMPFS. This option was
> > enabled while compiling 20100118.
> Heiko Carstens posted a simple patch to work around the issue that
> s390 write-protects the string, the option parser tries to modify.
> When Greg has pick it up, this should be fixed.
Yes, I've now queued it up in my trees.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/