linux-kernel - Re: [linux-usb-devel] 2.6.20-rc5: BUG: lock held at task exit time! (pm_mutex){--..}, at: [<c013bfff>] enter

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, 16 Jan 2007 15:31:10 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Andrey Borzenkov <arvidjaar@...l.ru>
cc:	linux-usb-devel@...ts.sourceforge.net,
	<linux-kernel@...r.kernel.org>
Subject: Re: [linux-usb-devel] 2.6.20-rc5: BUG: lock held at task exit time!
 (pm_mutex){--..}, at: [<c013bfff>] enter_state+0x3f/0x170

On Tue, 16 Jan 2007, Andrey Borzenkov wrote:

> I have Toshiba Portege 4000 that almost always hangs dead resuming from STR. 
> This was better before 2.6.18, since then STR is unusable. Sometimes it 
> manages to resume; yesterday I got on console and in dmesg:
> 
> =====================================
> [ BUG: lock held at task exit time! ]
> - -------------------------------------
> echo/28793 is exiting with locks still held!
> 1 lock held by echo/28793:
>  #0:  (pm_mutex){--..}, at: [<c013bfff>] enter_state+0x3f/0x170
> 
> stack backtrace:
>  [<c0103fea>] show_trace_log_lvl+0x1a/0x30
>  [<c01045f2>] show_trace+0x12/0x20
>  [<c01046a6>] dump_stack+0x16/0x20
>  [<c0132377>] debug_check_no_locks_held+0x87/0x90
>  [<c011c8bb>] do_exit+0x4db/0x820
>  [<c011cc29>] do_group_exit+0x29/0x70
>  [<c011cc7f>] sys_exit_group+0xf/0x20
>  [<c010300e>] sysenter_past_esp+0x5f/0x99
>  =======================

Have you tried using 2.6.19?  There was a bug which got fixed in that 
release.

Alan Stern

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