On Thu, Mar 07, 2002 at 10:40:07AM +0900, I wrote:
Apparently you have KTR enabled (not the default in GENERIC). I think
WITNESS+KTR already caused nasty recursion from the mtx_lock_spin, and
we now get an endless loop when nanotime() is called with an invalid
timecounter in the
On Wed, Mar 06, 2002 at 08:49:18AM +0100, Poul-Henning Kamp wrote:
In message 20020306054514.GA395@gzl, [EMAIL PROTECTED] writes:
Hello.
After upgrading to the kernel as of 2002-03-03 00:00:00(UTC), it stopped
booting just after the message:
Timecounter i8254 frequency 1193182 Hz
On Wed, 6 Mar 2002, Poul-Henning Kamp wrote:
The only thing I know off right now is this thing from BDE which
I havn't been able to verify yet:
I got the hang for all boots, but it was a local problem. I had added
a nanouptime() call the tc_windup(), and this spins forever when
tc_windup()
On Wed, 6 Mar 2002 [EMAIL PROTECTED] wrote:
I inserted a pair of printf() inside mtx_lock_spin/mtx_unlock_spin in
i8254_get_timecount() and it kept printing the message while tc_init()
was blocked, so I think it's blocked at mtx_lock_spin in i8254_get_timecount()
when called from tc_init(),
On Thu, Mar 07, 2002 at 04:34:00AM +1100, Bruce Evans wrote:
On Wed, 6 Mar 2002 [EMAIL PROTECTED] wrote:
I inserted a pair of printf() inside mtx_lock_spin/mtx_unlock_spin in
i8254_get_timecount() and it kept printing the message while tc_init()
was blocked, so I think it's blocked at
Hello.
After upgrading to the kernel as of 2002-03-03 00:00:00(UTC), it stopped
booting just after the message:
Timecounter i8254 frequency 1193182 Hz
With some debugging printf()'s inserted, I found it was tc-tc_get_timecount()
called from tco_delta() called just after the bcopy() in
The only thing I know off right now is this thing from BDE which
I havn't been able to verify yet:
From:Bruce Evans [EMAIL PROTECTED]
Subject: dummy_timecounter broken; breaks booting with -d
To: [EMAIL
