On Fri, 10 Jun 2005 at 16:27 GMT, quoth Jim
james@the-computer-shop.co.uk>:
DFS wrote:

Thousands of unexplainable Linux freezes shouldn't occur, but they do.

Thousands?

He's doing his Erik impersonation. Again. He may be called upon to fill
in sometime while Erik is out being reprogrammed.

In article <87k6l2dbt4.fsf@angua.ankh-morpork.lan>, Mart van de Wege wrote:

The problem is that, for the zillionth time, a bug has popped in IE
where the programmers didn't check their input, allowing IE to request
a too large amount of memory. The attempt to display a large image may
trigger other problems in the video driver causing a BSOD, but the
faulty component is most certainly IE, and therefore the Operating
System itself.

Mart

Except Mart... It doesn't matter if your using IE or not. It occurs
just as readily in FireFox as well. Unless your saying that FireFox has
the same bug?

Tom Shelton <tom@YOUKNOWTHEDRILLmtogden.com> writes:

In article <87k6l2dbt4.fsf@angua.ankh-morpork.lan>, Mart van de Wege wrote:

snip

The problem is that, for the zillionth time, a bug has popped in IE
where the programmers didn't check their input, allowing IE to request
a too large amount of memory. The attempt to display a large image may
trigger other problems in the video driver causing a BSOD, but the
faulty component is most certainly IE, and therefore the Operating
System itself.

Mart

Except Mart... It doesn't matter if your using IE or not. It occurs
just as readily in FireFox as well. Unless your saying that FireFox has
the same bug?

Quite possible. The original posts here made as if it was an IE flaw,
and IE has a history of flaws stemming from incomplete or missing
input validation.

I'd agree that if the Firefox devs made the same mistake that would
have been dumb as well.

Jim Richardson wrote something like:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 09 Jun 2005 08:27:08 GMT,
amosf <linux_nut@bcs4me.com> wrote:
Peter Köhlmann wrote something like:

Try this with XP (all patched)

HTML
BODY
IMG SRC="./sweetydead.jpg" width="9999999" height="9999999"> </BODY
/HTML

The image does not need to be that large, a very small one is
sufficient Just the /declaration/ of the size is enough to trigger the
bug

Save your data before. The machine will BSOD

May I note that firefox on linux wasn't real happy with this either. It
made firefox very sluggish but at least didn't kill it... Just really
really sloooow... :)




Not a problem here, firefox 1.0.4 on Ubuntu. No slow down, no resource
hogging, cpu not showing any unusual usage. What version of FF are you
using?

hmm. Maybe coz it's 1.03... I get high CPU. etc... I'll have to upgrade
and see.

Here's a scary one from last month where Linux spontaneously rebooted:
"While running a 32 bit Java program 2.6.12-rc3 rebooted spontaneously
leaving a corrupt partition table and disk with errors. There was nothing
in dmesg (no oops/panic) except some -MARK- entries during the reboot."
http://www.ussg.iu.edu/hypermail/linux/kernel/0504.3/0013.html



Linux ready for prime time? I think not.

On Friday 10 June 2005 13:03, Sinister Midget <sinister@stinkfoot.biz
(<slrndaj70d.gga.sinister@laptop.harry.net>) wrote:

On Fri, 10 Jun 2005 at 16:27 GMT, quoth Jim
james@the-computer-shop.co.uk>:
DFS wrote:

Thousands of unexplainable Linux freezes shouldn't occur, but they do.

Thousands?

He's doing his Erik impersonation. Again. He may be called upon to fill
in sometime while Erik is out being reprogrammed.

Did his vacuum tube burn out?

Thanks for the link. Didn't know this about /proc/kcore as I never
needed to use this before.

/proc/kcore is like an "alias" for
the memory in your computer. Its
size is the same as the amount of
RAM you have, and if you read it
as a file, the kernel does memory reads.

So out of curiousity... back to the crash reported on RedHat. If the
backup process was reading this file why would it randomly crash? It
appears that the backup app was running as root and reading this file
(in order to back it up) would result in reading the system RAM. It's
only a read operation so the read shouldn't be destructive to the RAM
contents. It's not clear why it would crash some times but not always.

Except Mart... It doesn't matter if your using IE or not. It occurs
just as readily in FireFox as well. Unless your saying that FireFox has
the same bug?

News Flash!!! Internet Explorer (IE) is NOT an operating system.

I have the same Intel controller: 82865G.

Not a problem here.

On Friday 10 June 2005 13:03, Sinister Midget <sinister@stinkfoot.biz
(<slrndaj70d.gga.sinister@laptop.harry.net>) wrote:

On Fri, 10 Jun 2005 at 16:27 GMT, quoth Jim
james@the-computer-shop.co.uk>:
DFS wrote:

Thousands of unexplainable Linux freezes shouldn't occur, but they do.

Thousands?

He's doing his Erik impersonation. Again. He may be called upon to fill
in sometime while Erik is out being reprogrammed.

Did his vacuum tube burn out?

Tom Shelton <tom@YOUKNOWTHEDRILLmtogden.com> writes:

In article <87k6l2dbt4.fsf@angua.ankh-morpork.lan>, Mart van de Wege wrote:

snip

The problem is that, for the zillionth time, a bug has popped in IE
where the programmers didn't check their input, allowing IE to request
a too large amount of memory. The attempt to display a large image may
trigger other problems in the video driver causing a BSOD, but the
faulty component is most certainly IE, and therefore the Operating
System itself.

Mart

Except Mart... It doesn't matter if your using IE or not. It occurs
just as readily in FireFox as well. Unless your saying that FireFox has
the same bug?

Quite possible. The original posts here made as if it was an IE flaw,
and IE has a history of flaws stemming from incomplete or missing
input validation.

I'd agree that if the Firefox devs made the same mistake that would
have been dumb as well.

begin Error Log for Thu, 09 Jun 2005 17:38:08 -0400 - "DFS"
nospam@dfs_.com> caused an invalid page fault at address
3F2qe.35$Ub4.10@fe06.lga>, details as follows:

I have the same Intel controller: 82865G.

Not a problem here.

A post ago you stated you have...

"Windows Server 2003, 1gig RAM, ATI 9600 video card"

begin oe_protect.scr

Tom Shelton <tom@YOUKNOWTHEDRILLmtogden.com> espoused:

snip bit about trying to blame drivers for XP problems

Will you please stop nymshifting.

*plonk*.