From: Sachin Sant <sachinp@in.ibm.com>
To: Greg KH <greg@kroah.com>, Kay Sievers <kay.sievers@vrfy.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-s390@vger.kernel.org
Subject: [-next Jan 18] Boot failure on s390 with DEVTMPFS=y
Date: Mon, 18 Jan 2010 19:51:47 +0530 [thread overview]
Message-ID: <4B546E7B.2080900@in.ibm.com> (raw)
In-Reply-To: <20100118195743.b45f119e.sfr@canb.auug.org.au>
Today next (next-20100118) failed to boot on a s390 box
with the following Oops :
Brought up 4 CPUs
Unable to handle kernel pointer dereference at virtual kernel address 0000000000543000
Oops: 0004 #1 SMP
Modules linked in:
CPU: 0 Not tainted 2.6.33-rc4-autotest-next-20100118-5-default #1
Process swapper (pid: 1, task: 00000000fd792038, ksp: 00000000fd797a30)
Krnl PSW : 0704200180000000 00000000001eb0b8 (shmem_parse_options+0xc0/0x328)
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:0 CC:2 PM:0 EA:3
Krnl GPRS: 000000000054388a 000000000000003d 0000000000543836 000000000000003d
0000000000000000 0000000000483f28 0000000000536112 00000000fd797d00
00000000fd4ba100 0000000000000100 0000000000483978 0000000000543832
0000000000000000 0000000000465958 00000000001eb0b0 00000000fd797c58
Krnl Code: 00000000001eb0aa: c0e5000994f1 brasl %r14,31da8c
00000000001eb0b0: b9020022 ltgr %r2,%r2
00000000001eb0b4: a784010b brc 8,1eb2ca
>00000000001eb0b8: 92002000 mvi 0(%r2),0
00000000001eb0bc: a7080000 lhi %r0,0
00000000001eb0c0: 41902001 la %r9,1(%r2)
00000000001eb0c4: b9040016 lgr %r1,%r6
00000000001eb0c8: b904002b lgr %r2,%r11
Call Trace:
(<00000000fd797c50> 0xfd797c50)
<00000000001eb5da> shmem_fill_super+0x13a/0x25c
<0000000000228cfa> get_sb_single+0xbe/0xdc
<000000000034ffc0> dev_get_sb+0x2c/0x38
<000000000066c602> devtmpfs_init+0x46/0xc0
<000000000066c53e> driver_init+0x22/0x60
<000000000064d40a> kernel_init+0x24e/0x3d0
<000000000010a7ea> kernel_thread_starter+0x6/0xc
<000000000010a7e4> kernel_thread_starter+0x0/0xc
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.
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2010-01-18 14:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 8:57 linux-next: Tree for January 18 Stephen Rothwell
2010-01-18 14:21 ` Sachin Sant [this message]
2010-01-18 14:31 ` [-next Jan 18] Boot failure on s390 with DEVTMPFS=y Kay Sievers
2010-01-19 21:14 ` Greg KH
2010-01-19 23:49 ` Stephen Rothwell
2010-01-18 23:44 ` linux-next: Tree for January 18 (pci + pm) Randy Dunlap
2010-01-19 23:04 ` Rafael J. Wysocki
2010-01-20 4:39 ` Jesse Barnes
2010-01-20 5:20 ` Stephen Rothwell
2010-01-20 16:53 ` Randy Dunlap
2010-01-28 16:33 ` Randy Dunlap
2010-01-28 19:04 ` Jesse Barnes
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=4B546E7B.2080900@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=greg@kroah.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).