An open community 
of Macintosh users,
for Macintosh users.

FineTunedMac Dashboard widget now available! Download Here

Previous Thread
Next Thread
Print Thread
Mysterious restarts
#65737 02/22/24 08:18 PM
Joined: Aug 2009
Likes: 15
OP Online

Joined: Aug 2009
Likes: 15
I've awakened twice in the past couple of weeks to pop-ups advising me that my MBP had restarted while I was asleep. The occurrences having happened while I was asleep - Music was running white noise and Safari was running in the background - leaves me clueless as to what might have triggered them.

I've booted into Recovery and run First Aid, but everything's come up roses.

I can't make heads or tails of the "panic" reports, but maybe someone else can:

Code
panic(cpu 4 caller 0xffffff801e89189b): userspace watchdog timeout: no successful checkins from WindowServer (2 induced crashes) in 120 seconds
WindowServer has not exited since first loaded
service: logd, total successful checkins in 115335 seconds: 11534, last successful checkin: 0 seconds ago
service: WindowServer (2 induced crashes), total successful checkins in 115302 seconds: 11518, last successful checkin: 120 seconds ago
service: remoted, total successful checkins in 115335 seconds: 11532, last successful checkin: 0 seconds ago
service: opendirectoryd, total successful checkins in 115335 seconds: 11533, last successful checkin: 0 seconds ago
service: configd, total successful checkins in 115335 seconds: 11534, last successful checkin: 0 seconds ago

Panicked task 0xffffff8b7499cdf8: 3 threads: pid 113: watchdogd
Backtrace (CPU 4), panicked thread: 0xffffff8b74d460c8, Frame : Return Address
0xffffffedbca9f510 : 0xffffff801bc36c41 
0xffffffedbca9f560 : 0xffffff801bd955c0 
0xffffffedbca9f5a0 : 0xffffff801bd84d0c 
0xffffffedbca9f620 : 0xffffff801bbd3971 
0xffffffedbca9f640 : 0xffffff801bc36f2d 
0xffffffedbca9f730 : 0xffffff801bc365d3 
0xffffffedbca9f790 : 0xffffff801c3d8e6e 
0xffffffedbca9f880 : 0xffffff801e89189b 
0xffffffedbca9f890 : 0xffffff801e891364 
0xffffffedbca9f8b0 : 0xffffff801e89042b 
0xffffffedbca9f9e0 : 0xffffff801c34e4d6 
0xffffffedbca9fa10 : 0xffffff801c34e84d 
0xffffffedbca9fb80 : 0xffffff801bd4077f 
0xffffffedbca9fca0 : 0xffffff801bc0f8a0 
0xffffffedbca9fd60 : 0xffffff801bc276b8 
0xffffffedbca9fdd0 : 0xffffff801bc27d28 
0xffffffedbca9fef0 : 0xffffff801bd6a302 
0xffffffedbca9ffa0 : 0xffffff801bbd3dd6 
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[F1797B78-7645-3FC6-AD29-624DD0826DA0]@0xffffff801e88f000->0xffffff801e891fff

Process name corresponding to current thread (0xffffff8b74d460c8): watchdogd

Mac OS version:
23D60

Kernel version:
Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58 PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64
Kernel UUID: 8C96896D-43A3-3BF0-8F4C-4118DA6AC9AA
roots installed: 0
KernelCache slide: 0x000000001b800000
KernelCache base:  0xffffff801ba00000
Kernel slide:      0x000000001b8e0000
Kernel text base:  0xffffff801bae0000
__HIB  text base: 0xffffff801b900000
System model name: MacBookPro16,1 (Mac-E1008331FDC96864)
System shutdown begun: NO
Hibernation exit count: 0

