linux-kernel - Re: BUG: spinlock trylock failure on UP on CPU#0, vgchange/936

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]

Message-ID: <4F1AB392.20604@kernel.dk>
Date:	Sat, 21 Jan 2012 13:46:10 +0100
From:	Jens Axboe <axboe@...nel.dk>
To:	Christian Kujau <lists@...dbynature.de>
CC:	LKML <linux-kernel@...r.kernel.org>, peterz@...radead.org,
	dm-devel@...hat.com
Subject: Re: BUG: spinlock trylock failure on UP on CPU#0, vgchange/936

On 2012-01-21 12:42, Christian Kujau wrote:
> On Wed, 18 Jan 2012 at 00:18, Christian Kujau wrote:
>> today's git checkout boots fine on powerpc32, but has this message during 
>> bootup:
>>
>> BUG: spinlock trylock failure on UP on CPU#0, vgchange/936
>>  lock: ef32a9f8, .magic: dead4ead, .owner: vgchange/936, .owner_cpu: 0
>> Call Trace:
> 
> Still happening with 3.3.0-rc1.

Can you try and pull:

git://git.kernel.dk/linux-block.git for-linus

and see if it helps?

-- 
Jens Axboe

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