Hello Okajima,
I'm sorry for the late reply.
Yes I tried this patch and the lock error messages are completely gone.
However, some things went wrong and I can't tell exactly what.
The system boots very slowly and never comes to an end. I inserted some
"sleep"s in the init scripts and changed the LED (my only output device)
before and after the "sleep"s. I could see that the "sleep"s took about
ten times longer than expected. Because everything went so slowly, I had to
bring sshd to the very front of the init script to give it a chance to
start.
I ssh-ed and executed a dmesg but saw nothing abnormal. No error, no
warning.
Could you point out a way to dig out the problem? Thanks!
Guan
On Sat, Jan 19, 2013 at 4:15 AM, <[1]sf...@users.sourceforge.net> wrote:
Guan Xin:
> I tried the patch and the kernel no longer starts. In my configuration,
> when the kernel starts, it turn on an LED; and on entering rdinit, the LED
> blinks. So I can see the kernel is not running because the LED is always
> off. I'm sorry I don't have access to the serial terminal at present and
> cannot see any messages until sshd starts.
I am afraid that tha patch I sent was for linux-3.0. Sorry.
On my local test machine for linux-3.7, I use this.
Try please, but I am not sure whether your system can boot successfully
or not.
J. R. Okajima
References
1. mailto:sf...@users.sourceforge.net
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
