Anders, On Tuesday 12 October 2004 13:27, Anders Johansson wrote:
On Tuesday, 12 October 2004 22.17, Randall R Schulz wrote:
Richard,
On Tuesday 12 October 2004 10:31, rkimber@ntlworld.com wrote:
...
Hmmnn. Well on my amd64, Opera regularly causes a complete freeze on my system, while Netscape at worst just crashes. Netscape 7.1 seems pretty good, whatever its provenance.
I hope you realize that symptoms of this sort (system freeze) cannot be pinned on Opera or on any user-level code. When a system with protected memory exhibits gross, system-wide failures, it is by definition a bug in some privileged code (kernel or driver, e.g.) or a failure of some hardware component.
It depends. Since X controls all input devices and output when it's active, a total X freeze can be indistinguishable from a total system freeze. For all practical purposes, it *is* a total system freeze, unless you can reach the system through ssh or similar, or can use a magic sysrq to kill it or something. This is the most common "system crash" in linux.
True. In a sense, it's a matter of semantics. Or, more precisely. of the limits of observation. I would not call an X lock-up a "system freeze," even though I might not be able to distinguish the two. If CTRL-ALT-F1 doesn't get me to a console because of an X problem and I have no serial terminal with which to attempt a login and can get to no other computer from which to attempt network access of some sort, then to all available external appearances, the system as a whole has locked up. Randall Schulz