-Original Message-
From: M. Warner Losh [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 27, 2006 9:39 PM
To: Michael Scheidell
Cc: freebsd-hackers@freebsd.org
Subject: Re: FBSD 5.5 and software timers
libc_r depends on absolute system time to do its sleeps and
timeouts, and has
In message: [EMAIL PROTECTED]
Michael Scheidell [EMAIL PROTECTED] writes:
: -Original Message-
: From: M. Warner Losh [mailto:[EMAIL PROTECTED]
: Sent: Thursday, July 27, 2006 9:39 PM
: To: Michael Scheidell
: Cc: freebsd-hackers@freebsd.org
: Subject: Re: FBSD 5.5
-hackers@freebsd.org
: Subject: Re: FBSD 5.5 and software timers
:
snip
: I am going to try to nail down just what and why this happens and
: post that.
: (reminder: even if this change happened in 3.4, it didn't affect me
: till 5.5)
It might be useful to find the change.
There was a fix
M. Warner Losh wrote:
:
: I replaced libc_r with libpthread and it immediately reboots the system!
Neither of these is good! Does it happen on 6?
Don't know, I had enough trouble going from 5.4 to 5.5 :-(
6.x might not even run on my hardware.
: I am going to try to nail down just
In message: [EMAIL PROTECTED]
Michael Scheidell [EMAIL PROTECTED] writes:
: Found it! library libc_r
:
: Given POC:
:
: int main( int argc, char **argv )
: {
: char execs1[256] = /bin/date +A%Y%m%d%H%M.%S;
: char execs2[256] = /bin/date +B%Y%m%d%H%M.%S;
: int a;
:
: while ( 1) {
On Mon, 2006-Jul-24 11:47:41 -0400, Michael Scheidell wrote:
This software timer was resetting a 1 second hardware watchdog timer.
Every 200ms, I sent a reset to the hardware WDT.
Everything worked on 5.4, but I am getting failures on 5.5
Basically, when you ask for a 200msec delay, the kernel
-Original Message-
From: Peter Jeremy [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 25, 2006 4:00 AM
To: Michael Scheidell
Cc: freebsd-hackers@freebsd.org
Subject: Re: FBSD 5.5 and software timers
Basically, when you ask for a 200msec delay, the kernel
sleeps until
-Original Message-
From: Steve Watt [mailto:[EMAIL PROTECTED]
Sent: Monday, July 24, 2006 6:28 PM
To: Michael Scheidell
Cc: [EMAIL PROTECTED]
Subject: Re: FBSD 5.5 and software timers
It sounds like ntpd isn't really synchronizing. If you keep
an eye on associations (my finger
In message: [EMAIL PROTECTED]
Peter Jeremy [EMAIL PROTECTED] writes:
: On Mon, 2006-Jul-24 11:47:41 -0400, Michael Scheidell wrote:
: This software timer was resetting a 1 second hardware watchdog timer.
: Every 200ms, I sent a reset to the hardware WDT.
: Everything worked on 5.4, but
In message: [EMAIL PROTECTED]
Michael Scheidell [EMAIL PROTECTED] writes:
: -Original Message-
: From: Peter Jeremy [mailto:[EMAIL PROTECTED]
: Sent: Tuesday, July 25, 2006 4:00 AM
: To: Michael Scheidell
: Cc: freebsd-hackers@freebsd.org
: Subject: Re: FBSD 5.5
M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Michael Scheidell [EMAIL PROTECTED] writes:
: I presume the servers are all stable (ie not stepping) and
: have a reasonably low delay. If so, I suspect your ntpd PLL
: has locked up. I've seen problems with some versions of
Tim Kientzle wrote:
M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Michael Scheidell [EMAIL PROTECTED] writes:
: I presume the servers are all stable (ie not stepping) and :
have a reasonably low delay. If so, I suspect your ntpd PLL : has
locked up. I've seen problems
Found it! library libc_r
Given POC:
int main( int argc, char **argv )
{
char execs1[256] = /bin/date +A%Y%m%d%H%M.%S;
char execs2[256] = /bin/date +B%Y%m%d%H%M.%S;
int a;
while ( 1) {
system( execs1 );
usleep( 500*1000);
system( execs2 );
}
return 0;
} /* main */
compile
I had a 200ms software timer running in FBSD 5.4 that isn't working in
5.5 now.
This software timer was resetting a 1 second hardware watchdog timer.
Every 200ms, I sent a reset to the hardware WDT.
Everything worked on 5.4, but I am getting failures on 5.5
It appears that something changed in
Michael Scheidell wrote:
I had a 200ms software timer running in FBSD 5.4 that isn't working in
5.5 now.
This software timer was resetting a 1 second hardware watchdog timer.
Every 200ms, I sent a reset to the hardware WDT.
Everything worked on 5.4, but I am getting failures on 5.5
It appears
15 matches
Mail list logo