Random thoughts from Jeffrey RSS 2.0
# Sunday, November 08, 2009

Looks like my nice new Intel SR1630HGP server, with its Intel Xeon X3460 processor is affected by the CLOCK_WATCHDOG_TIMEOUT STOP error discussed in KB975530:

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880021e1180, The PRCB address of the hung processor.
Arg4: 0000000000000006, 0.

(additional details follow that but don't really add anything)

GRRRRR!!! Looks like, at the time of this writing, the KB article needs to be updated, since the Xeon 3400 series aren't Xeon 5500's, nor Core i5's, nor Core i7's...

Now playing: The Beatles – One – 26 Let It Be

Sunday, November 08, 2009 02:48:13 UTC  #    Comments [1] -
IT
About the author
Jeffrey Stults
Jeffrey Stults is a software developer currently in Portland, Oregon. He is contactable at:
stultsj@ntldr.net
Archive
<November 2009>
SunMonTueWedThuFriSat
25262728293031
1234567
891011121314
15161718192021
22232425262728
293012345
Disclaimer

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

© Copyright 2012
Jeffrey Stults, Jr.
Statistics
Total Posts: 256
This Year: 0
This Month: 0
This Week: 0
Comments: 23
Utilities
Pick a theme:
Sign In