Rodrigo Barbosa wrote:
Have you tried disabling hyperthreading? I had suffered this problem when we started buying Intel Xeon's, disabling HT'ing seemed to fix the problem for me.
Some people suggested that too. I'm asking for two of these systems to be sent back from our remote data center. I'll try it then.
Did you just ended up running without hyperthreading? Did you ever find a solution? It seems an awful waste if you can't use it.
Disabling HT only solves it on single processor systems.
In my case it fixed our dual processor systems (Dell PE2650) but to be honest I was never quite sure if it was an OS patch or HT'ing. I just disable HT'ing, build and they just work, I have not seen this problem for a while now.
Dean
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, Jan 20, 2006 at 08:38:09AM -0000, Plant, Dean wrote:
Rodrigo Barbosa wrote:
Have you tried disabling hyperthreading? I had suffered this problem when we started buying Intel Xeon's, disabling HT'ing seemed to fix the problem for me.
Some people suggested that too. I'm asking for two of these systems to be sent back from our remote data center. I'll try it then.
Did you just ended up running without hyperthreading? Did you ever find a solution? It seems an awful waste if you can't use it.
Disabling HT only solves it on single processor systems.
In my case it fixed our dual processor systems (Dell PE2650) but to be honest I was never quite sure if it was an OS patch or HT'ing. I just disable HT'ing, build and they just work, I have not seen this problem for a while now.
Did't solve for me on a Dual Xeon. The problem was reduced, happens less frequently, but still happens :(
[]s
- -- Rodrigo Barbosa rodrigob@suespammers.org "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
On 1/20/06, Rodrigo Barbosa rodrigob@suespammers.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, Jan 20, 2006 at 08:38:09AM -0000, Plant, Dean wrote:
Rodrigo Barbosa wrote:
Have you tried disabling hyperthreading? I had suffered this problem when we started buying Intel Xeon's, disabling HT'ing seemed to fix the problem for me.
Some people suggested that too. I'm asking for two of these systems to be sent back from our remote data center. I'll try it then.
Did you just ended up running without hyperthreading? Did you ever find a solution? It seems an awful waste if you can't use it.
Disabling HT only solves it on single processor systems.
In my case it fixed our dual processor systems (Dell PE2650) but to be honest I was never quite sure if it was an OS patch or HT'ing. I just disable HT'ing, build and they just work, I have not seen this problem for a while now.
Did't solve for me on a Dual Xeon. The problem was reduced, happens less frequently, but still happens :(
I disabled hyperthreading... it is still hanging.
Rodrigo Barbosa rodrigob@suespammers.org "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFD0Q2DpdyWzQ5b5ckRAri/AJ9DEDPlWNKrT9S7Yha4NImPVw+yaACeMQuO /KnaeI7ZJbM4uFskZPe7vyA= =OyJl -----END PGP SIGNATURE----- _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
We've narrowed this down to the serial port. Whenever we have anything plugged into the serial port, the system hangs. At the local login prompt, it hangs after entering the user name and hitting enter.
USB keyboard still responds because you can still use ALT-Tab to switch to other virtual terminals.
Again, nothing on screen. silent.
This is reported by mgetty in the logs:
01/20 22:45:04 yS0 mgetty: experimental test release 1.1.31-Jul24 01/20 22:45:04 yS0 check for lockfiles 01/20 22:45:04 yS0 locking the line 01/20 22:45:35 yS0 WARNING: DCD line still active, check modem settings (AT&Dx)01/20 22:45:35 yS0 lowering DTR to reset Modem 01/20 22:45:36 yS0 waiting... 01/20 22:46:11 ##### failed dev=ttyS0, pid=5865, got signal 1, exiting
01/20 22:46:11 yS0 mgetty: experimental test release 1.1.31-Jul24 01/20 22:46:11 yS0 check for lockfiles 01/20 22:46:11 yS0 locking the line 01/20 22:47:13 yS0 WARNING: DCD line still active, check modem settings (AT&Dx)01/20 22:47:13 yS0 lowering DTR to reset Modem 01/20 22:47:13 ##### failed dev=ttyS0, pid=5898, got signal 15, exiting
On 1/20/06, Fong Vang sudoyang@gmail.com wrote:
On 1/20/06, Rodrigo Barbosa rodrigob@suespammers.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, Jan 20, 2006 at 08:38:09AM -0000, Plant, Dean wrote:
Rodrigo Barbosa wrote:
Have you tried disabling hyperthreading? I had suffered this problem when we started buying Intel Xeon's, disabling HT'ing seemed to fix the problem for me.
Some people suggested that too. I'm asking for two of these systems to be sent back from our remote data center. I'll try it then.
Did you just ended up running without hyperthreading? Did you ever find a solution? It seems an awful waste if you can't use it.
Disabling HT only solves it on single processor systems.
In my case it fixed our dual processor systems (Dell PE2650) but to be honest I was never quite sure if it was an OS patch or HT'ing. I just disable HT'ing, build and they just work, I have not seen this problem for a while now.
Did't solve for me on a Dual Xeon. The problem was reduced, happens less frequently, but still happens :(
I disabled hyperthreading... it is still hanging.
Rodrigo Barbosa rodrigob@suespammers.org "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFD0Q2DpdyWzQ5b5ckRAri/AJ9DEDPlWNKrT9S7Yha4NImPVw+yaACeMQuO /KnaeI7ZJbM4uFskZPe7vyA= =OyJl -----END PGP SIGNATURE----- _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 1/20/06, Fong Vang sudoyang@gmail.com wrote:
We've narrowed this down to the serial port. Whenever we have anything plugged into the serial port, the system hangs. At the local login prompt, it hangs after entering the user name and hitting enter.
USB keyboard still responds because you can still use ALT-Tab to switch to other virtual terminals.
Again, nothing on screen. silent.
This is reported by mgetty in the logs:
01/20 22:45:04 yS0 mgetty: experimental test release 1.1.31-Jul24 01/20 22:45:04 yS0 check for lockfiles 01/20 22:45:04 yS0 locking the line 01/20 22:45:35 yS0 WARNING: DCD line still active, check modem settings (AT&Dx)01/20 22:45:35 yS0 lowering DTR to reset Modem 01/20 22:45:36 yS0 waiting... 01/20 22:46:11 ##### failed dev=ttyS0, pid=5865, got signal 1, exiting
01/20 22:46:11 yS0 mgetty: experimental test release 1.1.31-Jul24 01/20 22:46:11 yS0 check for lockfiles 01/20 22:46:11 yS0 locking the line 01/20 22:47:13 yS0 WARNING: DCD line still active, check modem settings (AT&Dx)01/20 22:47:13 yS0 lowering DTR to reset Modem 01/20 22:47:13 ##### failed dev=ttyS0, pid=5898, got signal 15, exiting
All our CentOS 4.1 systems have this problem -- regardless of hardware. Disabling mgetty allows us to use the systems after plugging in the serial connection.
On 1/20/06, Fong Vang sudoyang@gmail.com wrote:
On 1/20/06, Rodrigo Barbosa rodrigob@suespammers.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, Jan 20, 2006 at 08:38:09AM -0000, Plant, Dean wrote:
Rodrigo Barbosa wrote:
> Have you tried disabling hyperthreading? I had suffered this problem > when we started buying Intel Xeon's, disabling HT'ing seemed to fix > the problem for me.
Some people suggested that too. I'm asking for two of these systems to be sent back from our remote data center. I'll try it then.
Did you just ended up running without hyperthreading? Did you ever find a solution? It seems an awful waste if you can't use it.
Disabling HT only solves it on single processor systems.
In my case it fixed our dual processor systems (Dell PE2650) but to be honest I was never quite sure if it was an OS patch or HT'ing. I just disable HT'ing, build and they just work, I have not seen this problem for a while now.
Did't solve for me on a Dual Xeon. The problem was reduced, happens less frequently, but still happens :(
I disabled hyperthreading... it is still hanging.
Rodrigo Barbosa rodrigob@suespammers.org "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFD0Q2DpdyWzQ5b5ckRAri/AJ9DEDPlWNKrT9S7Yha4NImPVw+yaACeMQuO /KnaeI7ZJbM4uFskZPe7vyA= =OyJl -----END PGP SIGNATURE----- _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Fong Vang -
Plant, Dean -
Rodrigo Barbosa