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]

Date:	Sat, 21 Jan 2012 14:35:18 -0800 (PST)
From:	Christian Kujau <lists@...dbynature.de>
To:	Jens Axboe <axboe@...nel.dk>
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 Sat, 21 Jan 2012 at 13:46, Jens Axboe wrote:
> Can you try and pull:
> 
> git://git.kernel.dk/linux-block.git for-linus
> 
> and see if it helps?

Pulled, compiled, bootet - but the BUG: stays. Please see .config and full 
dmesg: http://nerdbynature.de/bits/3.2.0/   (the 3.3.0-rc1 files)

Note that I don't have an actual problem here: the machine (PowerBook G4) 
is booting & running fine, I'm currently not using any LVM devices, so 
it's merely the BUG: being printed during bootup I'm whining about.

Thanks,
Christian.
-- 
BOFH excuse #292:

We ran out of dial tone and we're and waiting for the phone company to deliver another bottle.
--
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/