Gentoo Archives: gentoo-user

From: Valmor de Almeida <val.gentoo@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Internal error: Maps lock 14270464 < unlock 14274560
Date: Wed, 15 Sep 2010 20:06:18
Message-Id: 4C91274B.5090704@gmail.com
In Reply to: Re: [gentoo-user] Internal error: Maps lock 14270464 < unlock 14274560 by Alex Schuster
1 On 09/15/2010 07:40 AM, Alex Schuster wrote:
2 > Valmor de Almeida writes:
3 >
4 >> Filesystem isclean
5 >> * Remounting root filesystem read/write ...
6 >> * Setting up the Logical Volume Manager ...
7 >> Internal error: Maps lock 14270464< unlock 14274560
8 >> Internal error: Maps lock 14274560< unlock 14278656
9 >> Internal error: Maps lock 14278656< unlock 14282752
10 >> Internal error: Maps lock 14282752< unlock 14286848
11 >> Internal error: Maps lock 14286848< unlock 14290944
12 >> * Setting up dm-crypt mappings ...
13 >> [snip]
14 >> Filesystem is clean
15 >>
16 >> I don't find other messages in /var/log/messages. Also the system seems
17 >> to run fine. Has anyone seen these messages? Are they a false positive?
18 >
19 > I had similar errors when doing LVM stuff (while creating shapshots). They
20 > did no harm, and I found some bug report about it saying it's not a big
21 > problem, happing in some recent kernel. I'm running 2.6.35-tuxonice-r1
22 > now, and I no longer have them. But that might also have come from an
23 > update of lvm2.
24 >
25 > Wonko
26 >
27
28 Thanks. Here is what I have at the moment
29
30
31 > emerge --info
32 Portage 2.1.8.3 (default/linux/amd64/10.0/no-multilib, gcc-4.4.3,
33 glibc-2.11.2-r0, 2.6.34-gentoo-r6 x86_64)
34 =================================================================
35 System uname:
36 Linux-2.6.34-gentoo-r6-x86_64-Intel-R-_Core-TM-_i7_CPU_L_640_@_2.13GHz-with-gentoo-1.12.13
37 Timestamp of tree: Sun, 12 Sep 2010 15:45:01 +0000
38
39 Maybe the messages will go away next time I sync and update gentoo.
40
41 --
42 Valmor