Slashdot Mirror
Major Linux/Athlon CPU bug discovered
GeorgeFrancisco writes "I recently installed the nVidia drivers so I could play TuxRacer on my Athlon. Problem is it kept inexplicably hanging Linux. Now I know why. The CPU bug affects Athlon/Duron/Athlon MP AGP users. Fortunately there's a way around it, and: "Alan [Cox] is going to try to add some kind of Athlon/AGP CPU bug detection code to the kernel so that it will be able to auto-downgrade to 4K pages when necessary." Read more on the Gentoo Linux site."
Could this be AMD's version of the bug in the original Pentium?
It was bound to happen, everybody makes mistakes.
God save our Queen, and Heaven bless The Maple Leaf Forever!
just so he could play tux racer. why not just play the windows version?
I noticed this too, it seems to only affect 3D games, mainly SDL based ones such as armagedtron, but strangly it hasent affected quake 3 at all. Unreal tournamet was affected, but i SWEAR it didnt use to do that.
Aww, now I have to figure out how to install UMODs in Linux.
There was a Win2k bug a while back that did the exact same thing, and you had to install a "LargePageMinimum" patch for it to not crash. Is this the Linux equivilant of that? And if so, how come it has taken so long to surface and fix?
http://support.microsoft.com/support/kb/articles/Q 270/7/15.ASP
Since September of 2000..
Now, since gentoo's well and truly dead (thanks to slashdot), can someone explain the bug and the workaround for us Athlon users?
- A.P
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
It really shows up if you use the pre-empt kernel patch. Ever since I added the workaround, things have been pretty solid. (not that it's been that long)
The repetition of the elegant, almost minimalistic mantra, "fp," brings a warm, subtle shade of meaning to this first post. Truly a masterful work by a brilliant though little known artist. It seems a hot new contender for best original Slashdot content, a category previously dominated by the broad, mellow flavor of the goatse.cx link.
I guess it takes awhile to pile through the submissions. This was posted on pclinuxonline.com recently.
Windows=Security Bugs, huge pricetag.
Linux=Performance Bugs, no pricetag.
Gee, wonder which I'll choose...
Shift happens. Fire it up.
"AMD did prominently announce this bug when it was discovered."
Keep your tuxedos on. Not like they are recalling processors like Intel had to do to the 1.13 because it would not compile the linux kernel. Or recalling a million motherboeards for memory translation hub issues. Or forcing us to live with a floating point math error then doing their best to cover it up or Run around as the market leader yelling the sky is falling causing a slunp in the tech sector because they were faced with a little competition for the first time. And their 64 bit processor should run 32 bit apps faster than a 200mhx pentium pro.
If voting were effective, it would be illegal by now.
I don't think so. AMD reverse engineered the x86 and made their own implementation without Intel's crap in it.
AMD's version of the x86 that is in the Athlon and the Duron runs faster than Intel's chips because of this reverse engineering.
This bug could be a problem of reverse engineering the x86. It doesn't say Intel's chips have the problem.
--Metrollica
Is there more information about this bug anywhere? I'd like to know if it affects the Athlon XP I upgraded to in the last couple of months.
I had a Duron before which was very unstable with the nVidia driver AGP support enabled, but I've had a couple of crashes with the AGP support enabled on the Athlon XP - if I disable the AGP support it runs rock solid (current uptime is 8 days with GL screensavers and various GL apps having run for hours and hours of that 8 days).
I hope it's bugs in the drivers/agpgart and not the CPU - if AMD knew about this in 2000 the Duron I bought shouldn't even have had it, let alone me new Athlon XP.
More info (specifically, which CPUs it affects) would be really good. Any takers?
Chris "Ng" Jones
cmsj@tenshu.net
www.tenshu.net
Here is the cached article.
Thank Google again for this one!
--Metrollica
well, except that they released a patch back in 2000.
It would help if you actually read the story before posting uninformed opinions. Dumbass.
Chris "Ng" Jones
cmsj@tenshu.net
www.tenshu.net
Soooo... is Linux going to now start having kernel patches to detect people who overclock to 3+ gigahertz? lol -- I've heard that has some 'stability issues' as well *grin*
Groove Salad -- a nicely chilled plate of ambient grooves and beats.
Karma whoring, here I come. Hopefully this server can withstand a mild slashdotting. Link
The site seems to be down. However, last week, I contacted nVidia about this problem on my two dual Ahtlon MP workstations (random hangs when OpenGL is invoked). So the quick answer is you can
Boot your system with following option on your kernel command line: "mem=nopentium"
or
Disable AGP in XFree86 config (i.e. Option "NvAGP" "0" in the "Devices" section).
nVidia clued me into the first approach about a week and a half ago. It made my system completely stable. However, there was still some texture flakiness in some OpenGL applications. Since my workstations are number crunchers (and thus Quake FPS don't matter to me), the latter option eliminated both the stability problems and the texture flakiness (at the expense of some graphics speed).
By the way, nVidia mentioned the same issue exists on Win2K / Athlon boxes.
Enjoy,
Kevin
The Gentoo site says a simple workaround where you add "nopentium" to your kernel options at bootup and it will avoid the bug condition. Alan Cox is currently working on adding auto-detection of this bug in the kernel, so we wont have to worry about it soon.
And yes, this is the same Athlon Windows 2000 AGP bug that was discovered and patched last year with that registry key. They just didn't realize that it also effected Linux until now. I now realize that was the cause of my TuxRacer crashes with my nVidia card on my Athlon computer.
Boycott AMD!!!
--Metrollica
Wow, video problems with Athlons? That's unheard of! I've always had rock-solid stability with Athlon and all the video adapters I've owned - except the exact opposite.
You get what you pay for, baby.
So does anyone know how performance is affected from this 4MB->4KB page thing?
so the question is, if I configure my kernel for the K7 family, do I need to pass the kernel "mem=nopentium" or is this the default?
But the bug was there since Sep. 2000 !
You think someone in AMD may have correct the bug, but nooooooo.
How many version of Athlon / Thunderbird / XP / MP have there since Sep. 2000 ?
I thought in all new iteration of chip, they have "de-bugging sessions" - just like softwares - before the "tape-out" stage.
Have to wonder why AMD don't do debugging before tape-out ?
Is it money?
Or is the bug a "feature" instead ?
Muchas Gracias, Señor Edward Snowden !
Does anyone actually *know* if this is worked around in the *bsds?
Or do they use the 4k method by default anyway?
-Yarn - Rio Karma: Excellent
Nvdia drivers forces AGP to 1x due to corruptions caused by AMD Irongate chipset signal integrity [ Mentioned at the README for Nvidia 1.0-2313 Drivers ]
This newly discovered memory corruption with Athlon + AGP, is it contributing to the signal integrity of the Irongate ? Or is it a separate bug ?
Anyway this makes AMD look very bad in my view. There is a bug in the CPU and their chipset screws up my AGP to 1x. Sigh.
I should start by saying I haven't read the article yet, can't get to it. *hopes the /. traffic dies down soon...*
If it is a defect in the processor, I wonder if AMD will replace my existing processor. It may not seem like all that big of deal to most people here at Slashdot, but as a 3D artist I am *dependent* on OpenGL.
Don't get me wrong, I'm not having this problem now. (I'm not a Linux user.) But when I built my Athlon I had to install a patch for a similar type of problem in order to get the machine to work. At what point do we say "it's no longer ok to work around a CPU bug"?
If Intel has one set of bugs in their processors, and AMD has another, that divides the market. Software companies shouldn't have to put the effort into scrutinizing their code based on which CPU they are on, it's bad enough they are trying to optimize for one or the other. What happens when they get used to the workaround, but then it gets fixed? Worse yet, what happens when a company says "I'm sick of this, I'm only supporting one processor."
So it's not so much that I think AMD should replace the processors with this specific bug, but I think we should be vigilent in not allowing them to let errors like that run rampant.
"Derp de derp."
It is impossible to debug closed-source
drivers like the NVIDIA one. So any NVIDIA
bugs can't be found.
But you say "this is an AMD bug"...
How could we know that? The presence of
closed-source drivers in the kernel made
us unable to determine what was at fault.
Video drivers can cause non-video problems,
so in all cases only NVIDIA can help you.
It is easily fixed through software and there doesn't seem to be any noticeable performance hit when turning off PSE.
9 years don't menstruate. But I'd suck her pussy.
The site with the article is slashdotted to oblivion, so I'm not sure what the problem really consist of, but according to what I have read in comments below, it's not really comparable.
As far as I remember, the the bug in the original pentium was a floating point flaw that led to wrong calclulations under certain circumstances.
OK, I'll kill Clint Hollywood and you kill yourself.
I've had this problem before, so intermittent I didn't think it was worth worrying about.
:-) !!!!
When I noticed it the most (figured this out the other day) was when I had several compiles going at the same time, ie kde3 libs and say a new patched kernel.
I could never get it to reliably repeat, so never looked into it.
Great to see someone actually had the patience to figure it out
404 Not Found The requested signature was not found on this server.
I have an Athlon 850 with a Geforce 1. I thought I had finally gotten rid of the last of the system workarounds when I upgraded my BIOS and I stopped seeing "Stomping on Athlon bug" (the classic VIA chipset problem). Looks like this isn't going to be the case after all.
I have always compiled my kernel for Athlon optimisations and I use the NVidia linux drivers with agpgart. How come I haven't hit this bug before?
How much performance is knocked off the system as whole because of this? Is it a few percent? I presume this will hit all applications not just AGP ones...
can anyone tell me if this problem may occur when running SETI? only I used to run it on my dual MP Athlon under MDK 8.1 , but it would invariably kill my machine. so I stopped running it.. ideas anyone ?
nick(nospam)@(nospam)polyprecords.com
Electronic Music Made Using Linux http://soundcloud.com/polyp
I have 2 Athlon systems, a dual Thundirbird 1.4GHz (Tyan Thunder K7) and a single Thunderbird 1.4GHz (Asus A7V133). The former runs a GeForce 3 and kernel 2.4.17, the later TNT2 and RH 7.2 (kernel 2.4.9 I believe). Both systems run semi-custom NVidia drivers (release 2313). By semi-custom, I mean I tweaked them to use SBA, the NVIDIA AGP driver (NOT agpgart) and to run in 4x mode. The later has never had a problem, the former (the dual) had some problems until kernel 2.4.14.
The problems I had were frequent lockups with everything X, especially Q3A and Tribes 2. Some experimenting proved what worked and what didn't, and here's what I found:
agpgart never worked worth a damn even with kernel 2.4.17, despite several attempts by me to make it work (I don't maintain it, so I gave up on messing with it). Earlier NVIDIA drivers were less stable, but the latest is great (although it does not support FW, which blows). Tweaking the NVIDIA driver to use SBA and it's own AGP driver instead of agpgart, along with kernel 2.4.14 - 2.4.17 makes for a very stable and fast system. Older kernels just did not work worth a damn whenever I enabled DMA on my IDE drive - they locked every time. These newer kernels don't exhibit this problem, and the NVIDIA driver works nicely with all 3D games as well as 3D development tools like Blender.
My kernels have always been compiled as Athlon kernels as well. The bottom line is: don't blame this bug and/or the NVIDIA driver if your system is unstable and/or slow. There are other things at work, and in my case I seem to have found them all.
- Rohan
If one were using *BSD, AGP wouldn't be that well supported in the first place. :-)
If you're using lilo, and just want to apply the workaround quickly, edit /etc/lilo.conf.
Before the first image= line, insert the line:
append="mem=nopentium"
The article says it happens when the kernel is compiled for Pentium processors; but does this happen if the kernel is compiled for a K7?
... I have an Athlon and it kept hard freezing. The bug doesn't happen with a Voodoo card.
By the way, I had to shelve my nVidia card a couple months ago because of this
Oh my God, AMD makes you read a 7000-character licensing agreement in order to download a 334 byte patch. And people think the GPL is bad ...
Funny, I knew something was wrong...
dominionrd.blogspot.com - Restaurants on
MShaft: "Not-a-bug-it's-a-feature"
Intel: "Not a bug it's erratum."
VIA: "We slowed it down to keep it cool."
Nvidia: "That was a leak! We are not doing public driver beta testing!"
ATI "Who the hell plays Quack3?"
AMD "the patch is here"
If voting were effective, it would be illegal by now.
...seems they work for Intel. Their description was:
"It's a major bug. We don't know how it happend. We will ask marketing. We don't remember ever sell that chip.".
:-))
------I can please only one person per day. Today is not your day. Tomorrow isn't looking good either.------
I thought he meant the fdiv bug in the first generation Pentiums.. :)
;)
My mistake, I guess. It's still a little early in the morning here.
Thank you for your attention.
-- Could you use my software consulting serv
Quake 3 demo was run with \timedemo 1 and \demo DEMO001 . Each test was run three times. The system load average was < 0.5 before Quake 3 was run.
Without mem=nopentium
FPS = 79.4 (79.4, 79.4, 79.4)
With mem=nopentium
FPS = 79.2 (79.1, 79.3, 79.2)
System tested:
Athlon 850, 384MB RAM, Geforce 1 DDR, VIA KT133 Chipset
Athlon/Duron/K7 optimised 2.4.17 kernel (optimising the kernel above pentium makes very little difference though)
NVidia 1.0-2313 video drivers using agpgart
Mandrake 8.0
Quake 3 settings
Texture depth = 16 bits
Colour depth = 16 bits
Geometric detail = High
Texture detail = High
Dynamic lights = On
Video mode = 1024x768
Looks like there is a difference but it's very slight (0.003%) but my benchmarks aren't very scientific. Either way, if there is an improvement in stability this tradeoff is easily worth it. Here's hoping that you don't run linux just for it's Quake 3 scores though...
Well I had the same problem with the same setup, and after days of frustration it turned out to be overheating due to bad thermal contact and air flow. My problem never occured if I ran only one instance of seti, because cpu affinity of linux kernel sucks, and as a good sideeffect it can't overheat a single cpu. If single seti does not kill the machine, you should consider thermal problems.
Gentlemen, you can't fight in here, this is the War Room!
you are only right on this:
they add their own tech too, which is why they get different results.
quote
Now, the Athlon processor is made by a rival company, AMD. They have
basically reverse engineered the Intel processors and tried to make a
processor that operates just like Intel's processors, and then sell them
cheaper than Intel does.
This makes it a little more difficult to compare them to the Pentium
processors. Some things the AMD Athlon actually does faster than a Pentium
III, some things it does a little slower, and some things it can't do at
all, while other things the Intel can't do, the Athlon does do.
quote
Had AMD had a design ready when Intel released their Pentium, their market share
wouldn't have dropped to 10%. In the days of the 286, 386, and 486, AMD, Cyrix, and other "clones"
reverse-engineered the Intel chips. In a sense, it was Intel's design (with maybe a few improvments),
but it was reverse-engineered so it did not violate patents.
quote
But nothing lasts forever. The companies that had built Intel chips under license eventually reverse-engineered the chips and built them license-free. Intel copycats including Advanced Micro Devices (AMD) and Cyrix (a division of National Semiconductor) used the courts to validate their right to copy Intel's chip architectures. And PC manufacturers like Compaq and IBM used these clone chips as a weapon to force Intel prices down. Now the best way for Intel to stay ahead is to simply run faster. Running faster means shrinking product cycles from three years to 18 months by running parallel product development teams and spending more money faster than the other guys. Since Intel has more money to spend, this keeps them in command, but shorter product cycles mean less time to recoup R&D expenses. Hence, those lower margins.
someone better mod me up for all my work
--Metrollica
I had XMMS crashing and completely locking the box serveral times. I tried accessing my computer remotely too, but it didn't even echo on pings! This may ofcourse be XMMS' fault, but even though it's pretty darn dangerous.
no problems on FreeBSD, apparently
Shessh - that was quite a mistake (didn't multiply by 100). Man I hope nobody hires me for my mathematical ability...
I just got a new box, Athlon 1.2GHz... Asus a7a266 mainboard... nice little box for general usage. Soon as I finish moving, I'll get cable modem back and stop using mom's AOL, and I'll go back to Linux. But now I see this, and I'm eyeing my AGP card, and wondering. AMD has earned a lot of respect from me in the last couple years, as I've found the Athlons to be simply the finest x86 CPU's I've ever got my hands on, at great prices with very reasonable motherboards/chipsets as well. Now this. I'm not sure. Yeah, it's an engineering mistake, but I'm not clear on how AMD is handling it, and I hope they don't disappoint me. Sure, you can do a workaround - but as others have asked, what's the story on the performance hit? What about AMD working with the kernel folks to find another, better solution? Or maybe AMD could consider offering serious discounts on new, un-flawed CPU's, for those who are already eyeing upgrades?
think for yourself, you won't like the results if others do it for you.
I've posted some quake 3 benchmarks and it looks like the difference may not be significant (less than a half percent). However this is by no means a good test of a heavily loaded system (i.e. a high load average), nor does it test the effect when memory is tight (which is when I guess more paging would take place and the change would be more noticible).
except model 1 (the very first K7 since it didn't have PSE) are affected,
except the latest revision A5 (cpuid 662) of the Athlon XP, i.e. A0/660 and
A2/661 are affected as well (similarly all 64x Thunderbirds etc.).
(there was a model 1, 2, 4 and 6 Athlon, with 6 being XP)
Some or all Durons might be affected too, but I didn't look at that closely.
The above hinges on whether this is the correct bug description, feel free :)
to flame the anonymous coward if this has got nothing to do with it
"16 INVLPG Instruction Does Not Flush Entire Four-Megabyte Page Properly with Certain Linear Addresses
Normal Specified Operation. After executing an INVLPG instruction the TLB should not contain any
translations for any part of the page frame associated with the designated logical address.
Non-conformance. When the logical address designated by the INVLPG instruction is mapped by a 4-MB
page mapping and LA[21] is equal to one it is possible that the TLB will still retain translations after
the instruction has finished executing.
Potential Effect on System. The residual data in the TLB can result in unexpected data access to stale or
invalid pages of memory.
Suggested Workaround. When using the INVLPG instruction in association with a page that is mapped via
a 4-MB page translation, always clear bit 21."
(page 7 from Athlon Model 6 revision sheet)
The current workaround gets around this problem by disabling 4M (2M?) pages (PSE). Hence we go back to 4K pages, and mapping large slabs of VM is a little slower and wastes memory (we need another Page table for each slab of 4M) and obviously more TLB misses/space wasted, because to touch the whole 4M region, the CPU needs to do up to 1024 page table lookups instead of 1.
:-)
As discussed this may have performance implications.
According to the AMD docs, the problem is only when flushing TLB entries with INVLPG and the page is a 4M page, _and_ the virtual address's bit 21 is set (which does not affect the 4M block of memory the address is in - eg: 0x400000 (2^22) vs 0x600000 (2^22|2^21) are both in the second 4M block).
Hence, when invlpg'ing a VA we just need to INVLPG(address&~(1 (leftshift) 21)). This only requires a single ANDL instruction. But we need to distinguish a 4M page first though, so I don't know?
Heck maybe we should just do it the FreeBSD way and recursively map the Pagedir
Any ideas? Will this work?
--JQuirke
Don't know how ECC works exactly but would it possibly correct such an error on the fly?
Anyone out there know?
None of the Athlons or Durons I've built have had any problems with Tux Racer (Mostly on Man8.1 default install).
My nephew spends hours Sliding that little penguin arround with that bloody elevator music going, & not once has there been a freeze or lockup, much to my dissapointment.
Maybe it sheds some light on this issue.
this discussion is over. you lose. that quote says nothing about cpu's. quit giving fake links. stop trolling
--Metrollica
For good measure, re-install your grub config by running:
Where /dev/hda is your boot disk.
For most PC users with IDE drives, it will
be /dev/hda .
Last, just reboot.
chongo (was here)
From AMD's website:
Note: This patch is not needed for Windows XP
1. Who said Linux *never* crashes? It crashes, but not nearly as often as the OS you're obviously running..
2. Which OS can withstand hardware failiures?
3. Go LEARN SOMETHING, you nut.
I had the same problem but with my Pentium 4. When I installed the nvidia drivers the system became very unstabled and crashed often. But hey, I could start tux racer and thats the reason I installed it in the first place. But that problem was only in the latest mandrake release (8.1), it worked fine with RedHat (7.2).
Of course if you were in that situation, you must not have noticed.
Bug or no bug, my machines have been running just fine. I bought them based on reviews that showed them running circles aroung Intel and they did. At the speeds the newer machines run, I'd hardly notice if they were hanging.
DMCA, Hollings, Palladium. What might have sounded like paranoia is now common sense.
A lot of your market share is there only because we who use Linux® have stuck by you. We have been ridiculed because we are using an "off-brand" processor, we've rationalized a way thermal problem's and fragile cores to get the benefit of more bang for the buck. We have suffered through inadequate compiler support, until your market share has grown to the point where an honest push onto the main-stream desktop is possible.
And what do we get for it, no real support, write your own fix, no; that we can, and often do. What we got was forgotten, you didn't even tell us. We are used to and demand full disclosure, and in real time. Linix people hang their dirty laundry out in public to give everyone a fair and equal chance at a fix.
We're often treated as a minority because we are, but treat us as a second class minority at our own peril. In short don't ever let the marketing weenies convince you to hide something from us; if we wanted to be treated that way we would use Win/Intel products
Apocalypse Cancelled, Sorry, No Ticket Refunds
I ran a T-bird 900 with a GeForce3 for awhile on 2.4.17 using NVagp and never had one bit of a problem. Now I have a XP 1700+ and still have no problem, though i've switched my board from a kt133a to a kt266a and have to use agpgart because the NVidia driver dosn't support my chipset. Still perfectly stable (i've noticed one or two graphical glitches in glx apps lately but never a lockup or a crash)
Hey moderators, don't waste your points modding this AC up to +5,
It's not a waste if the content of the comment deserves it.
that's a total of 6 points
No, ACs start at 0. It takes 5 points to get them up to Score:5.
AC's don't get karma remember?
And neither do experienced users thanks to the karma kap. Karma determines only who gets to moderate and who gets to post at 2. It does not equal penis size. In fact, since Slashdot upgraded to Slashcode 2.2 with a messaging system to tell me when I've been modded or replied to, I haven't even looked at my karma.
Will I retire or break 10K?
So, if it was discovered over a year ago, was this hardware bug ever fixed? We bought a dual-athlon 1.53-GHz (1900+?) machine recently; do these processors still have the bug?
I certainly wouldn't mind bashing AMD, and not just for broken processors.. Their whole socket A platform is just plain unreliable.
They just don't have critical people taking a stance against them, like Intel, so AMD never has to recall anything.
I'd always assumed that it was just a crappy AGP implementation on my no-name motherboard, as I'd been following the Mesa/GLX groups for a while and hadn't seen the problem mentioned all that much. It's nice that there's a relatively easy fix for the problem. Maybe now I can get back into Tribes2 again :-)
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
For example, you can pass around 8-byte structures in a single register, which is damn useful given the lack of available registers in the x86 architecture.
And when you want to use or change one byte in the structure, what do you do? Shift it out and put it in another register. You can beat the "lack of registers" argument by switching to any current architecture but x86; you'll get at least 16, most likely 32, or even 64 registers.
And with the 64-bit representation, you can do this with just one subtraction and one branch rather than a combination of two subtracts and two branches.
One problem with your algorithm: one subtraction will "carry" over into the next because the processor assumes you're subtracting whole integers. What you want isn't really 64-bit integers but rather vector SIMD as found in MMX, SSE, and 3DNow!. In fact, AltiVec on the G4 processor is 128-bit.
Will I retire or break 10K?
I bet it will be Tom Daschle.
You lose, fuckwit. Even if Bush fails to get reelected, the new President would take over Jan 2005.
You eurotrash are so stupid.
Just wipe Linux & run a *BSD.
Could somebody with more knowledge explain why you need 4MB pages in the first place? Pages are supposed to be small for a reason. With 4MB pages, internal fragmentation would go through the roof. It's almost like not having paging at all. I don't understand why this option is even available and used.
___
If you think big enough, you'll never have to do it.
I finally throw away my old P-100 with the division bug and buy an Athlon, this happens.
I find it rather interesting that for Win2k, you needed to install a patch. For Linux, you can just edit your bootloader with an option, and it does the same thing. Which seems more robust?
Granted, the Win2k patch was probably just a registry tweak, but which could the average user do more easily? Which operating system gives more information to it's users?
My beliefs do not require that you agree with them.
I'm going to have a G400, but that's because I'm moving a card over from my main machine that's a P3-600 until I can afford another card. Most people getting an Athlon are looking for maximal speed (Who isn't?) so they're going with the NVidia cards because they're "fully" supported with all functionalities including T&L supported (The Radeon doesn't have T&L right at the moment and the top of the line one is a different card w/no support right at the moment...). Most of the Athlon crowd is going to have NVidia cards unless they're insistent about having everything Open Sourced. There's nothing wrong with that position, but since the profile indicates that there's not going to be as many people with other cards, how would they see other AGP cards having this problem?
I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
I've always been an Intel-supporter. At least their chips don't burn up if your heat sink falls off. And their power consumption has generally been half of AMD's chips.
I avoided the early AMD chips because of compatibility issues. However I was planning on trying an AMD Duron chip because I thought that AMD had a decent chip out now. Guess I'm wrong...
Buying AMD will eventually bite you in the ass somehow someway.
Go ahead...flame me.
I also noticed this problem just this weekend. My fiance started to enjoy playing the game (tuxracer), but it would hang the entire system once in a while. However, I've got a 933MHz pentium III, with a geforce2 mx (and using the nvidia accelerated GL drivers for that board, not the ones that come with XFree86)
Obviously, this can't be the same problem, but perhaps related in some way?? I've never had my system just completely hang (can't change virtual terminals, or ctrl-alt-del) before.
All in favour, say "Aye!"
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
Recently purchased 2 XP 1600+s (1 in Dec and 1 in Jan) - both indicate they are Rev A5 (CPUID 662) and do not have the INVLPG bug according to AMD's errata sheet.
Yes, UltraSPARC's run significantly slower in 64 bit mode. IIRC, this is because it takes more instructions to load 64 bit constants and access 64 bit pointers. This is not true of all 64 bit processors -- and it is not true of x86-64.
The x86-64 architecture allows 64 bit programs to take advantage of the extra precision (and doubles the number of general-purpose registers, which x86 desperately needs), without forcing them to take the performance hit of using the full 64 bit addressing. It also adds a new, IP-relative addressing, which makes position-independant code (ie, shared libraries) much more efficient. There will be an increase in code size (and possibly a performance drop, but this depends on how AMD implements the 'movabs' instruction) when you start using more than 4GB of data. And, when you start using >4GB of code, things get yucky (requiring indirect jumps).
But, the point is, x86-64 will run all your 32 bit x86 code at full speed, and if you're able to re-compile your programs for 64 bit mode, you should get a performance boost, if only from getting 9 more registers (8 + no longer need to keep a pointer to the GOT).
RedHat 7.2 is a flaming piece of shit! If it's not busy corrupting the ext2 filesystem, it's locking up on __pollwait calls! The entire machine locks up! What a flaming piece of dogshit! Absolutely perfect for AOL to buy! What a stinking, flaming piece of rotting dogshit!
Ok, I just found out about this today, this is probably old news, but I'll post it anyway in case someone missed it.
http://nvidia.netexplorer.org
The average user could most easily install a patch... Duh.
--sdem
The other day I left my Dual Boot system (with a Nvidia GeForce 2 MX 400 and NVIDIA drivers) booted into Mandrake Linux for most of the day and it was fine. Of course I was at the system for most of the time. I decided to go to the store and when I came back the system was locked tighter then a drum. No big deal since I run ext3 for the file system. Rebooted and it was fine. How would one add this option to a GRUB bootloader?? I bet if I add it, the screensaver won't lock (Open GL screensaver.....). I don't play a whole lot of games so the texture flakiness would not bother me.
Gorkman
First off, yes, this is a rather major bug.
But is it enough to warrant not buying the processor or flaming AMD???? Hardly!
EVERY piece of hardware out there has some bug in it! Have any of you ever sat down and read the list of errata on Intel parts and the list of how many flaws are fixed in each stepping? The list of bugs fixed over the life of the P3/Celeron core is a rather lengthy document to say the least.
And I can't really fault AMD at all on this one other than that they HAD a bug...for Win2K etc, they released a fix/patch in very short order and notified everyone rather quickly.
And don't forget this was back in 2000! What version was the norm for deployed kernels back then (over a year ago!)???
From what I gather, the 4Mb AGP paging didn't show up until kernel 2.4 builds -- which I do not think were final at that time. Regardless, I feel the Linux kernel community should have been a bit more proactive in noting a DOCUMENTED bug and correcting for it.
Regardless, this bug in no way affects whether or not I would buy an Athlon/Duron. It is basically trivial to workaround and results in almost no performance loss. In essence, my Athlon XP 1900+ with the fix will still beat the crap of most P4 2Ghz machines in 90% of all applications (for half the price).
This is basically a failing of the entire Linux concept more than a failing of AMD.
Is there any central authority who regularly checks AMD, Intel, Via, Transmeta, etc. erratum sheets for bugs that might potentially affect the kernel? Based on this, I strongly doubt it.
Don't get me wrong, Linux is a great OS, but the lack of centralized control and build management is starting to cause problems. There are so many changes to different modules that version dependencies crop up all the time and no one is managing them.
I am not a big fan of Microshaft myself, but I would put money that they have at least one or two people whose job is to do nothing but monitor the processor manufacturers erratums to make sure no major problems submarine the sales of Windows XP! Bill Gates may be many things, but stupid is not one of them. H*ll, if I was Microshaft, I could have a marketing field day on this one -- it could be a very persuasive argument to lots of upper management types as to why Windows is better than Linux.
Is this bug a problem? Yes.
Was the original problem AMD's? Yes.
Did they address it and notify people? Yes.
Did anyone in the Linux community actually notice? NO
Regardless, any bug that can be worked around this easily is not THAT big a deal people...but it does point out some serious flaws in how Linux kernel development is managed. If Linux is to survive, some order had better start arising out of the spiraling chaos!
So to sum up the appropriate response to this bug: LEARN FROM YOUR MISTAKES AND GET OVER IT!!!!!!!!
"The sky is falling! The sky is falling!"
sheesh...
Odd, but Windows 2000 was so unstable on an Athlon/Geforce2 system I built last year, that I could only use Linux on the box. Linux has never crashed, but Windows 2000 was blue screening constantly. Applying the patch some time ago, made Windows stable on it, so I could dual boot.
Odd that RedHat 7.2 didn't seem to stumble over this bug.
Yes, everyone knows CmdrTaco drove away all the women long ago. Slashdot would hardly be a good place for him to find new sex partners if there were women here.
As I remember, SuSE was the people being paid to make the 64 bit AMD patch effort.
They have the 'cozy' relationship with AMD.
And yet, little gentoo found the 'feature'.
Does anyone know if registered and/or ECC ram help? It seems that if this is a problem of memory corruption, something like ECC ram could at least reduce the chances of corruption.
you're obviously an ignorant moron who has never used an AMD system that was set up on a decent chipset
- what proccessor rev its fixed in. I'm wanting to buy a new machine, it's still gonna be AMD, but I don't want a processor with that bug, as I am a big gamer.
- how to tell if my processor is affected. (I'd rather not have to wait for my system to crash to find out)
Do not spread "09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0" over the internet, thank you.
Errata is already plural ;-)
Erratum is singular
After hearing Alan harp on nvidia driver bugs and them actually being the catalist for his "poluted kernel" flag, I'm sure it took quite a bit of work to get AC to not dismiss this as yet another nvidia problem...
Below is a letter I sent to AMD (and post it on various AMD/hardware sites) regarding the differences and similarities between MP and XP.
... The P value are active low"
The problem is propagated by AMD's conflicting ignorance, and they are doing nothing about it.
AMD better learn that if they want to play in the big leauges, technical documents should be treated like the bible, because some of the consumer's are also developers.
"
The current, accepted belief by some of the more influential hardware internet sites, and magazines (pcmaximmum) is best represented by a quote on anandtech.com
"The current Athlon MPs that are officially validated for dual processor operation are actually no different than their Athlon XP desktop counterparts.
There is one small exception to that statement and that is in regards to the L1 bridges on the most recent CPUs that implement the new organic packaging.
As we pointed out in our Athlon XP 1900+ article, the L1 bridges on desktop CPUs are actually cut from the factory while MP CPUs aren't cut, the bridges simply aren't connected."
Most AMD users are both performance and money conscious (you guys have a great product), and as a direct result, there is a growing number of consumers influenced by the internet media and also their wallets into using XP in SMP configuration. But some of the consumers seduced into using XP in SMP might start questioning (unfairly) AMD's CPUs' integrity/stability when they start experiencing problems with XP in SMP. Who is to blame? I don't know!
I believe that this is contrary to AMD's intentions, and for the last few weeks I've attempting in different forums to show that MP and XP are technically different, therefore XP should not be used as a replacemen for MP in an SMP configuration.
Besides the L1 locked/unlocked difference, I documented 3 other differences between MPceramic, MPorganic, and XP.
1. MPceramic has an FID_Change state, MPorganic does not have an FID_Change state.
2. MPceramic has an FID_Change state, XP does not have an FID_Change state.
3. MPceramic/MPorganic has 8 SCHECK pins, XP has this corresponding pins as "Not Connected".
Questions/Observations:
1. Is there any documentation on the FID_Change?
2. Two different sources (first source a "second-hand" source inside AMD, second source using a multimeter) confirm that the 8 SCHECK pins on the XP are indeed connected to something, therefore they are not "Not Connected". Are the 8 SCHECK corresponding pins on the XP in fact functional, therefore connected?
In a further attempt to show a difference between MP and XP, I compared the registers on the "PCI Bus: 0 Device : 0" between a system with 2x1600XP and a different system with 2x1600MP. There were 16 registers with different values, 13 due to different hardware configuration, but 3 registers might be due to different processors:
offset 0x04 bit 8:
System Error Enable
offset 0x18 bit 7:
Reserved bits, not documented - different in XP and MP
offset 0x50 bit 20:
Fixed bit (Read Only), defined in the docs as "P transitor strength Value -
Questions:
1. Could NMI errors be the result of XP's disabled SERR bit?
2. What sets and/or determines the the value in the 0x50 bit 20 (Read-Only)? (cpu, chipset, bios, or something else)
3. How can the chipset differentiate between MP and XP, if AMD's own cpuid routine which I assumed is based AMD Processor Recognition Application Note, cannot differentiate between MP and XP?
In light of the previously mentioned reasons, an almost unanimous internet voice advocating (contrary to AMD) that MP and XP are identical, an ever growing group of consumer using XP in SMP, and an ambiguous AMD statement found in http://athlonxp.amd.com/overview/keyFeatures.jsp
"266MHz AMD Athlon(TM) XP processor system bus enables excellent system bandwidth for data movement-intensive applications
Source synchronous clocking (clock forwarding) technology
Support for 8-bit ECC for data bus integrity
Peak data rate of 2.1GB/s
Multiprocessing support: point-to-point topology, with number of processors in SMP systems determined by chipset implementation
Support for 24 outstanding transactions per processor"
I think it would be in the interest of all parties, both current and potential SMP/AMD customers, and AMD's own reputation, for AMD to clarify once and for all what are the technical differences between MP and XP.
"
Of course, you need to run lilo before you reboot.
//FIXME: Bad
What irks me is this: I got hit with this bug. I posted bug reports to Debian, with NVidia, on different forum, report lock-ups in certain open-GL situations. I got generally hand-waving "read the fucking manual" responses.
As the article notes, this isn't just a problem with AMD. It suggests that there's an ongoing problem with troubleshooting and resolving the sorts of issues that desktop users are going to have in Linux. (And "paying for support" would not have resolved much, would it have? The problem is the lack of coordination, not the lack of money.)
I'm sure the average user is more likely to type in a boot loader option than double click a patch. Yes, you're absolutely right.
I've posted this elsewhere but to clarify - it looks like this will still happen regardless of which processor you have selected (even i386!). This is because the test for whether your processor does pse seems to be run on startup (I think it's done by arch/i386/mm/init.c __init pagetable_init).
As an aside, as far as I can tell the only (extra) things that optimising a kernel for a K7 seems to set are gcc options (someone please correct me if I'm wrong).
I think the k62 had this problem as well. Anyone know about that?
Spring is here. Don't believe me, look outside!
It's rather hard to read non-existent documentation. This bug isn't listed in the AMD K7 errata, which is why it wasn't found - the only 'documentation' for this is the Win2k patch that AMD provided.
Linux and *BSD just do things differently: it's not a matter of one set of hackers being better than the other.
himi
My very own DeCSS mirror.
I've seen a number of mysterious X freezes in XFree86 4.1.0 and earlier on my Athlon/GeForce2MX system with NVidia kernel/X drivers. Most often the X server just seems to lock up when I'm doing nothing in particular. Occasionally I've had the whole system freeze during 3d gaming.
This is all with Linux 2.2.18. Has anyone commented for sure on this bug in the 2.2 series?
- jon
Ganymede, a GPL'ed metadirectory for UNIX
Maybe this would explain the extreme flakiness of my box. I've searched and troubleshooted high and low for a solution to the constant crashing and hanging of my system:
ASUS A7A266
512MB Crucial DDR
Athalon 1.4GHz (266FSB)
Nvidia GeForce2 GTS 32MB
Red Hat 7.2
However, it was difficult to pin down the culprit and now the problem *has* been fixed proving that the the decentralisation of Linux does work, albeit slowly when there isn't outside help. I suppose you can point to FreeBSD as an example that management does help but even over there not everyone knows about it and mistakes are made.
The problem was nobody knew exactly where this was happening. Things like the properitry NVidia drivers are frowned upon for not being open (fair enough - it makes it more difficult to tell where bugs are) because it's difficult to prove they are not buggy. Ironically, it was these drivers that were helping to show up this bug. In the end it took people from within NVidia who could check their own code is correct to file this bug simply because they were in the best position to verify it.
Not to sound stupid but does it affect XP?
The list off affected is: Athlon/Duron/Athlon MP
No XP in the list so am I to assume I am safe?
Looking at this post it seems like all but the very first and the very latest K7s are affected.
I dunno if I've had crashes because of this bug but I have definitely seen some weird polygon corruption (in Mesa gears sometimes a poly would come loose). After implementing the workarounds I haven't seen again...
Take a look at page 7 of the AMD AthlonTM Processor Model 6 Revision Guide.
Guess the hackers missed this one...
I think you are missing the point here. Does a Win2k user have to be connected to the internet in order to fix their system? Yes. Does someone on the Linux system? No. Imagine you manage 100 machines. Which would be easier to fix? Push out lilo.conf files to the Linux machines, or install 100 patches?
My beliefs do not require that you agree with them.
First, as has already been pointed out, there is no performance hit.
But I still did not get the answer to my question. What is the purpose of having 4MB pages in the first place? It is inconceivable that an OS would use 4MB pages exclusively. The internal fragmentation would be enourmous.
To give you an analogy, think of what would happen if your file system used 4MB blocks. When you create a file, space would be allocated 4MB at a time so a 1 byte file would waste (4MB - 1byte) of disk space; (4MB + 1byte) file would take up two blocks, also wasting (4MB - 1byte) of disk space. On average, each file wastes 1/2 of the last block. Similarly, each process wastes on average 1/2 of the last page. That's not a problem if the pages are 4KB in size, but with 4MB pages there's lots of space wasted. That's like throwing away paging altogether.
So, I ask again, what is the point of having 4MB pages?
___
If you think big enough, you'll never have to do it.
It's a registry patch. That's all. If you have multiple machines on a network and the users log into a domain, you can trivially write a batch file that will apply the patch. The difficulty of placing this patch is going to be entirely dependant upon each specific situation.
The only way linux/freebsd/etc. will see this as being an easier situation is if in the future they make detection and application of the problem an automatic feature of the OS. MS could do the same, but the question is will they?
Here's the stark truth for you: 1)Money, 2)Userbase.
Remember when Corporate Enemy #1 was singing something to the tune of, "Whenever there's a problem, you don't know who to blame?", and how The Community laughed it all off as FUD? Now you can see that whenever there's a problem, you don't necessarily know who to notify, either. Don't call it a feature one day and then curse it the next. That sounds all too much like somebody else...
Wow, what a bunch of FUD. I've never had a thermal problem, never had a "fragile core" and never suffered from "inadquate compiler support", whatever that is. My new XP system seems to get stuck every now and then, but it's a new system and I've probably done something stupid like make my swap file much too large. My k6/2s and my Athlon perfom better than their more expensive Intel counterparts. According to reviews the XP system sould work just fine when I finish ironing it out. Other people have made it work and so it will work for me too. AMD does math cheap and better than Intel. Gaming? That's not my bag, but others are reporting good results.
When you look at the support AMD gives the Widoze world, you have to remember that those who suffer under M$ OS NEED the help. Just check out the utilities offered at their site. AMD CPUID? cpuinfo gets that for me. They rushed out with the goofey win2k utility because Windoze users can't pass information like, "no_pentium" to their kernel or recompile it. I'm no kernel hacker, but the AMD documentation site looks informative.
Yeah, they could have been nicer about it, but I'm not about to give up on AMD over a video bug. The short answer is that this looks like an error of ommision that could occur in any large organization. The folks in the Windoze software branch, asside from having goog feelings toward M$ by the nature of their jobs, might not know who to contact to get the word out to the Linux world. Does AMD even have a Linux division?
We're often treated as a minority because we are.
Another beautiful flame disguised as advocacy. It's neither true nor right. There are now more Linux developers than there are M$. I refuse to accept immoral or offensive behavior for myself, a minority of one. Fortunatly, there seems to be none of that here, at least not intentionally.
Friends don't help friends install M$ junk.
1. delete your partiton table
2. install netbsd 1.5.2
3. install more things
4. repeat
Apparently, if you'd believe the Linux community, you'd be hard-pressed upon where to place the blame. You see, the Linuxist Manifesto's number one rule is to lie to protect the best interests of Linux. No self-respectable Linux zealot would insult or place blame upon AMD, because AMD's philosophy centers around tackling American Corporations with their Asian sweatshops, selling their chips at bargain-basement prices like the Red Menace Commies do with their Wal-Mart shit.
So, right about now, you're probably thinking that the zealots are clearly in a dilemma. Who are they going to blame? If you have a prediction before I tell you, the poll is on the right. Or maybe the left. Either way, take your pick.
You'd think that the parasitic community would place blame upon Microsoft, right? Alas, Microsoft has had the bug patched since September 2000. Not only that, Windows XP , the latest in the suite of high-powered, stable operating systems from Microsoft Corp., has this patch built in. That's right, built in. Keep in mind that Windows XP was released in October 2001, over three months ago. Meanwhile, no one knows what the hell Alan Cocks has been doing since then, since he hides under the cloak of secrecy. nVidia has been informing users via tech support, even to the Linux community, how to fix the problem for months now. Clearly the blame is upon Alan Cocks's shoulder, but to place the blame where it is rightfully justified is inexcusable in the Linux community. The drones are in disarray.
The actual bug occurs when Linux users contract the Tux Racer virus via KEmail. When first run, Tux Racer enables a feature in your third-world sweatshop AMD processor called "extended paging." Now, I know you're probably thinking that this sounds like some sort of Nokia feature. Well, you're wrong. It's yet another feature that AMD illegally hacked from Intel. It allows your browser to seamlessly view pages up to 4Mb in size. Before its introduction in the early days of the Intel Pentium processor, web pages were broken up into 4K segments, because any pages larger would freeze the computer. That's why Microsoft didn't invent Javascript until after the Pentium, every time they went to use it, their pages exceeded 4K, and henceforth froze the computer. Intel came to the rescue with the Pentium line of chips, and, as usual, AMD got out their super high tech Asian hacking tools and "reverse-engineered" (code-name for 'illegally hacked') Intel's technology. Thus, users of the inferior AMD Cyrix Kx86-2 Now! processor could also view large web pages without crashing. So why did no one notice that pages larger than 4K would crash AMD processors? Well, Microsoft has had a fix for 16 months, like we mentioned earlier. But why did no one from the Linux community notice? Well, apparently, there does not exist a page devoted to Linux that is more than 4K in size. Since most of the Linux installations out there denounce color as 'feature bloat,' all Linux pages follow an unwritten oath to suck. Believe me, they all do.
So, for the good of Linux, you may now disperse. Head off to various tech sites and continue blaming Microsoft for not telling you sooner. Your community will thank you.
s/LSB/MSB/ obviously
--- Hindsight is 20/20, but walking backwards is not the answer.
NO!!
...and in the chair's opinion the nos have it.
I have an AGP Nividia Geforce 2 MX, and an AMD K6-3 333 MHz. I have experienced these memory corruption, graphical anomolies, and lockups in linux and windows 95.
I noticed that AMD K6-3 was not mentioned, but it has to exist on it. The K6-3 was made with the same instruction set as a pre-Athlon. Thus the bug definately exists.
Not sure about K6/K6-2, but it is possible.
NVidia has made it clear, on numerous occasions, that they don't care about Linux. The only reason they have any sort of Linux drivers is because a couple of internal techies do care. You'll get a couple in every company. However, NVidia as a whole has repeatidly state that Linux users should go f- themselves.
this is so much a problem on my AMD XP that i can not install the nvidia drivers on it at all without the system crashing every 10 minutes at the drop of a hat. i have this problem on my dual AMD 1800MP but it is far less an issue, as it only seems to crash occassionally during screen savers and very rarely during a game of wolfenstien. on both ssytems i was using the 2.4.9_13 kernel and smp kernel respectively with nvidia drivers 2314 built from src.
You seemed to have missed that it's a registry setting -- aka a configuration file entry. Fundamentally the same.
The Windows "patch" just changes a registry key, so the correct answer to your initial question is No, a Win2K user does NOT need to be connected to the internet (other then to figure out just which key to change in the first place, in which case a Linux user would also need an internet connection to figure out which line to add to the bootloader).
The only really valid point I see against Windows in this situation is that the registry has essentially no documentation! There are TONS of settings and customizations available within the registry for Windows, but essentially nobody knows even 1/10th of them because of lack of documentation!
Alan Cox and other kernel hackers do read these documents. The question is if AMD documented this bug in their errata, or just fixed for Windows 2000 and figured that was good enough.
Bug #16 in AMD's Errata list for the AMD Athlon Model 6 processor (ie the AthlonXP/MP) lists the following:
(Begin quoting)
16 INVLPG Instruction Does Not Flush Entire Four-Megabyte Page Properly with Certain Linear Addresses
Products Affected. A0, A2
Normal Specified Operation. After executing an INVLPG instruction the TLB should not contain any translations for any part of the page frame associated with the designated logical address.
Non-conformance. When the logical address designated by the INVLPG instruction is mapped by a 4-MB page mapping and LA[21] is equal to one it is possible that the TLB will still retain translations after the instruction has finished executing.
Potential Effect on System. The residual data in the TLB can result in unexpected data access to stale or invalid pages of memory.
Suggested Workaround. When using the INVLPG instruction in association with a page that is mapped via a 4-MB page translation, always clear bit 21.
(end quoting)
It's there. It's been listed there for quite some time. No one read the errata and/or no one bothered to check to see if this one affected Linux systems. I hate to break it to the Linux boys, but they kinda missed the boat on this one. Normally Linux kernal hackers seem pretty good at staying on top of processor bugs, but it looks like this one slipped through the cracks.
FWIW, anyone looking for this errata list can find it here. As a bit of an aside, none of AMD's PDF documents will load for me in Mozilla/Netscape 6 with Acrobat 5, but they all work fine with IE/Acrobat 5. Wierd.
i've been using an athlon (slot a) cpu for more than a year now, with all 2.4 kernels (except for the REALLY broken ones) and i haven't had any such problem at all. i used matrox agp cards (g400 and g550), so shouldn't it crash here too? quake3, castle wolfenstein and a lot of other opengl apps work perfectly well.
which part am i missing? is this problem somehow nvidia-related after all?
I would say yes, since the 2.2 kernel also uses these Pentium big pages:2 .2.19#L302
http://lxr.linux.no/source/arch/i386/mm/init.c?v=
We also meet systematic freezing with XFree86 on our Athlon+Ati/AGP.
Nevermind, just saw the "workaround" listed in the article.
STOP MISUSING APOSTROPHES, YOU MORONS!!!
I can't understand what "CPU" bug you are talking about. Could somebody tell me where's that bug? As far as I'm concerned, the trouble is our dear kernel trying to get those 4Mb pages found in Pentium and not in Athlons. Now, why everybody call this a BUG????? I think this is just a "NOT supported feature". Maybe should a say I've found a bug on the new Pentium IV. They can't work with "3D NOW!" optimizations!
But seems I should have. I have played Tuxracer many times, and while I can't say I'm good at it, I haven't had my system lock up even once. (It did this on a nearly daily basis with several different clean installs of MicroYouKnowWhat Windows 98! Hence the reason I switched.)
/proc/cpuinfo" and I have 6/4/2, model 4 of the CPU so I should be having the same problem and haven't noticed it. Hmmm...
I have a custom built (made it myself) with the following:
Red Hat 7.2 (kernel 2.4.7) running a nearly standard install on an AMD Athlon 900MHz single CPU in a Biostar MB with VIA chipset.
I use an ATI All In Wonder (Rage 128 based) AGP card with 32 MB of memory, and 4X AGP enabled in the BIOS. I have 768MB of PC133 memory installed.
The only thing I've noticed so far is my fresh install of Netscape (anyone notice how NS resembles M$? Maybe with AOL considering a penguin dinner we should just call them N$... when I read that story I thought "I JUST BOUGHT THE THING!") anyway, N$ ver 6.2 likes to crash, which is too bad. Mozilla does not, that I've noticed, and I like that Mozilla allows me to right-click images from advertisers and block their transmissions, which as far as I know NS does not offer... I'm uninstalling all N$ on my box momentarilly...)
But to get back to the subject at hand, I did "cat
~ a newborn Penguinista Mozillite StarOfficer.
And I understand that most computer users WANT this. If there is some problem with their magical computer thingy, they want something to just fix it. That is part of the real problem here, which goes way beyond this particular issue, that people are patching their systems with blind faith that the patch will "fix" whatever is wrong. Was the name of the registry setting provided? Can you go in and change it manually if you wanted to? I am guessing that it wasn't.
I am no zealot. I understand that things need to work a certain way in the computer world, just because not everyone is comfortable with computers. But it is my machine, I want to know what is going on with it.
My beliefs do not require that you agree with them.
If what you are saying is true
"As it turns out, AMD did eventually get
around to fixing this issue with Stepping
A5 of the AthlonXP/MP core."
then we have a real problem here.
You see, Alan Cox and friends are planning to make Linux "recognizes" Athlons, and do a special case - the "nomem" thingy - on it.
But if the Stepping A5 of AthlonXP/MP core has the bug licked, then, the "nomem" thingy by Alan Cox et al may be a step backward.
Unless of course, the kernel hackers want to have a double-checked thingy on their "Atholon finder". Such as
If Athlon=step5, then do nothing.
Muchas Gracias, Señor Edward Snowden !
Slightly off-topic, but...
How often are 4M pages useful? I guess the whole kernel could be in one page, but where else is this useful? I bet most applications would never see any benefit from 4M pages anyway.
Patrick Doyle
I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
Update to the previous message:
I can confirm that the option mem=nopentium
given to the 2.2 kernel
allows us to use Xfree on our Athlon without
freezing.
In fact, I do not understand why everyone is talking about a *2.4* bug.
This is a Athlon/linux bug more generally.
Since Alan Cox is working on automatic workaround,
and since he is the 2.2 maintainer, I think we 2.2 users should not worry too much.
Then read the KB article that is associated with the patch. There is your documentation as what the patch is doing. Here is the link for you....
f search%2fviewDoc.aspx%3fdocID%3dKC.Q270715%26dialo gID%3d1928924%26iterationID%3d1%26sessionID%3danon ymous%7c1700360
http://support.microsoft.com/default.aspx?scid=%2
Microsoft makes it a policy to write one of these for every patch it makes. So RTFM ok? (sorry couldn't help myself..at least I told you where in the manual to read)
Silly Rabbit...Sig's are for kids.
And using regedit, you can change it manually, too. You can add keys and values and screw things up like a 5 year-old with root, if you like.
The criticism of the registry model that is valid is two-fold: 1, it can be corrupted like any file, but since it is one file and not a directory like /etc, that can muck up your whole system (the registry can still be backed up and reinstalled) and 2, it is somewhat easier for malicious code to muck with the registry, since most Windows users work in some privileged mode.
I built a K7S5A system for a friend, at the first go it couldn't install Windows, it turned out we had faulty RAM, so we replaced it, but problems persisted, went to the shop to had the thing looked; the motherboard was faulty. Got a new motherboard but even that didn't go smoothly. After spending 3 hours getting Windows installed, the system rebooted by itself and couldn't get back into Windows because of a corrupted registry file. I looked on the internet, and found this forum and it turns out the problem is widespread. Read especially this FAQ. K7S5A, blah.
What time is it/will be over there? Check with my iPhone app!
Not surprised they are junk? They are most definitely NOT junk.
You, however, are an idiot who knows not of what he speaks
Care to read the list of errata on the Pentium 3 or 4? Its quite a volume and most bugs are of equal severity to this or worse.
This bug is only a problem in certain rarely seen circumstances that happen with AGP transfers using large page sizes -- which apparently only Nvidia seems to do in their drivers.
And disabling the feature in the kernel is trivial and affects performance almost unmeasurably. And the bug was known and documented and fixed under Win2K over a year ago. But, as the large paging feature wasn't used under 2.2 Linux kernels, it didn't apply then and slipped through the cracks because the Linux kernel teams didn't apparently read AMD's errata sheets well enough. This is a failing on the part of LINUX not AMD.
Of course if you look at the old Intel P3 1.1Ghz processor, it wouldn't even COMPILE the Linux kernel without crashing. They had to actually recall the part....hows that for stability???
The average user is probably more capable of going to the Windows Updates website, clicking on the tick box and hitting 'Download' which then runs the install.
The typical computer geek is probably equally capable of editing the bootloader or a registry, but prefers the first.
Your question was kinda like asking "Which could the typical person do easier. Build a rocket to goto the moon, or build one to goto Pluto?"
For the typical person, neither is possible.
Rod Taylor
ALright, but the mem=nopentium still doesnt work, at least in my case. Not only do I have mem=nopentium, but I also have BIOS AGP set to 2x, Option "NoRenderAccel" "true" in XF86Config, and Option "NvAGP" "0" in XF86Config (basically totally disabling AGP totally anyway). Despite all these safeguards, sure enough, graphically intensive programs (including an idle X desktop) hard-crash the kernel. Anyone else still experiencing this? I didnt have to wait long either, the system crashed within seconds of opening Quake 3 while I was still navigating the game menus.
I have expereienced that myself. I put Mandrake 8.1 on Duron 900 with DDR ram in have experienced inexplicable lockups. just my 2 cents
"Congress shall make no law... abridging the freedom of speech, or of the press"
Moderation Totals: Flamebait=1, Insightful=2, Interesting=1, Informative=1, Funny=3, Overrated=2, Underrated=1, Total=11.
I think I'm only missing 'troll' and 'offtopic' and It would have been a full house.
If I remember correctly, to enable 64 bit operation on an UltraSPARC 1 cpu (such as that in an Ultra 1 workstation), you need to upgrade to OpenBoot 3.11.1 at a minimum, and then uncomment the line in /platform/sun4u/boot.conf that says this: ALLOW_64BIT_KERNEL_ON_UltraSPARC_1_CPU=true.
I don't know exactly what the bug is with the old UltraSPARC 1's, except that given specific hand-written assembly code, it is possible to lock up the machine.
I have been running mine on the 64 bit kernel for some time now, and haven't noticed any problems, so it's probably safe in most circumstances.
mpb
man tunefs | grep fish
How does Abit try to overclock? How does Abit push too for? Just because they provide you with the means to push your CPU past its ability, doesn't mean you have to do it. It's your fault if your CPU is overclocked to a point that it becomes unstable.
Abit has never let me down. 4 out of 5 machines I am currently running at home use Abit Mobos. None of them have given me a problem that couldn't be solved with minimal effort, and a majority of those problems were my fault for trying to push too far, and even then it wasn't Abit that failed me, it was the hardware I had attached to it that couldn't handle what I was trying to force it to do. I like Abit because they give me the ability to push my systems to the edge of the envelope and beyond, but it is stupid to say that they suck if I push past the edge. Besides that, Abit provides better documentation on their products than any other manufacturer I have ever seen.
That third article about the supposed "HCF" instruction on the 4004 is completely and utter BS. None of the instructions on the 4004 will cause it to burn up, even on the earliest production parts.
When the IBM System 360 series came out it had a large number of new opcodes (as compared with the 70x/70xx series). These were the days of CISC (Complex Instruction Set Computers), and the 360 really lived up to the name. It gave over a large amount of its word space to opcodes and opcode extensions, so it had a VERY large potential opcode space. Much of it was unpopulated, but some was populated with undocumented instructions. Further, the machine was microcoded, and the microcode was loaded when the machine powered up. (That's what floppy disks were invented for.) So the company could write new opcodes and add them later.
Of course the new machine with the ENORMOUS list of opcodes and (true) rumors of hidden undocumented opcodes quickly lead to the circulation of a humorous list of perhaps 20ish additional "new undocumented opcodes". Things like XOE (Execute Operator Immediately), EK (Electrify Keyboard), SSJ (Select Stacker and Jam), BLNK (Blink Lights), WHR (Whirr), etc. The crown jewel of this list was HCF (Halt and Catch Fire).
While this list was still funny Motorola released the 6800 single-chip microprocessor, predecessor to 650x knockoff that formed the core of the first Apple computers. To ease chip testing, the all-ones opcode threw the chip into a test mode, where it continuously incremented the program counter and performed memory reads. This wiggled all the address lines and most of the control lines, letting you know if the chip was alive and bonded.
Of course they didn't tell you about it. And of course the only way out was hard reset. And of course a jump to an unpopulated region of the address space (i.e. most of it) would leave the bus floating and generate 0xFF. And of course jumping into random data or uninitialized memory would also quickly get you an 0xFF or jump you off into unpopulated address space. So the typical behavior for a program bug was to lock up the processor beyond the ability of a debugger to function.
(Hell: I had one of the first round of solder-it-yourself evaluation kits, bent a pin on the debugger ROM putting it into the socket, and ended up with a board that booted into the test state. Was starving student and it took a couple days to get access to test equipment to find out what was wrong.)
So of course programmers, once they found out about the instruction that hung the chip in a mode where it "twiddled its thumbs at maximum speed" and got a bit warmer than usual, and couldn't get out of the mode except by hard reset, quickly christened the opcode "Halt and Catch Fire". And this became the generic term for get-stuck-in-a-test-mode instructions on microprocessors, until the chip manufacturers finally came to their senses and stopped putting such instructions into instruction sets.
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
Yeah, the firmware patch came with the solaris CD set. I patched it during my first install after I got the machine.
Kernel's runnin' in 64 bit mode. Unfortunately, I don't know enough C to really take advantage of it like I want to, but I'm learnin'...
Those who can't do, teach. Those who can't teach either, do tech support.
Linux increasingly has both. IBM. Google. etc.
We NOW know that this is an AMD bug.
It was proper to assume the NVIDIA
driver was at fault though, because
this one closed-source driver made
debugging near-impossible.
Closed-source drivers are guilty
until proven innocent.
...just append the option to the end of your 'kernel' line. For me, it looks like this:
/vmlinuz root=/dev/hdb1 vga=5 mem=nopentium
kernel
Hope this helps!
And, for convenience, a rundown by the players involved (both for the Linux kernel and AMD) is here.
In short, for the reading-impaired, it's not an Athlon bug.
- I don't need to go outside, my CRT tan'll do me just fine.
It was obviously well known in late 2000 when I bought my system because there were registry patch fixes for windoze avaliable from AMD's site and now are avaliable on mobo manufacturer's sites too.
F4+80y +1++135
FatBoy Titties - (aren't I l33+