[lkml]   [2012]   [Jan]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: dmsetup fails on latest kernel
On Thu, Jan 19, 2012 at 7:56 AM, Kasatkin, Dmitry
<> wrote:
> On Thu, Jan 19, 2012 at 3:02 PM, Kasatkin, Dmitry
> <> wrote:
>> Hi,
>> (subject added)
>> I rebased on the stop of latest mainline tree and now dmsetup fails...
>> It says: "Failed to create notification semaphore: Function not implemented".
>> I run strace and saw that dmsetup uses "semget" which returns -ENOSYS...
>> It works on
>> 122804ecb59493fbb4d31b3ba9ac59faaf45276f
>> but does not work on
>> ccb19d263fd1c9e34948e2158c53eacbff369344
>> Any ideas?
>> - Dmitry
> Hi,
> I have bisected the problem...
> It is introduced by this commit:
> 303395ac3bf3e2cb488435537d416bc840438fcb is the first bad commit
> commit 303395ac3bf3e2cb488435537d416bc840438fcb
> Author: H. Peter Anvin <>
> Date:   Fri Nov 11 16:07:41 2011 -0800
>    x86: Generate system call tables and unistd_*.h from tables

Interesting. I just munged the old pre-merge


and the new


with some trivial shell scripting, and they are definitely identical.

So the tables look like they match 1:1.

The compat tables match too, except the new list contains the entry
for bdflush (134), but that's a legacy thing that doesn't matter.

I wonder what else could be going on. Wrong number of system calls
check? Peter, any ideas?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2012-01-19 20:09    [W:0.081 / U:13.616 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site