System uptime in nanoseconds: 115335548765536
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000068e5a66a0a9f
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x000000066e070ed8 0x0000000000000000
Compressor Info: 6% of compressed pages limit (OK) and 5% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
  Zone map: 0xffffff8040b0f000 - 0xffffffa040b0f000
  . PGZ   : 0xffffff8040b0f000 - 0xffffff8042b10000
  . VM    : 0xffffff8042b10000 - 0xffffff850f30f000
  . RO    : 0xffffff850f30f000 - 0xffffff86a8b0f000
  . GEN0  : 0xffffff86a8b0f000 - 0xffffff8b7530f000
  . GEN1  : 0xffffff8b7530f000 - 0xffffff9041b0f000
  . GEN2  : 0xffffff9041b0f000 - 0xffffff950e30f000
  . GEN3  : 0xffffff950e30f000 - 0xffffff99dab0f000
  . DATA  : 0xffffff99dab0f000 - 0xffffffa040b0f000
  Metadata: 0xffffffffdcfee000 - 0xfffffffffcfee000
  Bitmaps : 0xfffffffffcfee000 - 0xfffffffffffee000
  Extra   : 0 - 0

last started kext at 6339687245: >!AHIDKeyboard	7400.2 (addr 0xffffff801d0f4000, size 20480)
last stopped kext at 114494892603152: @UVCService	1 (addr 0xffffff7fb0de3000, size 4096)
loaded kexts:
com.binaryfruit.driver.SATSMARTDriver	0.10.3
>!AHIDALSService	1
>!ATopCaseHIDEventDriver	7430.5
>!APlatformEnabler	2.7.0d0
>AGPM	135
>X86PlatformShim	1.0.0
@filesystems.autofs	3.0
@kext.AMDRadeonX6000	5.0.2
@kext.AMDRadeonServiceManager	5.0.2
>!AUpstreamUserClient	3.6.11
>!AGraphicsDevicePolicy	8.1.9
@AGDCPluginDisplayMetrics	8.1.9
>pmtelemetry	1
@filesystems.nfs	1
|IOUserEthernet	1.0.1
>usb.!UUserHCI	1
>!ASunrise	1
>!AHV	1
>!AGFXHDA	300.1
>!A!IKBLGraphics	22.0.1
>!A!ISlowAdaptiveClocking	4.0.0
>!AMuxControl2	8.1.9
>!ABridgeAudio!C	400.1
>AGDCBacklightControl	8.1.9
>BridgeAudioCommunication	400.1
>!AMCCSControl	1.17
>!AAVEBridge	6.1
>!A!IPCHPMC	2.0.1
>!A!ICFLGraphicsFramebuffer	22.0.1
>!AThunderboltIP	4.0.3
|SCSITaskUserClient	492
>!UMass!SInterfaceNub	556
>BCMWLANFirmware4388.Hashstore	1
>BCMWLANFirmware4387.Hashstore	1
>BCMWLANFirmware4378.Hashstore	1
>BCMWLANFirmware4377.Hashstore	1
>BCMWLANFirmware4364.Hashstore	1
>BCMWLANFirmware4355.Hashstore	1
>!AFileSystemDriver	3.0.1
@filesystems.tmpfs	1
@filesystems.lifs	1
@filesystems.hfs.kext	650.0.2
@BootCache	40
@!AFSCompression.!AFSCompressionTypeZlib	1.0.0
@!AFSCompression.!AFSCompressionTypeDataless	1.0.0d1
@filesystems.apfs	2235.80.4
>!ABCMWLANBusInterfacePCIeMac	1
@private.KextAudit	1.0
>!ASmartBatteryManager	161.0.0
>!AACPIButtons	6.1
>!ASMBIOS	2.1
>!AACPIEC	6.1
>!AAPIC	1.7
@!ASystemPolicy	2.0.0
@nke.applicationfirewall	404
|IOKitRegistryCompatibility	1
|EndpointSecurity	1
@Dont_Steal_Mac_OS_X	7.0.0
>!ADiskImages2	273
@kec.!AEncryptedArchive	1
>!AHIDKeyboard	7400.2
>!AHS!BDriver	7430.5
>IO!BHIDDriver	9.0.0
>!AActuatorDriver	7430.5
>!AMultitouchDriver	7430.5
>!AInputDeviceSupport	7410.1
@kext.AMDRadeonX6100HWLibs	1.0
@kext.AMDRadeonX6000HWServices	5.0.2
>!AAudioClockLibs	300.1
@kext.triggers	1.0
>IOHIDPowerSource	1
>!ACallbackPowerSource	1
|IOAVB!F	1220.1
>!ARSMChannel	1
|IORSM!F	1
>!AIPAppender	1.0
>!A!ILpssUARTv1	3.0.60
>!A!ILpssUARTCommon	3.0.60
>!AOnboardSerial	1.0
@!AGPUWrangler	8.1.9
|IOSlowAdaptiveClocking!F	1.0.0
>!AGraphicsControl	8.1.9
|IOAudio!F	500.4
@vecLib.kext	1.2.0
@kext.AMDRadeonX6000Framebuffer	5.0.2
@kext.AMDSupport	5.0.2
>!ABacklightExpert	1.1.0
|IONDRVSupport	598
>!ASMBus!C	1.0.18d1
|IOAccelerator!F2	481.0.1
@!AGraphicsDeviceControl	8.1.9
|IOGraphics!F	598
@plugin.IOgPTPPlugin	1230.2
>X86PlatformPlugin	1.0.0
>IOPlatformPlugin!F	6.0.0d8
>!AThunderboltDPOutAdapter	8.5.1
>driverkit.serial	6.0.0
>usb.IOUSBHostHIDDevice	1.2
>usb.cdc.ecm	5.0.0
>usb.cdc.ncm	5.0.0
>usb.cdc	5.0.0
>usb.networking	5.0.0
>usb.!UHostCompositeDevice	1.2
>!AThunderboltPCIDownAdapter	4.1.1
>!AThunderboltDPInAdapter	8.5.1
>!AThunderboltDPAdapter!F	8.5.1
>!AHPM	3.4.4
>!A!ILpssI2C!C	3.0.60
>!A!ILpssI2C	3.0.60
>!A!ILpssDmac	3.0.60
>!ABSDKextStarter	3
|IOSurface	352.0.3
@filesystems.hfs.encodings.kext	1
>!ASyntheticGame!C	11.3.1
>!AThunderboltNHI	7.2.81
|IOThunderbolt!F	9.3.3
>!AXsanScheme	3
>usb.!UVHCIBCE	1.2
>usb.!UVHCICommonBCE	1.0
>usb.!UVHCI	1.2
>usb.!UVHCICommon	1.0
>!AEffaceableNOR	1.0
|IOBufferCopy!C	1.1.0
|IOBufferCopyEngine!F	1
|IONVMe!F	2.1.0
>!ABCMWLANCoreMac	1.0.0
|IO80211!F	1200.13.0
>IOImageLoader	1.0.0
>!AOLYHALMac	1
|IOSerial!F	11
>corecapture	1.0.4
>usb.!UHostPacketFilter	1.0
|IOUSB!F	900.4.2
>usb.!UXHCIPCI	1.2
>usb.!UXHCI	1.2
>!AEFINVRAM	2.1
>!AEFIRuntime	2.1
>!ASMCRTC	1.0
|IOSMBus!F	1.1
|IOHID!F	2.0.0
|IOTimeSync!F	1230.2
|IOSkywalk!F	1.0
>mDNSOffloadUserClient	1.0.1b8
|IONetworking!F	3.4
>DiskImages	493.0.0
|IO!B!F	9.0.0
|IOReport!F	47
$quarantine	4
$sandbox	300.0
@kext.!AMatch	1.0.0d1
>!ASSE	1.0
>!ALockdownMode	1
>!AKeyStore	2
>!UTDM	556
|IOUSBMass!SDriver	243
|IOSCSIBlockCommandsDevice	492
|IOSCSIArchitectureModel!F	492
>!AFDEKeyStore	28.30
>!AEffaceable!S	1.0
|IO!S!F	2.1
>!ACyrus	1
>!ACredentialManager	1.0
>KernelRelayHost	1
|IOUSBHost!F	1.2
>!UHostMergeProperties	1.2
>usb.!UCommon	1.0
>!AMobileFileIntegrity	1.0.5
$!AImage4	5.0.0
@kext.CoreTrust	1
|CoreAnalytics!F	1
>!ABusPower!C	1.0
>!ASEPManager	1.0.1
>IOSlaveProcessor	1
>!AACPIPlatform	6.1
>!ASMC	3.1.9
|IOPCI!F	2.9
|IOACPI!F	1.4
>watchdog	1
@kec.pthread	1
@kec.XrtHostedXnu	1
@kec.Libm	1
@kec.Compression	1.0
@kec.corecrypto	14.0


