Connection Timeouts and Sending Msg. Failed Errors

peskypescado · Post by **peskypescado** » January 14th, 2006, 12:30 pm

Nice workaround you found. Easier to tell people to do that than to setup affinity. I agree though, this is not a proper fix. This just makes tbird start with affinity for CPU 0 everytime (at least on my machine).

Carlton Bale · Post by **Carlton Bale** » January 14th, 2006, 12:55 pm

Has a bug report been entered for this? This needs to be addressed asap because Thuderbird 1.5 is non-functional on dual-core processors. Glad I found this thread!

nimsje · Post by **nimsje** » January 14th, 2006, 1:31 pm

Don't know if it has been reported. Anyone knows where to file a bug report?

Carlton Bale · Post by **Carlton Bale** » January 14th, 2006, 1:42 pm

I did find a bug report. Links below. Please vote for this bug to give it more priority! I can't believe Thunderbird 1.5 was released with this bug still alive!

Bug report 307527:
https://bugzilla.mozilla.org/show_bug.cgi?id=307527

Vote for this bug (may help get it resolved more quickly):
https://bugzilla.mozilla.org/votes.cgi? ... ote_307527

JeffreyReid · Post by **JeffreyReid** » January 14th, 2006, 1:46 pm

Carlton Bale wrote:Has a bug report been entered for this? This needs to be addressed asap because Thuderbird 1.5 is non-functional on dual-core processors. Glad I found this thread!

I know it's been recognized, it's been entered into the knowledge base:

http://kb.mozillazine.org/Timeout_on_dual_core

Carlton Bale · Post by **Carlton Bale** » January 14th, 2006, 2:03 pm

Thanks, I updated the KB article with more information on Windows98 Compatibility Mode work-around reported here. The KB article also has links to the bug reports.

Everyone, please vote for the bug on bugzilla.mozilla.org:
https://bugzilla.mozilla.org/votes.cgi? ... ote_307527

Carlton Bale · Post by **Carlton Bale** » January 14th, 2006, 2:12 pm

I did find a problem with the "Windows 98/ME compatibility mode" fix. In this mode, forward slashes are converted to back slashes in links sent to external applications (such as Firefox). This makes the URL invalid. So the compatibility mode fix is only a partial work-around.

nimsje · Post by **nimsje** » January 14th, 2006, 3:09 pm

Ah so that is causing this problem

. I didn't know why this was happening.

p.s. Maybe this isn't a real thunderbird problem, but actually somehting else. This I found on the VMWARE website, while also having problems running vmware on my X2.
<a href="http://www.vmware.com/support/kb/enduser/std_adp.php?p_sid=VIxaSCZh&p_lva=&p_faqid=1236&p_created=1078878344&p_sp=cF9zcmNoPTEmcF9ncmlkc29ydD0mcF9yb3dfY250PTcyJnBfc2VhcmNoX3RleHQ9c2luZ2xlIE5VTUEgbm9kZSAoQ0VDKSZwX3NlYXJjaF90eXBlPTcmcF9wcm9kX2x2bDE9fmFueX4mcF9wcm9kX2x2bDI9fmFueX4mcF9zb3J0X2J5PWRmbHQmcF9wYWdlPTE*&p_li=">http://www.vmware.com/support/kb/......</a>

64-Bit AMD Systems

Timestamp counters (TSCs) on 64-bit AMD systems should ideally remain synchronized, because these systems run all CPUs from a common clock oscillator. However, some 64-bit AMD systems have power management features that can cause the TSCs on some processor cores to lose time relative to others.

You may be able to disable these features in your system's BIOS. In the BIOS setup screens, look for settings labeled PowerNow or Cool'N'Quiet, and disable them.

If you require these features or your BIOS does not provide a way to disable them, you need to assign each of your virtual machines to a subset of processor cores whose TSCs do remain synchronized. In some cases you may need to do this even after turning off power management in your system's BIOS; this occurs if your system only partially disables the power management features involved. See the next section.

