Talk:Pentium F00F bug

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing / Hardware  
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 ???  This article has not yet received a rating on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
Taskforce icon
This article is supported by Computer hardware task force.
 

Title[edit]

"F00f" is awkward, but "F00F" would be equally correct as a title. Why not move it? Hairy Dude 04:15, 24 August 2006 (UTC)

Oh, yeah. Anyone against the move? --Ihope127 00:50, 30 August 2006 (UTC)


Meaning and grammar of "possible data loss" statement[edit]

I propose changing

if the disk buffers had not been flushed, any drives that were interrupted during a write operation, or some other non-atomic operation was interrupted, it is possible for data loss to occur

to instead read

if the disk buffers had not been flushed, and any drives were interrupted during a write operation or some other non-atomic operation, it would be possible for data loss to occur

so that it's a little more grammatically correct, but I'm not sure if it has the original intended meaning. Can anyone double-check this or explain what the original version is saying? 218.189.243.131 16:59, 26 December 2006 (UTC)

No, its supposed to be a list of possible things that if interrupted could cause damage, eg:
  • If the disk buffers had not been flushed
  • or A drive is interrupted during a write operation
  • or Some other non-atomic operation was interrupted
Any of these could cause data loss to occur.
I think when I originally wrote it, it was "if the disk buffers had not been flushed, a drive was interrupted during a write operation, or some other non-atomic operation was interrupted, it is possible for data loss to occur" but someone modified it. I'm terrible at grammar, so please correct it :-) -- taviso 19:29, 26 December 2006 (UTC)


Add list of affected models?[edit]

This entry would be greatly improved by a list of affected models like the list in the Pentium FDIV bug entry. Alas, I haven't been able to find a reliable source listing which models are affected. Some anonymous Usenet posts claim that AMD K5 and K6 processors are not affected but Cyrix (which ones?) are.

And yes, the title should be changed from F00f to F00F. Upper case representations of hexadecimal numbers are quite common; my perception is that F00F is more common than f00f. Guy Macon (talk) 19:28, 18 March 2007 (UTC)

AT&T syntax?[edit]

Why not use Intel IA86 syntax?

it's exactly the same, except for the extra % before the register name, i think any intel syntax fans will work it out. -- taviso 17:52, 11 July 2007 (UTC)
And your point is?
This is an Intel IA86 bug.
Historically, this was a MS/Windows crack, at a time when MS/Windows hackers used IA86 syntax in all of their tools.
So, that's two reasons to use Intel IA86 syntax. Conversely, is there any reason to use AT&T syntax?
(FWIW, i think that any AT&T syntax fans would be able to work it out.)150.101.166.15 (talk) 03:06, 22 November 2007 (UTC)
Even if that sentence made any sense, which it doesn't, it would be wrong. Regardless, if that % sign really bothers you that much, go ahead and change it ;) -- taviso (talk) 00:17, 23 November 2007 (UTC)

Workaround[edit]

IMHO there should be some information about the workaround in this article. —Preceding unsigned comment added by 62.181.193.162 (talk) 08:38, 18 September 2007 (UTC)

I don't think there are any workarounds other than using softfloat libraries (implementing the affected arithmetic operations with integer arithmetic). -- intgr [talk] 09:21, 18 September 2007 (UTC)
I think you're confusing this (Pentium F00F bug) with the Pentium FDIV bug, there are workarounds for this one, eg [1] - taviso 03:17, 19 September 2007 (UTC)
You're right, I was confusing it with the FDIV bug. :) -- intgr [talk] 07:27, 19 September 2007 (UTC)

help with pronunciation[edit]

I wanted to clean up the pronunciation, but can't tell if it's pronounced with the oo of foot or the oo of food. kwami (talk) 11:02, 15 December 2007 (UTC)

Is it just me...[edit]

Or does this sound like the automonapoea (SP?) "FOOF!"? Maiq the liar (talk) 18:02, 18 January 2008 (UTC) Do you mean onomatopoeia? And, no, I don't think the bug makes any noise. Freddy. — Preceding unsigned comment added by 220.233.71.153 (talk) 00:04, 22 January 2013 (UTC)

New CPU affected[edit]

The article states 'No Intel processors since the introduction of the Pentium Pro have been affected by the bug' - but the Intel Quark SoC X1000 (intreduced with the galileo platform) is based on a intel 486/pentium hybrid, which states:

cat /proc/cpuinfo
processor       : 0 
vendor_id : GenuineIntel
cpu family : 5
model : 9
model name : 05/09
stepping : 0
cpu MHz : 399.076
cache size : 0 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : yes


So, we have more affected cpu's — Preceding unsigned comment added by 46.228.92.142 (talk) 11:48, 29 August 2014 (UTC)

Thanks, but to add this to the article we would need a reliable source supporting this claim. -- intgr [talk] 14:39, 29 August 2014 (UTC)
German wiki cites heise: http://www.heise.de/developer/artikel/Intels-Einplatinen-Computer-Galileo-unter-der-Lupe-2252539.html and confirms it under Intel Quark page — Preceding unsigned comment added by 85.221.130.92 (talk) 17:48, 29 August 2014 (UTC)
Heise cites Wikipedia which cites Heise? Not reputable. Reverted article. Has anyone actually *tested* this? Linux is detecting Quark as Pentium and then assuming Quark has the bug. See See also https://twitter.com/marcan42/status/526559512853889024. — Preceding unsigned comment added by 60.242.88.97 (talk) 08:05, 27 October 2014 (UTC)
I think Heise was linking to Wikipedia for an explanation about what the f00f bug is, not "citing Wikipedia" for the presence of the bug on Quark. The mention of Quark was added after the Heise article was published: [2]. But you're probably right that there's not enough evidence that they tested it, so let's keep it out of the article. -- intgr [talk] 09:34, 27 October 2014 (UTC)