From: Frans Pop <elendil@planet.nl>
To: Tej <bewith.tej@gmail.com>
Subject: Re: [BUG-rc8]: Kernel bootprocess
Date: Wed, 2 Sep 2009 16:36:34 +0200
User-Agent: KMail/1.9.9
Cc: linux-kernel@vger.kernel.org, ebiederm@xmission.com
References: <f1c9d250909020545x90c3610nb75c0716cdf4d440@mail.gmail.com>
In-reply-To: <f1c9d250909020545x90c3610nb75c0716cdf4d440@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200909021636.35796.elendil@planet.nl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1008
Lines: 24

Tej wrote:
> Recently upgraded to 2.6.3-rc8. While doing I could not able to boot,
> and boot process stop at dmesg saying something:
> ADDR_CONF (NETDEV CHANGE): eth0 interface become ready.
> 
> message seems success only but affter pressing alt+ctl+del. machine
> boot without xserver and complete / with readonly filesystem. So I
> couldn't capture whole dmesg.
> 
> Now: I have bisected the problem (twice), and bisect result goes to
> 0db501bd0610ee0c0aca84d927f90bcccd09e2bd is first bad commit
> Author: Eric W. Biederman <ebiederm@xmission.com>
>     inotify: Ensure we alwasy write the terminating NULL.

Can you try with the current git mainline, or current snapshot kernel? 
There have been a couple of inotify fixes committed since rc8.

Cheers,
FJP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/