The new Great Equalizer is the SEND button.

In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
Re: Mysterious restarts
artie505 #65738 02/22/24 08:50 PM
Joined: Aug 2009
Offline

Joined: Aug 2009
Dunno. Energy Saver settings? Something woke it from sleep? Had a power failure while you were sleeping?


iMac (19,1, 3.1 GHz i5, 12.7.4, 40 Gb RAM); MacBook Air (1.8 Ghz, 8 Gb RAM, 10.14.6, 256 Gb SSD) Vodafone router and Devolo Wi-Fi Extender, Canon TS8351 printer/scanner.
Re: Mysterious restarts
freelance #65739 02/23/24 03:05 AM
Joined: Aug 2009
Likes: 15
OP Online

Joined: Aug 2009
Likes: 15
Originally Posted by freelance
Dunno. Energy Saver settings? Something woke it from sleep? Had a power failure while you were sleeping?
Nope, none of the above scenarios would have triggered a kernel panic.

I just looked in Console, and it happened yesterday and on the 18th, both instances apparently having had something to do with WindowServer.


The new Great Equalizer is the SEND button.

In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
Re: Mysterious restarts
artie505 #65740 02/23/24 06:27 PM
Joined: Aug 2009
Likes: 16
Moderator
Online
Moderator

Joined: Aug 2009
Likes: 16
Originally Posted by artie505
I've awakened twice in the past couple of weeks to pop-ups advising me that my MBP had restarted while I was asleep. The occurrences having happened while I was asleep - Music was running white noise and Safari was running in the background - leaves me clueless as to what might have triggered them.

