[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A7A7C37.7020609@linux.vnet.ibm.com>
Date: Thu, 06 Aug 2009 12:16:15 +0530
From: gowrishankar <gowrishankar.m@...ux.vnet.ibm.com>
To: Clark Williams <williams@...hat.com>
CC: gowrishankar.m@...ux.vnet.ibm.com,
Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
rt-users <linux-rt-users@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>,
Steven Rostedt <rostedt@...dmis.org>,
Peter Zijlstra <peterz@...radead.org>,
Carsten Emde <ce@...g.ch>,
Frank Rowand <frank.rowand@...sony.com>,
Robin Gareus <robin@...eus.org>,
Gregory Haskins <ghaskins@...ell.com>,
Philippe Reynes <philippe.reynes@...smpp.fr>,
Fernando Lopez-Lezcano <nando@...ma.Stanford.EDU>,
Will Schmidt <will_schmidt@...t.ibm.com>,
Darren Hart <dvhltc@...ibm.com>, Jan Blunck <jblunck@...e.de>,
Sven-Thorsten Dietrich <sdietrich@...ell.com>,
Jon Masters <jcm@...hat.com>
Subject: Re: [ANNOUNCE] 2.6.31-rc4-rt1 (problem with CONFIG_SYSFS_DEPRECATED_V2)
Clark Williams wrote:
> On Wed, 05 Aug 2009 11:36:03 +0530
> gowrishankar <gowrishankar.m@...ux.vnet.ibm.com> wrote:
>
>> Thomas Gleixner wrote:
>>> We are pleased to announce the next update to our new preempt-rt
>>> series.
>>>
>>> - update to 2.6.31-rc4
>> Hi,
>> I am seeing below kernel panic on 8 way Intel and 4 way AMD blades.
>>
>> Kernel panic - not syncing: Attempted to kill init!
>> Pid: 1, comm: init Not tainted 2.6.31-rc4-rt1-autotest #1
>> Call Trace:
>> [<ffffffff8104c887>] panic+0xc1/0x171
>> [<ffffffff8104ec9a>] ? put_files_struct+0xc3/0xe6
>> [<ffffffff81394313>] ? rt_write_unlock+0x1c/0x32
>> [<ffffffff810582fd>] ? exit_ptrace+0xab/0x130
>> [<ffffffff81394313>] ? rt_write_unlock+0x1c/0x32
>> [<ffffffff810500af>] do_exit+0x88/0x726
>> [<ffffffff810507d5>] do_group_exit+0x88/0xbb
>> [<ffffffff8105082d>] sys_exit_group+0x25/0x3d
>> [<ffffffff8100be2b>] system_call_fastpath+0x16/0x1b
>>
>> Thanks,
>> Gowri
>
> Gowri,
>
> Would you post your .config so we can see what options you have enabled?
>
Hi Clark,
Thanks for the attention. I just looked at error message before the trace I posted.
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Only if I set CONFIG_SYSFS_DEPRECATED_V2=y, I could successfully boot
which I have tested with this kernel in same system.
Is it not set by default from 2.6.31 onwards ?
Thanks,
Gowri
> Clark
>
--
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/
Powered by blists - more mailing lists