All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <g3vbv@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Strange problem with FUTEX_WAIT_PRIVATE
Date: Thu, 05 Mar 2009 21:34:29 +0000	[thread overview]
Message-ID: <49B04565.2060708@blueyonder.co.uk> (raw)

I don't know if it's a kernel problem, I have already posted to openSUSE
Factory list without any response. It's either an openSUSE problem or
one encountered since about 2.6.29-rc4 I'd guess and through to
2.6.29-rc7-git1.
If I execute certain applications as root I never get the GUI output, as
user everything works as expected.
Below is part of the strace output from "qjackctl". VirtualBox  and
others do the same.
<<<Previous lines deleted>>
stat("/etc/kde4/share/config/oxygenrc", {st_mode=S_IFREG|0644,
st_size=55, ...}) = 0
stat("/etc/kde4/share/config/oxygenrc", {st_mode=S_IFREG|0644,
st_size=55, ...}) = 0
fstat(8, {st_mode=S_IFREG|0644, st_size=55, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x7fba0d1a9000
read(8, "[Windeco]\nBlendTitlebarColors=false\nShowStripes=false\n\n",
4096) = 55
read(8, "", 4096)                       = 0
close(8)                                = 0
munmap(0x7fba0d1a9000, 4096)            = 0
socket(PF_FILE, SOCK_STREAM, 0)         = 8
connect(8, {sa_family=AF_FILE, path=@"/tmp/dbus-8XYkB058j7"}, 23) = 0
fcntl(8, F_GETFL)                       = 0x2 (flags O_RDWR)
fcntl(8, F_SETFL, O_RDWR|O_NONBLOCK)    = 0
fcntl(8, F_GETFD)                       = 0
fcntl(8, F_SETFD, FD_CLOEXEC)           = 0
geteuid()                               = 0
rt_sigaction(SIGPIPE, {0x1, [PIPE], SA_RESTORER|SA_RESTART,
0x7fba0869d6e0}, {SIG_DFL, [], 0}, 8) = 0
poll([{fd=8, events=POLLOUT}], 1, 0)    = 1 ([{fd=8, revents=POLLOUT}])
write(8, "\0", 1)                       = 1
write(8, "AUTH EXTERNAL 30\r\n", 18)    = 18
poll([{fd=8, events=POLLIN}], 1, -1)    = 1 ([{fd=8, revents=POLLIN}])
read(8, "OK 7c5d389345212834a5f2258649afe483\r\n", 2048) = 37
poll([{fd=8, events=POLLOUT}], 1, -1)   = 1 ([{fd=8, revents=POLLOUT}])
write(8, "BEGIN\r\n", 7)                = 7
poll([{fd=8, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=8,
revents=POLLIN|POLLOUT|POLLHUP}])
read(8, "", 2048)                       = 0
close(8)                                = 0
sched_yield()                           = 0
sched_yield()                           = 0
sched_yield()                           = 0
sched_yield()                           = 0
<<< many lines of the same truncated>>>
sched_yield()                           = 0
sched_yield()                           = 0
futex(0x7722ac, FUTEX_WAIT_PRIVATE, 1, NULL

It never moves beyond that point and I have to CTRL-C back to the prompt.
Regards
Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks


             reply	other threads:[~2009-03-05 22:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 21:34 Sid Boyce [this message]
2009-03-06  0:18 ` Strange problem with FUTEX_WAIT_PRIVATE Darren Hart
2009-03-06  2:55   ` Sid Boyce
2009-03-06  3:58     ` Eric Dumazet
     [not found]       ` <49B119CF.8020003@blueyonder.co.uk>
2009-03-06 14:06         ` Eric Dumazet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49B04565.2060708@blueyonder.co.uk \
    --to=g3vbv@blueyonder.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.