I've booted into Recovery and run First Aid, but everything's come up roses.

I can't make heads or tails of the "panic" reports, but maybe someone else can:

Those are intended for the use of developers and without intimate knowledge of the hardware, macOS, and software that is running they are relatively unintelligible. However, there are a few breadcrumbs that can be identified.

Originally Posted by panic report
Code
panic(cpu 4 caller 0xffffff801e89189b): userspace watchdog timeout: no successful checkins from WindowServer (2 induced crashes) in 120 seconds
WindowServer has not exited since first loaded[/color]
service: logd, total successful checkins in 115335 seconds: 11534, last successful checkin: 0 seconds ago

-->snip<--

Panicked task 0xffffff8b7499cdf8: 3 threads: pid 113: watchdogd
Backtrace (CPU 4), panicked thread: 0xffffff8b74d460c8, Frame : Return Address


      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[F1797B78-7645-3FC6-AD29-624DD0826DA0]@0xffffff801e88f000->0xffffff801e891fff

Process name corresponding to current thread (0xffffff8b74d460c8): watchdogd

-->snip<--

last started kext at 6339687245: >!AHIDKeyboard	7400.2 (addr 0xffffff801d0f4000, size 20480)
last stopped kext at 114494892603152: @UVCService	1 (addr 0xffffff7fb0de3000, size 4096)
loaded kexts:
com.binaryfruit.driver.SATSMARTDriver	0.10.3
>!AHIDALSService	1
>!ATopCaseHIDEventDriver	7430.5
>!APlatformEnabler	2.7.0d0
>AGPM	135
>X86PlatformShim	1.0.0
@filesystems.autofs	3.0
@kext.AMDRadeonX6000	5.0.2
@kext.AMDRadeonServiceManager	5.0.2
>!AUpstreamUserClient	3.6.11

@kext.AMDRadeonX6100HWLibs	1.0
@kext.AMDRadeonX6000

  • the panic was raised by the task Watchdog due to a failure to receive a response from a task in the user area
  • there were three kernel extensions in the backtrace com.binaryfruit.driver.SATSMARTDriver, kext.AMDRadeonX6100HWLibs, and
    kext.AMDRadeonX6000.


Given that information and your recent history of issues with DriveDX there is at least a start for troubleshooting. The first question I have is in System Settings > Energy Saver is Put hard disk to sleep when possible On or OFF? What about Prevent automatic sleeping when the display is off?

COMMENT: I wish there was an AI to analyze crash reports.


If we knew what it was we were doing, it wouldn't be called research, would it?

— Albert Einstein
Re: Mysterious restarts
joemikeb #65743 02/26/24 05:57 AM
Joined: Aug 2009
Likes: 15
OP Online

