linux-kernel - Re: system gets stuck in a lock during boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 18 Aug 2009 12:49:06 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	"Justin P. Mattock" <justinmattock@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: system gets stuck in a lock during boot

On Thu, Aug 13, 2009 at 08:42:21AM -0700, Justin P. Mattock wrote:
> I posted already and had no reply,
> I cannot boot my system with the latest git
>
> seems to be stuck in some lock:
>
> [   0.655640] [<ffffffff81440c33>] panic+0x84/0x129
> [   0.655883] [<ffffffff81063f96>]  do_exit+0x84/0x67e
> [   0.656125] [<ffffffff81445044>] oops_end+0x9c/0xb7
> [   0.656368] [<ffffffff81044a6c>] no_context+0x200/0x223
> [   0.656611] [<ffffffff81442d3d>] ? __mutex_lock_slowpath+0x226/0x249
> [   0.656848] [<ffffffff81044c36>] __bad_area_nosemaphore+0x1a7/0x1e1
> [   0.657097] [<ffffffff81442b01>]? mutex_unlock+0x1c/0x32
> [   0.657097] [<ffffffff811ce094>] ? inode_doinit_with_dentry+0x533/0x5be
> [   0.657579] [<ffffffff81443ee0>] ? _spin_unlock+0x1c/0x32
> [   0.657822] [<ffffffff81044c91>] bad_area_nosemaphore+0x2a/0x40
> [   0.658066] [<ffffffff811ce149>] ? selinux_d_instantiate+0x2a/0x40
> [   0.658309] [<ffffffff8144687d>] do_page_fault+0x192/0x2dd
> [   0.658549] [<ffffffff814444cf>] page_fault+0x1f/0x30
> [   0.658791] [<ffffffff8120e856>] ? strcmp+0x17/0x46
> [   0.659040] [<ffffffff810b9ca0>] event_create_dir+0x49/0x37b



Ouch...

I've never seen such panic. Could you send me your config, hopefully
I could reproduce it?

Thanks.


> [   0.659276] [<ffffffff81696f0a>] ? event_trace_init+0x0/0x1a2
> [   0.659519] [<ffffffff81697061>] event_trace_init+0x157/0x1a2
> [   0.659762] [<ffffffff81696f0a>] ? event_trace_init+0x0/0x1a2
> [   0.660008] [<ffffffff810091db>] do_one_initcall+0x65/0x14e
> [   0.660251] [<ffffffff81140000>] ? proc_set_super+0x49/0x5d
> [   0.660488] [<ffffffff8167ef53>] kernel_init+0x160/0x1cc
> [   0.660731] [<ffffffff8102801a>] child_rip+0xa/0x20
> [   0.660973] [<ffffffff8167edf3>] ? kernel_init+0x0/0x1cc
> [   0.661220] [<ffffffff81028010>] ? child_rip+0x0/0x20
>
>
>
> seems my other machine boots just fine, maybe this is something
> with x86_64.
>
> Justin P. Mattock
> --
> 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/

--
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/