Note: If you are running Windows XP Service Pack 2 as the host operating system on a multiprocessor 64-bit AMD host that supports processor power management features, you also need to apply the hotfix described in Microsoft knowledge base article 896256 at www.support.microsoft.com/?id=896256. According to this Microsoft knowledge base article, the hotfix is needed for the following operating systems:

* Microsoft Windows Server 2003, Standard and Enterprise x64 Editions
* Microsoft Windows XP Service Pack 2, when used with Microsoft Windows XP Home and Professional Editions
* Microsoft Windows XP Tablet PC Edition 2005

No hotfix is needed for Microsoft XP Media Center.

I will try to disable cool n quite and see if tbird starts back up.

nimsje · Post by **nimsje** » January 14th, 2006, 3:19 pm

Bummer disabling cool and quiet did not solve this problem.

nimsje · Post by **nimsje** » January 14th, 2006, 5:29 pm

*SOLUTION FOUND*

I have found the solution thanks to http://www.xtremesystems.org/forums/sho ... hp?t=81429

The real cause of the problem seems to be something with the X2 and XP.

The hotfix from microsoft and the AMD drivers cause tbird not to mess-up the TSC-timing problem anymore.

To fix the problem read this, copied from http://www.xtremesystems.org/forums/sho ... hp?t=81429:

PLEASE BACKUP YOUR REGISTRY FIRST!!

1 - Install the amd drivers, download it from here... http://www.amd.com/us-en/Processors/Tec ... 18,00.html

2 - read this website and download the hotfix....READ http://support.microsoft.com/?id=896256 ........Download here http://www.sendmefile.com/00213285

3 - Edit your registry to enable the HOTFIX, follow these steps.
1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Right-click HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session Manager, point to New, and then click Key.
3. Type Throttle for the new key name.
4. Right-click Throttle, point to New, and then click DWORD Value.
5. Type PerfEnablePackageIdle for the value name.
6. Right-click PerfEnablePackageIdle, and then click Modify.
7. In the Edit DWORD Value box, type 1. In the Value data box, make sure that Hexadecimal is selected, and then click OK.
8. Quit Registry Editor.

4 - Make sure your BOOT.ini has this command in it, /usepmtimer to check, right click on My Computer go to properties, click on the ADVANCE tab, then under startup and recovery click on settings, then click on EDIT....make sure your boot.ini looks like this

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /usepmtimer

<b>Note: it can fail, and it looks like the patch from MS only works on the English version of XP. I had no problem installing it, but that is no guarantee!</b> The word is, that this patch wil be included in SP-3 from XP.

J0Mama · Post by **J0Mama** » January 15th, 2006, 3:10 am

DO NOT install both fixes at the same time. nimsje is talking out of his ass. Use only the hotfix; don't modify your boot.ini.

nimsje · Post by **nimsje** » January 15th, 2006, 3:57 am

It doesn't really matter because: AMD's new CPU driver for X2 will automatically add a string "/usepmtimer" in the boot.ini file, as it did with mine. I installed both fixes, and my problem was gone.

"/usepmtimer" is used to tell windows to use the southbridge timer instead of the CPU timers.

JOMama: Please explain what the crap is, that is coming out of it then

.

nimsje · Post by **nimsje** » January 15th, 2006, 4:03 am

p.s. As a test I removed the /usepmtimer from my boot.ini, and it looks like to be working still.

J0Mama · Post by **J0Mama** » January 15th, 2006, 4:08 am

Of course it is. Only AMD systems fuck up some games' timings if you don't have /usepmtimer, even if you have the hotfix installed. Which doesn't speak good for AMD.

nimsje · Post by **nimsje** » January 15th, 2006, 5:00 am

Correction, the /usepmitimer actually is needed! I have the same connection errors back without this option in my boot.ini!