Joined: Aug 2009
Likes: 15
Originally Posted by joemikeb
Originally Posted by artie505
I can't make heads or tails of the "panic" reports, but maybe someone else can:

Those are intended for the use of developers and without intimate knowledge of the hardware, macOS, and software that is running they are relatively unintelligible. However, there are a few breadcrumbs that can be identified.
Indeed, and I was hoping you could do better at identifying those crumbs than I could.

Originally Posted by panic report
[code]
panic(cpu 4 caller 0xffffff801e89189b): userspace watchdog timeout: no successful checkins from WindowServer (2 induced crashes) in 120 seconds
WindowServer has not exited since first loaded[/color]

-->snip<--

loaded kexts:
com.binaryfruit.driver.SATSMARTDriver 0.10.3

-->snip<--

  • the panic was raised by the task Watchdog due to a failure to receive a response from a task in the user area
  • there were three kernel extensions in the backtrace com.binaryfruit.driver.SATSMARTDriver, kext.AMDRadeonX6100HWLibs, and
    kext.AMDRadeonX6000.


Given that information and your recent history of issues with DriveDX there is at least a start for troubleshooting. The first question I have is in System Settings > Energy Saver is Put hard disk to sleep when possible On or OFF? What about Prevent automatic sleeping when the display is off?
To that, I'll add that each panic report was reported in Console as "Kernel" and accompanied by two "WindowServer" "Spin Reports" that are perhaps even more incomprehensible than the panic reports. (See, and I've saved copies of the "Spin Reports" if you're interested in seeing them.) That makes me wonder if having IMGUR open in a Safari tab could be involved, because the Imgur page invariably has any number of animated thumbnails running at any given time. (I've begun quitting Safari before I go to sleep to see if it has any effect.)

I'll discount DriveDx as a possible guilty party. It's always been erratic in its reporting on my thumb drive, but no more so recently than usual. (It's kevs who's reported issues with DriveDx, not me, and it appears to have been mentioned not as contributing factor, but simply as one of a number of kexts that were running at the time of the panics.)

My Energy Saver settings (I've always wondered how/if the hard disk setting related to machines with SSDs.)

Originally Posted by joemikeb
COMMENT: I wish there was an AI to analyze crash reports.
Wouldn't it be luverly!


The new Great Equalizer is the SEND button.

In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
Re: Mysterious restarts
artie505 #65746 02/26/24 09:44 PM
Joined: Aug 2009
Likes: 16
Moderator
Online
Moderator

Joined: Aug 2009
Likes: 16
Originally Posted by artie505
To that, I'll add that each panic report was reported in Console as "Kernel" and accompanied by two "WindowServer" "Spin Reports" that are perhaps even more incomprehensible than the panic reports. (See, and I've saved copies of the "Spin Reports" if you're interested in seeing them.) That makes me wonder if having IMGUR open in a Safari tab could be involved, because the Imgur page invariably has any number of animated thumbnails running at any given time. (I've begun quitting Safari before I go to sleep to see if it has any effect.)

Each report type is designed for the specific needs of a specific audience. None of them are designed for the user. In their raw form, many (most?), are unintelligible to any audience and what you see in the log files has been formatted and carefully tailored to their unique audience not to inform the user.

Originally Posted by artie505
I'll discount DriveDx as a possible guilty party. It's always been erratic in its reporting on my thumb drive, but no more so recently than usual. (It's kevs who's reported issues with DriveDx, not me, and it appears to have been mentioned not as contributing factor, but simply as one of a number of kexts that were running at the time of the panics.)

There are clues in the report that indicated a hung or non-responsive task. The kext com.binaryfruit.driver.SATSMARTDriver 0.10.3 is near the bottom of the linked chin of tasks, therefore closer to the root cause. SATSMARTDriver is an Open-Source project used in several other applications, including TechTool Pro, to overcome limitations in the USB standard.

  1. IIRC you use the thumb drive as a backup drive? If a backup were in process when DriveDX pinged the thumb drive, thumb drives typically lack the buffering that might allow a timely response to the ping causing the exception to be raised.
  2. The thumb drive may not wake fast enough to respond if it is "sleeping" when pinged.
  3. The issue may be related to the Radeon drive not responding or not responding fast enough.


