Re: port-alpha/38335 (kernel freeze on alpha MP system)

[Jarle Greipsland <jarle%uninett.no@localhost>]

The following reply was made to PR port-alpha/38335; it has been noted by GNATS.

From: Jarle Greipsland <jarle%uninett.no@localhost>
To: gnats-bugs%NetBSD.org@localhost, dholland%NetBSD.org@localhost
Cc: port-alpha-maintainer%netbsd.org@localhost, 
netbsd-bugs%netbsd.org@localhost,
        gnats-admin%netbsd.org@localhost
Subject: Re: port-alpha/38335 (kernel freeze on alpha MP system)
Date: Tue, 22 Sep 2009 19:00:07 +0200 (CEST)

 dholland%NetBSD.org@localhost writes:
 > Synopsis: kernel freeze on alpha MP system
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: dholland%NetBSD.org@localhost
 > State-Changed-When: Sat, 19 Sep 2009 21:51:28 +0000
 > State-Changed-Why:
 > A bunch of MP alpha fixes just went into -current; might want to give them a
 > try.
 The problem is still there.  I installed and booted GENERIC.MP,
 and built a full release.  During extraction of the newly built
 sets, the system wedged again.  This time I could not break into
 DDB from the console.
 
 I power-cycled the system, and started to extract the sets again.
 During extraction I noticed that the IO performance through the
 file system seemed abyssmal (according to 'systat vm').  The 'tar
 zxBpf' command consumed almost no CPU, but the disk IO hovered
 around 500KB/s.  Doing a plain dd from/to a single file on the
 same disk gets around 20-30MB/s.
 
 Also, right after root file system detection, the kernel complains:
 
 WARNING: negative runtime; monotonic clock has gone backwards
 
 I don't know if this might be related to the wedging or not.
 
 If you want me to dig out more information, please ask, and I'll
 see what I can do.
                                        -jarle