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: <alpine.DEB.2.01.1201210341430.2895@trent.utfs.org>
Date:	Sat, 21 Jan 2012 03:42:32 -0800 (PST)
From:	Christian Kujau <lists@...dbynature.de>
To:	LKML <linux-kernel@...r.kernel.org>
cc:	peterz@...radead.org, axboe@...nel.dk, dm-devel@...hat.com
Subject: Re: BUG: spinlock trylock failure on UP on CPU#0, vgchange/936

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.

Anyone?

Thanks,
Christian.

> [eed459e0] [c0009de4] show_stack+0x70/0x1bc (unreliable)
> [eed45a20] [c0326da8] spin_dump+0x70/0xe0
> [eed45a30] [c0326f8c] do_raw_spin_trylock+0x58/0x70
> [eed45a40] [c0512b28] _raw_spin_trylock+0x34/0xa0
> [eed45a60] [c02f5510] put_io_context+0xd8/0x184
> [eed45a80] [c0303428] __cfq_slice_expired+0x1e4/0x43c
> [eed45ac0] [c03053d8] cfq_insert_request+0x264/0x5b0
> [eed45ae0] [c02edef4] __elv_add_request+0x1a4/0x2d4
> [eed45af0] [c02f1024] blk_flush_plug_list+0x22c/0x270
> [eed45b20] [c05112dc] io_schedule+0x74/0xec
> [eed45b30] [c0110f88] dio_await_completion+0x60/0xf4
> [eed45b50] [c0112d0c] __blockdev_direct_IO+0x1b80/0x3574
> [eed45d70] [c010f4a4] blkdev_direct_IO+0x54/0x64
> [eed45d90] [c009a424] generic_file_aio_read+0x7b8/0x808
> [eed45e40] [c00d4f68] do_sync_read+0xb8/0x144
> [eed45ef0] [c00d6168] vfs_read+0xcc/0x1c0
> [eed45f10] [c00d6394] sys_read+0x58/0xc8
> [eed45f40] [c00127a0] ret_from_syscall+0x0/0x38
> --- Exception: c01 at 0xfe52b90
>     LR = 0x1003e834
> 
> The system is running fine so far and has before with 3.2.0-rc7, without 
> that warning. The "vgchange" could be the result of some LVM2 initscripts 
> (lvm2-2.02.66-5 are installed on this Debian/stable system), but there are 
> no LVM disks anywhere on the system.
> 
> Full .config & dmesg: http://nerdbynature.de/bits/3.2.0/
> 
> Is this BUG something to worry about?
> 
> Thanks,
> Christian.
> -- 
> BOFH excuse #100:
> 
> IRQ dropout
> --
> 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/
> 

-- 
BOFH excuse #63:

not properly grounded, please bury computer
--
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/