In any case, the issue in DriveDX task lineage so by temporarily disabling DriveX, you can confirm the problem is either DriveDX or still farther downstream. After that, it is a slow, tedious process of disconnecting/disabling one device/task at a time until the cause is identified. At least it will allow you to practice your patience.


If we knew what it was we were doing, it wouldn't be called research, would it?

— Albert Einstein
Re: Mysterious restarts
joemikeb #65935 03/25/24 09:24 AM
Joined: Aug 2009
Likes: 15
OP Online

Joined: Aug 2009
Likes: 15
Originally Posted by joemikeb
There are clues in the report that indicated a hung or non-responsive task. The kext com.binaryfruit.driver.SATSMARTDriver 0.10.3 is near the bottom of the linked chin of tasks, therefore closer to the root cause. SATSMARTDriver is an Open-Source project used in several other applications, including TechTool Pro, to overcome limitations in the USB standard.
  1. IIRC you use the thumb drive as a backup drive? If a backup were in process when DriveDX pinged the thumb drive, thumb drives typically lack the buffering that might allow a timely response to the ping causing the exception to be raised.
  2. The thumb drive may not wake fast enough to respond if it is "sleeping" when pinged.
  3. The issue may be related to the Radeon drive not responding or not responding fast enough.

In any case, the issue in DriveDX task lineage so by temporarily disabling DriveX, you can confirm the problem is either DriveDX or still farther downstream. After that, it is a slow, tedious process of disconnecting/disabling one device/task at a time until the cause is identified. At least it will allow you to practice your patience.
My patience? HAH!!!

Thanks for the insight that the closer you get to the bottom of the report, the closer you are to the root of the problem.

I ASSume that SATSMARTDriver isn't involved in my problem, because the crashes didn't occur while backups were in progress.

I've got no idea what the AMDRadeonX6000 extension is or how it might be involved or investigated.

Since the crash reports were accompanied by the WindowServer spin reports, I decided that maybe Safari/Imgur was somehow involved, I now close my Imgur tab while I'm sleeping, and the issue hasn't recurred in the month since.

Fingers crossed.


The new Great Equalizer is the SEND button.

In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
Re: Mysterious restarts
artie505 #65944 03/25/24 04:59 PM
Joined: Aug 2009
Likes: 16
Moderator
Online
Moderator

Joined: Aug 2009
Likes: 16
Originally Posted by artie505
I ASSume that SATSMARTDriver isn't involved in my problem, because the crashes didn't occur while backups were in progress.

SATSMARTDriver is an open source utility that permits reading the S.M.A.R.T. values of a drive connected via USB. It is necessary because the USB protocol does not support reading the S.M.A.R.T. parameters and is installed by DriveDX. It plays no part in backups other than its operation might be blocked by a backup in progress.


If we knew what it was we were doing, it wouldn't be called research, would it?

— Albert Einstein
Re: Mysterious restarts
joemikeb #65947 03/26/24 05:16 PM
Joined: Aug 2009
Likes: 15
OP Online

Joined: Aug 2009
Likes: 15
Originally Posted by joemikeb
Originally Posted by artie505
I ASSume that SATSMARTDriver isn't involved in my problem, because the crashes didn't occur while backups were in progress.

SATSMARTDriver is an open source utility that permits reading the S.M.A.R.T. values of a drive connected via USB. It is necessary because the USB protocol does not support reading the S.M.A.R.T. parameters and is installed by DriveDX. It plays no part in backups other than its operation might be blocked by a backup in progress.
I mentioned SATSMARTDriver only because you suggested it as a possible factor in an earlier post.


The new Great Equalizer is the SEND button.

In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire

Moderated by  alternaut, dkmarsh, joemikeb 

Link Copied to Clipboard
Powered by UBB.threads™ PHP Forum Software 7.7.4
(Release build 20200307)
Responsive Width:

PHP: 7.4.33 Page Time: 0.233s Queries: 32 (0.016s) Memory: 0.6326 MB (Peak: 0.7394 MB) Data Comp: Zlib Server Time: 2024-04-18 01:29:58 UTC
Valid HTML 5 and Valid CSS