Re: FUTEX deadlock in ping?

2005-02-24 Thread Jörn Nettingsmeier
Olof Johansson wrote: On Thu, Feb 24, 2005 at 11:14:45AM +0100, Jörn Nettingsmeier wrote: futex(0x401540f4, FUTEX_WAIT, 2, NULL ^^ is this one related to the FUTEX problem olof described? As bert said, it's likely something else. Is the process killable

FUTEX deadlock in ping?

2005-02-24 Thread Jörn Nettingsmeier
hi ! disclaimer: i'm not a kernel guy ;) after reading the FUTEX deadlock thread (http://thread.gmane.org/gmane.linux.kernel/280900), i was wondering: ever since moving to ldap for passwd/group/shadow/hosts lookup, ping to a non-reachable host just freezes up and never returns: spunk:~ # strace

Re: kernel lockup in 2.4.5-ac3 and 2.4.6-pre7 (netfilter ?)

2001-07-19 Thread Jörn Nettingsmeier
uot; which seems to explain why no syslog messages survive. regards, jörn -- Jörn Nettingsmeier home://Kurfürstenstr.49.45138.Essen.Germany phone://+49.201.491621 http://icem-www.folkwang-hochschule.de/~nettings/ http://www.linuxdj.com/audio/lad/ - To unsubscribe from this list: sen

Re: kernel lockup in 2.4.5-ac3 and 2.4.6-pre7 (netfilter ?)

2001-07-19 Thread Jörn Nettingsmeier
[christian, i'm quoting a message of yours below. maybe this is of interest to you, so i'm cc:ing] Thomas wrote: > > Jörn Nettingsmeier wrote: > > > hello brad, hello netfilter people ! > > Brad Chapman wrote: > > > >>Were you able to rescu

Re: [PATCH] fbdev logo (fwd)

2001-05-12 Thread Jörn Nettingsmeier
) CONFIG_FB_LOGO_CIGAR CONFIG_FB_LOGO_MD5 -- Jörn Nettingsmeier home://Kurfürstenstr.49.45138.Essen.Germany phone://+49.201.491621 http://icem-www.folkwang-hochschule.de/~nettings/ http://www.linuxdj.com/audio/lad/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel&qu

2.4.4-pre6 does not compile

2001-04-23 Thread Jörn Nettingsmeier
of pollution was my old .config, which i copied into the tree before making menuconfig. but this has always worked before. regards, jörn (please cc: me, i only read the archives, which have some lag. thanks.) -- Jörn Nettingsmeier home://Kurfürstenstr.49.45138.Essen.Germany phone://+49.201

Re: 8139too.c and 2.4.4-pre1 kernel burp

2001-04-17 Thread Jörn Nettingsmeier
and flood-pinging, and all seems to be well. if you want me to run more specific tests, let me know. thanks, jörn Jeff Garzik wrote: > > Jörn Nettingsmeier wrote: > > > > jeff garzik wrote: > > > > > > Frank Jacobberger wrote: > > > > >

Re: 8139too.c and 2.4.4-pre1 kernel burp

2001-04-13 Thread Jörn Nettingsmeier
Jörn Nettingsmeier wrote: > > i'm seeing this, too. forgot to mention: i'm running 2.4.4-pre2 here. problem persists. -- Jörn Nettingsmeier home://Kurfürstenstr.49.45138.Essen.Germany phone://+49.201.491621 http://www.folkwang-hochschule.de/~nettings/ http://www.l

Re: 8139too.c and 2.4.4-pre1 kernel burp

2001-04-13 Thread Jörn Nettingsmeier
eep me on cc:, as i have only archive access to LKML. thanks. btw, jeff, the old "kernel: eth0: Abnormal interrupt, status 000[2,6]" messages have disappeared since 2.4.3 or so. regards, jörn -- Jörn Nettingsmeier home://Kurfürstenstr.49.45138.Essen.Germany phone://+49.201.

Re: yacc dependency of aic7xxx driver

2001-03-07 Thread Jörn Nettingsmeier
r sent me the following simple workaround: Just create a shell script called yacc with the following content --- #!/bin/sh bison --yacc $* --- i ran into the same problem with a school proiject here yesterday regards, jörn -- Jörn Nettingsmeier home://Kurfürstenstr.49

yacc dependency of aic7xxx driver

2001-03-07 Thread Jörn Nettingsmeier
kernel has not relied on yacc, which is why i'd like to ask you if it's possible to make it work with bison. sorry if this has been dealt with before, but i didn't find anything in the lkml archive. regards, jörn please keep me cc:ed, i'm not on lkml. thanks. -- Jörn Net

video drivers hog pci bus ? [was:[linux-audio-dev] low-latency scheduling patch for 2.4.0]

2001-01-13 Thread Jörn Nettingsmeier
add a > control flag to XF86Config for this. I believe they > have - it's called `PCIRetry'. > > I believe PCIRetry defaults to `off'. This is bad. > It should default to `on'. > > You can read about this minor scandal at the following > URLs: >