hi,
here are some error messages after reboot in my logs.
Badness in futex_wait at kernel/futex.c:542
Oct 26 03:01:26 h2so4 kernel: ReiserFS: sda1: found reiserfs format "3.6" with
standard journal
Oct 26 03:01:27 h2so4 kernel: ReiserFS: sda1: using ordered data mode
Oct 26 03:01:27 h2so4 kernel: ReiserFS: sda1: journal params: device sda1,
size 8192, journal first block 18, max trans len 1024, max batch 900, max
commit age 30, max trans age 30
Oct 26 03:01:27 h2so4 kernel: ReiserFS: sda1: checking transaction log (sda1)
Oct 26 03:01:27 h2so4 kernel: ReiserFS: sda1: Using r5 hash to sort names
Oct 26 03:14:18 h2so4 kernel: Badness in futex_wait at kernel/futex.c:542
Oct 26 03:14:18 h2so4 kernel: [<c012b5e1>] futex_wait+0x180/0x18a
Oct 26 03:14:18 h2so4 kernel: [<c0115295>] default_wake_function+0x0/0xc
Oct 26 03:14:18 h2so4 kernel: [<c0115295>] default_wake_function+0x0/0xc
Oct 26 03:14:18 h2so4 kernel: [<c010a323>] convert_fxsr_from_user+0x15/0xd8
Oct 26 03:14:18 h2so4 kernel: [<c012b80f>] do_futex+0x35/0x7f
Oct 26 03:14:18 h2so4 kernel: [<c01dba43>] copy_from_user+0x34/0x61
Oct 26 03:14:18 h2so4 kernel: [<c012b939>] sys_futex+0xe0/0xec
Oct 26 03:14:18 h2so4 kernel: [<c0103da5>] sysenter_past_esp+0x52/0x71
Oct 26 03:14:18 h2so4 kernel: Badness in futex_wait at kernel/futex.c:542
Oct 26 03:14:18 h2so4 kernel: [<c012b5e1>] futex_wait+0x180/0x18a
Oct 26 03:14:18 h2so4 kernel: [<c0115295>] default_wake_function+0x0/0xc
Oct 26 03:14:18 h2so4 kernel: [<c0115295>] default_wake_function+0x0/0xc
Oct 26 03:14:18 h2so4 kernel: [<c010a323>] convert_fxsr_from_user+0x15/0xd8
Oct 26 03:14:18 h2so4 kernel: [<c012b80f>] do_futex+0x35/0x7f
Oct 26 03:14:18 h2so4 kernel: [<c01dba43>] copy_from_user+0x34/0x61
Oct 26 03:14:18 h2so4 kernel: [<c012b939>] sys_futex+0xe0/0xec
Oct 26 03:14:18 h2so4 kernel: [<c0103da5>] sysenter_past_esp+0x52/0x71
Oct 26 03:14:21 h2so4 init: Switching to runlevel: 0
Oct 26 03:14:25 h2so4 rpc.statd[10128]: Caught signal 15, un-registering and
exiting.
Oct 26 03:14:26 h2so4 kernel: Kernel logging (proc) stopped.
Oct 26 03:14:26 h2so4 kernel: Kernel log daemon terminating.
Oct 26 03:14:28 h2so4 exiting on signal 15
Oct 26 10:10:17 h2so4 syslogd 1.4.1: restart.
--
Michael Geithe
On Tue, 26 Oct 2004 11:35:50 +0200
Michael Geithe <[email protected]> wrote:
> hi,
> here are some error messages after reboot in my logs.
>
> Badness in futex_wait at kernel/futex.c:542
Hey Ingo,
this futex.c:542 looks familiar to me (see the BUG logs for RP-V0.2). Dunno
if it's coincidence though. Just guessing they might be correlated.
>
> Oct 26 03:01:26 h2so4 kernel: ReiserFS: sda1: found reiserfs format "3.6" with
> standard journal
> Oct 26 03:01:27 h2so4 kernel: ReiserFS: sda1: using ordered data mode
> Oct 26 03:01:27 h2so4 kernel: ReiserFS: sda1: journal params: device sda1,
> size 8192, journal first block 18, max trans len 1024, max batch 900, max
> commit age 30, max trans age 30
> Oct 26 03:01:27 h2so4 kernel: ReiserFS: sda1: checking transaction log (sda1)
> Oct 26 03:01:27 h2so4 kernel: ReiserFS: sda1: Using r5 hash to sort names
> Oct 26 03:14:18 h2so4 kernel: Badness in futex_wait at kernel/futex.c:542
> Oct 26 03:14:18 h2so4 kernel: [<c012b5e1>] futex_wait+0x180/0x18a
> Oct 26 03:14:18 h2so4 kernel: [<c0115295>] default_wake_function+0x0/0xc
> Oct 26 03:14:18 h2so4 kernel: [<c0115295>] default_wake_function+0x0/0xc
> Oct 26 03:14:18 h2so4 kernel: [<c010a323>] convert_fxsr_from_user+0x15/0xd8
> Oct 26 03:14:18 h2so4 kernel: [<c012b80f>] do_futex+0x35/0x7f
> Oct 26 03:14:18 h2so4 kernel: [<c01dba43>] copy_from_user+0x34/0x61
> Oct 26 03:14:18 h2so4 kernel: [<c012b939>] sys_futex+0xe0/0xec
> Oct 26 03:14:18 h2so4 kernel: [<c0103da5>] sysenter_past_esp+0x52/0x71
> Oct 26 03:14:18 h2so4 kernel: Badness in futex_wait at kernel/futex.c:542
> Oct 26 03:14:18 h2so4 kernel: [<c012b5e1>] futex_wait+0x180/0x18a
> Oct 26 03:14:18 h2so4 kernel: [<c0115295>] default_wake_function+0x0/0xc
> Oct 26 03:14:18 h2so4 kernel: [<c0115295>] default_wake_function+0x0/0xc
> Oct 26 03:14:18 h2so4 kernel: [<c010a323>] convert_fxsr_from_user+0x15/0xd8
> Oct 26 03:14:18 h2so4 kernel: [<c012b80f>] do_futex+0x35/0x7f
> Oct 26 03:14:18 h2so4 kernel: [<c01dba43>] copy_from_user+0x34/0x61
> Oct 26 03:14:18 h2so4 kernel: [<c012b939>] sys_futex+0xe0/0xec
> Oct 26 03:14:18 h2so4 kernel: [<c0103da5>] sysenter_past_esp+0x52/0x71
> Oct 26 03:14:21 h2so4 init: Switching to runlevel: 0
> Oct 26 03:14:25 h2so4 rpc.statd[10128]: Caught signal 15, un-registering and
> exiting.
> Oct 26 03:14:26 h2so4 kernel: Kernel logging (proc) stopped.
> Oct 26 03:14:26 h2so4 kernel: Kernel log daemon terminating.
> Oct 26 03:14:28 h2so4 exiting on signal 15
> Oct 26 10:10:17 h2so4 syslogd 1.4.1: restart.
* Florian Schmidt <[email protected]> wrote:
> On Tue, 26 Oct 2004 11:35:50 +0200
> Michael Geithe <[email protected]> wrote:
>
> > hi,
> > here are some error messages after reboot in my logs.
> >
> > Badness in futex_wait at kernel/futex.c:542
>
> Hey Ingo,
>
> this futex.c:542 looks familiar to me (see the BUG logs for RP-V0.2). Dunno
> if it's coincidence though. Just guessing they might be correlated.
yeah, it definitely looks like there is some futex race that the
PREEMPT_REALTIME kernel triggers in no time. (this is because the
locking in the PREEMPT_REALTIME kernel is equivalent to an SMP system
with an infinite number of CPUs and will trigger the same races.)
Ingo
Hi,
first config with > e100
Oct 26 10:57:33 h2so4 kernel: e100: Intel(R) PRO/100 Network Driver,
3.2.3-k2-NAPI
Oct 26 10:57:33 h2so4 kernel: e100: Copyright(c) 1999-2004 Intel Corporation
Oct 26 11:02:19 h2so4 kernel: Badness in futex_wait at kernel/futex.c:542
Oct 26 11:02:19 h2so4 kernel: [<c012ba15>] futex_wait+0x180/0x18a
Oct 26 11:02:19 h2so4 kernel: [<c011532c>] default_wake_function+0x0/0xc
Oct 26 11:02:19 h2so4 kernel: [<c011532c>] default_wake_function+0x0/0xc
Oct 26 11:02:19 h2so4 kernel: [<c010a323>] convert_fxsr_from_user+0x15/0xd8
Oct 26 11:02:19 h2so4 kernel: [<c012bc43>] do_futex+0x35/0x7f
Oct 26 11:02:19 h2so4 kernel: [<c01dbd77>] copy_from_user+0x34/0x61
Oct 26 11:02:19 h2so4 kernel: [<c012bd6d>] sys_futex+0xe0/0xec
Oct 26 11:02:19 h2so4 kernel: [<c0103da5>] sysenter_past_esp+0x52/0x71
and second config with > eepro100
Oct 26 13:12:25 h2so4 kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://www.scyld.com/network/eepro100.html
Oct 26 13:12:25 h2so4 kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17
Modified by Andrey V. Savochkin <[email protected]> and others
and i dont see this message again.
--
Michael Geithe
-
Michael Geithe wrote:
> Hi,
>
> first config with > e100
>
> Oct 26 10:57:33 h2so4 kernel: e100: Intel(R) PRO/100 Network Driver,
> 3.2.3-k2-NAPI
> Oct 26 10:57:33 h2so4 kernel: e100: Copyright(c) 1999-2004 Intel Corporation
>
> Oct 26 11:02:19 h2so4 kernel: Badness in futex_wait at kernel/futex.c:542
> Oct 26 11:02:19 h2so4 kernel: [<c012ba15>] futex_wait+0x180/0x18a
> Oct 26 11:02:19 h2so4 kernel: [<c011532c>] default_wake_function+0x0/0xc
> Oct 26 11:02:19 h2so4 kernel: [<c011532c>] default_wake_function+0x0/0xc
> Oct 26 11:02:19 h2so4 kernel: [<c010a323>] convert_fxsr_from_user+0x15/0xd8
> Oct 26 11:02:19 h2so4 kernel: [<c012bc43>] do_futex+0x35/0x7f
> Oct 26 11:02:19 h2so4 kernel: [<c01dbd77>] copy_from_user+0x34/0x61
> Oct 26 11:02:19 h2so4 kernel: [<c012bd6d>] sys_futex+0xe0/0xec
> Oct 26 11:02:19 h2so4 kernel: [<c0103da5>] sysenter_past_esp+0x52/0x71
>
> and second config with > eepro100
>
> Oct 26 13:12:25 h2so4 kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
> http://www.scyld.com/network/eepro100.html
> Oct 26 13:12:25 h2so4 kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17
> Modified by Andrey V. Savochkin <[email protected]> and others
>
> and i dont see this message again.
>
Hi,
Can you try the following patch and see what it says?
Ingo Molnar wrote:
> yeah, it definitely looks like there is some futex race that the
> PREEMPT_REALTIME kernel triggers in no time. (this is because the
> locking in the PREEMPT_REALTIME kernel is equivalent to an SMP system
> with an infinite number of CPUs and will trigger the same races.)
>
> Ingo
That's an interesting claim. I don't understand why it is equivalent.
Could you please explain it?
Michal
* Nick Piggin <[email protected]> wrote:
> >Oct 26 11:02:19 h2so4 kernel: Badness in futex_wait at kernel/futex.c:542
> Hi,
> Can you try the following patch and see what it says?
i found the bug that most likely caused the PREEMPT_REALTIME one
reported by Florian - it was a spurious wakeup caused by that patch, so
upstream is not affected.
Ingo