EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.

[yoman82]

The edac_amd64 module attempts to load on many systems. If the system doesn't have ECC
memory, or it is disabled in the BIOS, then the module prints

EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
    Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
    Might be a BIOS bug, if BIOS says ECC is enabled
    Use of the override can cause unknown side effects.

before failing to load. This won't cause issues for most people that see the message.

kerneloops picks this up as kernel problem as the "WARNING:" looks a lot like what
you get when using WARN().

There are several aspects to this issue:

  * linux
     - something attempts to load the module when perhaps it doesn't need to (unclear at this point)
     - the module looks like it is using WARN() when it isn't, and is arguably more SHOUTY than
       it needs to be.
  * kerneloops
     - picks up this as WARN() when it isn't.
     - Was accidentally left enabled for the stable release, people shouldn't be getting asked to report
        this at this point.
     - Isn't very good at dealing with repeat issues, causing more reports to be sent than are needed.

and possibly others as well.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: yoman82 3464 F.... pulseaudio
 /dev/snd/pcmC0D0p: yoman82 3464 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xf9ff0000 irq 16'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,18491e01,00100001'
   Controls : 37
   Simple ctrls : 21
Date: Tue Sep 1 07:48:00 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=69c64130-cc6f-4a5b-952b-3ba4c893ba48
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-8-generic 2.6.31-8.28
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: root=UUID=19f3bdd6-1b33-48e0-8081-d00e178d9f7d ro splash vga=792
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-8-generic N/A
 linux-firmware 1.16
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: 6.073813] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
Uname: Linux 2.6.31-8-generic x86_64
WifiSyslog:

WpaSupplicantLog:

dmi.bios.date: 04/24/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: M3A780GXH/128M
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd04/24/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A780GXH/128M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

http://bugzilla.kernel.org/show_bug.cgi?id=15238

[Leann Ogasawara (leannogasawara)]

I notice the following in your OopsText.txt file:

EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
    Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
    Might be a BIOS bug, if BIOS says ECC is enabled
    Use of the override can cause unknown side effects.

Could you check your BIOS and see if ECC is enabled or disabled?

[eXlin (hirvonen-henri)]

Checked bios and nothing about ECC, but maybe thats because i have non-ecc memory.
Dont think that on earlier kernels its tryed to load ecc module and then complaining that cant do it.

Can someone help how to disable that ecc module?
Thanks for advance ;)

[Dave Morley (davmor2)]

Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tester 3047 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfe028000 irq 20'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1019e601,00100002'
   Controls : 37
   Simple ctrls : 21
CurrentDmesg: [ 81.413041] eth0: no IPv6 routers present
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=afce901e-f703-43c1-afb3-b62acec0b28d
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Package: linux (not installed)
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=b29b36fe-88fa-4f90-8869-b9cf30716c72 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-10-generic N/A
 linux-firmware 1.18
RfKill:

Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/08/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: NF-M2S
dmi.board.vendor: www.abit.com.tw
dmi.chassis.type: 3
dmi.chassis.version: NF-M2S
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/08/2006:svn:pnNF-M2S:pvr:rvnwww.abit.com.tw:rnNF-M2S:rvr:cvn:ct3:cvrNF-M2S:
dmi.product.name: NF-M2S

[Koen Verweij (kfverweij)]

I'm having the same issue (bug 430547, I marked it as duplicate). Each time I boot Apport reports the kernel error 2-4 times (maybe the double reports is a separate Apport bug). Like asked before: is there a way for me to disable the ECC module. My motherboard, a Gigabyte K8NF-9, does not support ECC so I can not disable it in the BIOS.

[Koen Verweij (kfverweij)]

So there are about a dozen duplicate bugs of this now (bug 415381, bug 431039, bug 432905). Is this going to be looked at?

[Paul Cook (narkosen)]

By way of further information, this crashes disappears when the proprietary nvidia is driver removed (version 185).
When it is activated the kernel oops crash is reported by apport around 10-20 seconds after logon to the gnome desktop. It has occurred with both the x86_64 generic kernels 2.31.10 and 2.31.11.
Motherboard is an Asus A8N-SLI premium with 4GB non-ECC RAM and nVidia Corporation G72 [GeForce 7300 LE] rev 161 card. There is no option to enable/disable ECC in the Phoenix bios.
Hope this helps!

[Seth Hikari (sethhikari)]

I believe my RAM supports ECC but not when I clock it over 800 witch it is.

[Paul Cook (narkosen)]

Kernel oops continues as of 2.6.31.11.38, with or without nvidia driver loaded now!
However it occurs exactly 60 seconds after logging on to the GDM and seems to coincide with update-manager (Update Notifier) being loaded automatically under 'System->Preferences->Startup Applications (monitored using top in the terminal).

The workaround for me is to untick Update Notifier and use manually when required. Kernel oops then disappears!
Attached is the details from the kern.log when the oops occurs.

Is this an update-manager bug?

[Juan Tyson (juant)]

I have no ECC memory.

[Tim Wright (timw)]

Same issue. Yes, I do have the nvidia video driver loaded. I can easily try without. But this is *not* an oops, not a real problem, and apport should probably not be picking it up. The driver could do with being less verbose. As others have pointed out, a lot of non-server boards don't even have the option to enable/disable ECC in the BIOS. It was my impression that the NForce4 chipset happily autodetected and supported ECC memory without any settings being needed.

[oli z (oliver-z)]

for me it was an oops and the whole system freezes - and imo this is a big problem when my system freezes

[wayne pronge (waynepronge)]

Same warning message as fist op. No ECC in bios settings. amd64 X2 4200 Bios Award.

[Gerard Chabbey (jgchab)]

through the same computeur, upgrading from Ubuntu 9.04 and kernel 2.6.28 to Ubuntu 9.10, problems become with kernel 2.6.31 and nvidia 185: instable with gnome and many applets, crash and frezze. GC

[josesuarez1983 (j-suarez-agapito)]

I have the same mobo as narkosen.
This had not happen with previous kernels

[Juan Tyson (juant)]

This happed while using firefox. I recived three reports of failures.

[wayne pronge (waynepronge)]

With the new updates today to Kernel 2.6.31-13 Error messages are resolved for me. Karmic64 beta all updated.

[Koen Verweij (kfverweij)]

This still happens for me on an updated Karmic 64-bit.

[Tim Wright (timw)]

Still broken with the latest update, in fact worse than before. It is perfectly normal and expected that you can use either non-ECC or ECC memory with the NForce4 Ultra chipset, and it gets handled appropriately. This machine is working fine. The "EDAC amd64" driver is broken if it is treating this an an error. If it only supports ECC memory, then either it should not be being loaded or it should gracefully exit/fail with a statement to that effect.

[Pitcher (m-waechter)]

same here, after last updates today not resolved

[Harry (harry33)]

Due to posts 27 and 29 the importance should possibly be high.
This crash report really does come up even nothing is done manually after login, seemingly just by itself.
But I can confirm that the timing is exactly the same as the update-notifier comes up.

[bwallum (rbw2)]

This problem has just started with me, 17:15 gmt Friday 16th October, latest updates from main.

[Sam_ (and-sam)]

Karmic since two weeks (new installation).
First time it occured after an update (via Synaptic) and reboot today.
Message about ECC (Error Correction Code) was in the logs all along, but no Apport bug report till this moment.
System runs still stable.
History:
Since the message occured in logfiles I did a search on this and acknowledged the GUI system monitor showed 999,9 MB RAM instead of 1024 as before in Hardy. My BIOS also isn't capable of ECC. (Details of sys specs are in the uploaded Apport report)
Related message in logfile was:
Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.

$free
            total used free shared buffers cached
Mem: 1023932 980728 43204 0 59672 399912
-/+ buffers/cache: 521144 502788
Swap: 3478032 0 3478032

$free -m
             total used free shared buffers cached
Mem: 999 957 42 0 58 390
-/+ buffers/cache: 508 490
Swap: 3396 0 3396

As suggested here I ran MEM Test, passed without any errors.
http://ubuntuforums.org/archive/index.php/t-1084863.html

Only Synaptic was open during update.
Commit Log for Fri Oct 16 19:49:53 2009
apport (1.9.3-0ubuntu1) to 1.9.3-0ubuntu2
apport-gtk (1.9.3-0ubuntu1) to 1.9.3-0ubuntu2
apt (0.7.23.1ubuntu1) to 0.7.23.1ubuntu2
apt-transport-https (0.7.23.1ubuntu1) to 0.7.23.1ubuntu2
apt-utils (0.7.23.1ubuntu1) to 0.7.23.1ubuntu2
compiz (1:0.8.3+git20091005-0ubuntu5) to 1:0.8.4-0ubuntu1
compiz-core (1:0.8.3+git20091005-0ubuntu5) to 1:0.8.4-0ubuntu1
compiz-fusion-plugins-extra (0.8.3+git20090914-0ubuntu1) to 0.8.4-0ubuntu1
compiz-fusion-plugins-main (0.8.3+git20091006-0ubuntu1) to 0.8.4-0ubuntu1
compiz-gnome (1:0.8.3+git20091005-0ubuntu5) to 1:0.8.4-0ubuntu1
compiz-plugins (1:0.8.3+git20091005-0ubuntu5) to 1:0.8.4-0ubuntu1
compiz-wrapper (1:0.8.3+git20091005-0ubuntu5) to 1:0.8.4-0ubuntu1
compizconfig-backend-gconf (0.8.2-0ubuntu2) to 0.8.4-0ubuntu1
cups (1.4.1-4) to 1.4.1-5ubuntu2
cups-bsd (1.4.1-4) to 1.4.1-5ubuntu2
cups-client (1.4.1-4) to 1.4.1-5ubuntu2
cups-common (1.4.1-4) to 1.4.1-5ubuntu2
devicekit-power (011-1) to 011-1ubuntu1
evince (2.28.0-0ubuntu4) to 2.28.0-0ubuntu5
gnome-power-manager (2.28.0-0ubuntu6) to 2.28.0-0ubuntu7
gnome-settings-daemon (2.28.0-0ubuntu3) to 2.28.0-0ubuntu5
libcompizconfig0 (0.8.3+git20090901-0ubuntu1) to 0.8.4-0ubuntu1
libcups2 (1.4.1-4) to 1.4.1-5ubuntu2
libcupscgi1 (1.4.1-4) to 1.4.1-5ubuntu2
libcupsdriver1 (1.4.1-4) to 1.4.1-5ubuntu2
libcupsimage2 (1.4.1-4) to 1.4.1-5ubuntu2
libcupsmime1 (1.4.1-4) to 1.4.1-5ubuntu2
libcupsppdc1 (1.4.1-4) to 1.4.1-5ubuntu2
libdecoration0 (1:0.8.3+git20091005-0ubuntu5) to 1:0.8.4-0ubuntu1
libdevkit-power-gobject1 (011-1) to 011-1ubuntu1
libevdocument1 (2.28.0-0ubuntu4) to 2.28.0-0ubuntu5
libevview1 (2.28.0-0ubuntu4) to 2.28.0-0ubuntu5
libgudev-1.0-0 (1:147~-5) to 1:147~-6
libpolkit-agent-1-0 (0.94-1) to 0.94-1ubuntu1
libpolkit-backend-1-0 (0.94-1) to 0.94-1ubuntu1
libpolkit-gobject-1-0 (0.94-1) to 0.94-1ubuntu1
libudev0 (147~-5) to 147~-6
nvidia-173-modaliases (173.14.20-0ubuntu2) to 173.14.20-0ubuntu3
nvidi...

[bwallum (rbw2)]

This bug appears to set off a Pheonix bios protection function on a i386 platform.

[bwallum (rbw2)]

Bug still here with completely new install using AMD64 daily dated 12th October and updated from main.

[ubox (gwydionwaters)]

i am on kernel 2.6.31-14 and it has just started for me, non-ecc ram. i had no problems in either 2.6.31-11 or 2.6.31-13

[ubox (gwydionwaters)]

i just got it again, just sitting around playing with my desktop. actually all i did was minimize kopete

[ubox (gwydionwaters)]

i am also using the nvidia 185 driver, if that matters

[Michael Martin-Smucker (mmartinsmucker)]

I just got this when I updated to 2.6.31-14. As with ubox, this hadn't been happening for me with previous versions of the kernel. I'm on amd64 with ati graphics. Also, I haven't actually seen any misbehavior; Apport just wants to report an error whenever I start up.

[Neil Wilson (neil-aldur)]

Not sure why apport is starting to pick this up as a 'serious error' all of a sudden. I've had this 'error' in the dmesg since I first installed karmic. It never causes a problem on my system, because its just a warning. In my case the error is that ECC memory is disabled in the BIOS. Which is hardly surprising since the laptop doesn't have ECC memory installed.

Perhaps the driver needs to alter its warning messages so that it is less alarming.

[M Henri Day (mhenriday)]

Agree with Neil Wilson's post above - is it really necessary for a warning of this type to be posted to users whose BIOS doesn't support EEC ? I am certainly willing to be corrected here, but from what I understand the problem - if, indeed, it can be considered such - is hardly so grave as to merit a comment regarding the possibility of one's system becoming unstable....

Henri

[BruceW (bmw-greencampaigns)]

All was fine until the update to:
Linux desktop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux

Then Klapooee!!! First plasma-desktop crashed several times, then the kernel crashes now with the ECC error. Using non-ecc RAM and have it disabled on my ASUS mb.

Please fix.

[sampattuzzi (sam-pattuzzi)]

I can confirm what BruceW is saying. Everything was fine until 2.6.31-14 update. Now the kernel is giving errors about non-ecc memory everytime I log in.

[Shaved Wookie (shavedwookie)]

Mine gave it once, but it hasn't given it again since...

[vaughn (vaughngrisham)]

@ Shaved Wookie,

Have you rebooted? Mine throws the error multiple times after log in. After I have cleared the errors I do not experience any instability however.

[BruceW (bmw-greencampaigns)]

I shut down plasmoids that were connecting with Google and one giving
weather and it all stopped. Sometimes depending on the updates, certain
plasmoids crash due with python errors. The next following update usually
corrects that problem. Most of the time, I just suppose in the beta state
that updates are pushed out quickly maybe too soon but then when finding
those errors are patched immediately and then pushed out again the following
day.

Bruce

On Sun, Oct 18, 2009 at 11:30 AM, vaughn <email address hidden> wrote:

> @ Shaved Wookie,
>
> Have you rebooted? Mine throws the error multiple times after log in.
> After I have cleared the errors I do not experience any instability
> however.
>
> --
> 6.073813] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS.
> Module will NOT be loaded.
> https://bugs.launchpad.net/bugs/422536
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--

Pablo Picasso<http://www.brainyquote.com/quotes/authors/p/pablo_picasso.html>
- "Computers are useless. They can only give you answers."

[Shaved Wookie (shavedwookie)]

@vaughn - Yes, I've rebooted a bunch of times. Why?

[vaughn (vaughngrisham)]

Thanks SW. Just curious. I couldn't replicate your solution and wondered whether your problem returned or not after reboot.

I'm not using any plasmoids but I am using checkgmail and avant window navigator. I tried rebooting without those things launching on startup et voila, no kernel error.

[Ramana (ramana-b-v)]

I think it stopped coming with 2.6.31-14 at least on start up. Fingers crossed.
I still get crashes mostly in firefox complaining about npviewer though
Ramana

[Shaved Wookie (shavedwookie)]

Augh. It came back. But it seems to only do it very rarely - like once every few days or so. Then again, I use almost no plasmoids.

[vaughn (vaughngrisham)]

Yeah, it's back for me as well.

[b01 (shabazzk)]

This is NOT a bug to me, just a REALLY BAD way to indicate that ECC has NOT been enabled in the BIOS. I can't be sure if this happened before or after I did a BIOS update on 10/18/2009. I know for sure there is a setting to enable ECC in my BIOS. I didn't think my memory supported it and was afraid it might decrease performance or make my system unstable without memory supporting it. But I will enable it. But I believe the memory controller on the AMD Athlon 64 X2s is built in, maybe that is why the option is there for me.

Maybe some may want to try a BIOS update if your brave, to see if you get the option to set ECC, as I'm thinking the setting is referring to enable ECC built in with the CPU.

[Leandro (leandromartinez98)]

I have just enabled ECC in the BIOS and I get the crash anyway. So, it is indeed a bug, unless
I started to have bios bug as well two days ago...

[speleovar (speleovar)]

after upgrading this evening still the same bug. And since sometimes npviewer and then nautilus crashed too

[sam (sdoyle-2)]

Just encountered same

[wraithmonk (geoffitton-deactivatedaccount)]

Encountering the same bug.
AMD 64 x2 cpu, 2GB non-ECC RAM, KDE 4.3.2 desktop.
BIOS: Phoenix Technologies, LTD - Release Date: 03/06/2008
Mainboard: MICRO-STAR INTERNATIONAL CO., LTD - Product Name: MS-7253

I was also getting a +------ PCI-Express Device Error ------+ in dmesg, but added the parameter "pci=nommconf" to the kernel boot string, which fixed it.

[Vaughn Tolle (avtolle)]

Having removed the nvidia 185 driver,I'm not getting any further messages
about the bug. I, too, have had npiviewer crash as well, but not nautilus
(yet).

On Tue, Oct 20, 2009 at 4:34 AM, wraithmonk <email address hidden>wrote:

> Encountering the same bug.
> AMD 64 x2 cpu, 2GB non-ECC RAM, KDE 4.3.2 desktop.
> BIOS: Phoenix Technologies, LTD - Release Date: 03/06/2008
> Mainboard: MICRO-STAR INTERNATIONAL CO., LTD - Product Name: MS-7253
>
> I was also getting a +------ PCI-Express Device Error ------+ in dmesg,
> but added the parameter "pci=nommconf" to the kernel boot string, which
> fixed it.
>
> --
> 6.073813] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS.
> Module will NOT be loaded.
> https://bugs.launchpad.net/bugs/422536
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[Dodiak (dodo-sk)]

In my case the crash appear when I try to install ATI fglrx driver. With normal xorg driver it's running fine ...

[ursaminor (ursa-juvenis)]

Ubuntu 9.10 Beta Reboot failure. Screenshot of shutdown freeze attached. Apport submitted.

[Otus (jan-varho)]

I don't think it has anything to do with nvidia drivers. I have a Radeon 4850 and no proprietary drivers installed and have been seeing this message once in a while since the latest kernel update. However, there has been no apparent freezing or anything - just the message.

[b01 (shabazzk)]

I agree with Otus, I am positive this error is caused by exactly what is says in the error report:

     EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.

I only saw it appear once, unfortunately it does make some systems unstable.

After a BIOS update, I checked the BIOS and now there is a whole page of settings, as where before I was only able to enable/disable ECC in the BIOS.

Currently I have ECC set to Good in the BIOS. I have a BIOSTAR TA790GX XE version 5.x mobo, an AMD64 X2 5000+, and GSkill 1066 DDR2 memory.

[wayne pronge (waynepronge)]

Error Message back with kernel 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux

[aarond80 (stefan1-98)]

What about blacklisting the relevant modules? (edac_core, amd64_edac, amd64_edac_mod) After I blacklisted them I stopped getting this error. I intend to keep them blacklisted at least until the next kernel update.

[Harry (harry33)]

Bug still here, I wonder is it going to be looked at during the Karmic development life cycle.
Funny that if I untick the Update-Notifier in the Startup Applications, I do not get the visual kernel crash report, but the I can found the kernel crash log in the /var/crash directory.

[Shaved Wookie (shavedwookie)]

For me this has gone from rock solid stable a couple of weeks ago, to the very occasional error message a few days ago, to a nearly unusable system with no sound, random processes crashing and more. It always starts with the ECC error message though. From the number of dupes this is a very common bug, and if my experience turns out to be average, it may get worse over time.

[Prosthetic Head (propanone)]

Given the effects and the number of people effected I'd suggest that this is very urgent to fix.

[Georg (georg-lippold)]

Booted with amd64_edac.ecc_enable_override=1 with kernel 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 but the error still shows. Despite the annoying bug reports on every login, the system seems to be stable, there are no other application crashes or kernel oops.

[Urmo Kõiv (urmok6iv)]

I just started getting these error messages. Now I've already had it 3 times during 2 hours. And what I was doing? - Just browsing the web... Weird stuff.

[vaughn (vaughngrisham)]

The problem seems to now be affecting stability as I've started experiencing freezes as the message has proliferated (while it was just on boot, now the message keeps popping up ad nauseum).

I agree with Prosthetic Head (why does that previous fragment sound like a spam message?). This should be ranked higher than medium importance. If this were happening with the Windows 7 release, it'd be front page news, and we'd all be pointing and and saying why people should switch to Ubuntu. Fortunately, this is still in beta, so hopefully the developers will get their teeth into this soon.

[rfurgy (rfurgy)]

Hi everyone, I don't get any pop up error messages, but I do see the entry also listed in my logs. Some of you may want to check your chipset or northbridge settings in the BIOS. My ECC settings were hidden inside those areas.

I turned my ECC on (my BIOS also has multiple settings) and rebooted with each setting and still have the messages in my logs.

I have had other apps crash on me in Karmic but don't know if they are related to this. My system is mostly stable so it's hard to say if any instability is coming from it of the fact that I'm running Karmic before RC1.

I do see a problem with this though. Memory can become very unstable when overclocked or even if you have a wrong setting which can definitely cause crashes, and sometimes a system to not even boot. Also if you have ever built some computers, you may know how picky some computers can be about it's memory (example, a stick of memory might work fine in one motherboard and cause the next one to freeze on boot).

So as far as those that don't have ECC in the BIOS or don't turn it on, there shouldn't be any errors concerning this (But it seems there are). Then for those who do have it and have it turned on, there also shouldn't be this error because the ECC is enabled.

Hope there's a fix coming soon.

[Paul Cook (narkosen)]

Problem still continues with current kernel 2.6.31.14-generic x86_64.
Adding boot parameter ecc_enable_override makes no difference.
However it does not occur on booting with 2.6.31.12-generic.

Please can we get this fixed soon, it is getting tiresome.
Thanks in anticipation :-)

[gerstrong (gerstrong)]

Also here.

I have two PC with AMD 64 Processor and they both show this error, but nothing bad happens.

[Urmo Kõiv (urmok6iv)]

Same with rt-kernel.
Karmic Release Candidate

[ralph (rmcknight)]

I also have this issue. Grrrrr. And i dont have ECC memory nore any bios settings to change.

[malcolm (bmcandlish-googlemail)]

Me too! AMD 64 and running happily, no application crashes and yet a
crash notice appears on screen.

Quite weird.
Brian.

On 23/10/2009, ralph <email address hidden> wrote:
> I also have this issue. Grrrrr. And i dont have ECC memory nore any
> bios settings to change.
>
> --
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> https://bugs.launchpad.net/bugs/422536
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> ?
>
> ProblemType: KernelOops
> Annotation: Your system might become unstable now and might need to be
> restarted.
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: yoman82 3464 F.... pulseaudio
> /dev/snd/pcmC0D0p: yoman82 3464 F...m pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'SB'/'HDA ATI SB at 0xf9ff0000 irq 16'
> Mixer name : 'Realtek ALC888'
> Components : 'HDA:10ec0888,18491e01,00100001'
> Controls : 37
> Simple ctrls : 21
> Date: Tue Sep 1 07:48:00 2009
> DistroRelease: Ubuntu 9.10
> Failure: oops
> HibernationDevice: RESUME=UUID=69c64130-cc6f-4a5b-952b-3ba4c893ba48
> MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
> NonfreeKernelModules: nvidia
> Package: linux-image-2.6.31-8-generic 2.6.31-8.28
> PccardctlIdent:
>
> PccardctlStatus:
>
> ProcCmdLine: root=UUID=19f3bdd6-1b33-48e0-8081-d00e178d9f7d ro splash
> vga=792
> ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
> RelatedPackageVersions:
> linux-backports-modules-2.6.31-8-generic N/A
> linux-firmware 1.16
> RfKill:
> 0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> SourcePackage: linux
> Tags: kernel-oops
> Title: 6.073813] EDAC amd64: WARNING: ECC is NOT currently enabled by
> the BIOS. Module will NOT be loaded.
> Uname: Linux 2.6.31-8-generic x86_64
> WifiSyslog:
>
> WpaSupplicantLog:
>
> dmi.bios.date: 04/24/2009
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: P1.00
> dmi.board.name: M3A780GXH/128M
> dmi.board.vendor: ASRock
> dmi.chassis.asset.tag: To Be Filled By O.E.M.
> dmi.chassis.type: 3
> dmi.chassis.vendor: To Be Filled By O.E.M.
> dmi.chassis.version: To Be Filled By O.E.M.
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd04/24/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A780GXH/128M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
> dmi.product.name: To Be Filled By O.E.M.
> dmi.product.version: To Be Filled By O.E.M.
> dmi.sys.vendor: To Be Filled By O.E.M.
>

[Sam_ (and-sam)]

Follow up: Since 2009-10-16 #38 no Apport notifying (bootup every day). Now today two Apport reports right after boot, one followed right after the other one and directed twice to this page #422536. I rebooted and received again two Apport reports (same content).

[Sam_ (and-sam)]

Follow up: Just opened Nautilus via terminal (gksudo nautilus) to remove all those crash files. After doing so Apport reports again, number one was about the topic here, number two about #448183 (private) concerning Nautilus.

[rfurgy (rfurgy)]

I hadn't had any Apport reports detected or reported about this but I did find the error in my logs. Today though I happened to get a report after starting Update-Manager.

[Jauna (lm-pellerin)]

Problème sur le noyau !

[fenian (kingsofoblivion)]

Also have this error with 2 AMD 64 systems

[Mike Matis (mmatis)]

same problem here, and prior to it happening, my system slows to a crawl. After I repoot apport shows up with this error

[Kamil Wilczek (kamil-van-wilczek)]

Hi, I checked my RAM module, and it is not ECC type (motherboard support ECC modules); I also did not found any ECC memory option in BIOS (Award F3 version for Gigabyte MA770T-UD3P);
My processor is AMD Athlon II x2 245;
RAM module is Hynix 2GB 1066Mhz HMT125U6AFP8C-G7 PC-8500F;

I also noticed, that dmidecode and similiar tools can not determine exactly what this module is, some fields are empty; I installed XP and only GIGABYTE motherboard tuning and info program (EasyTune 6) provided all info (I closed RAM in radiator and I can not see labels without dissasembling ;-) )

I had also messages about system instability etc.

O, and I used Beta live CD, then daily build (22 oct) with the same result;
Previously I tried Debian Squeeze and had no problems, clean logs with 2.6.30.8 included;

[DarkMerc (jeffm)]

My system doesn't have any speed problems when the error occurs. I have an AMD Athlon X2 5200+ on a Gigabyte GA-M55SLI-S4 (rev. 2.0) motherboard with SLIed 7900GS cards running and no ECCed RAM (667MHZ Ram). I just upgraded from 9.04 with no errors on that. I'm running the 185 nvidia proprietary drivers. It keeps telling me repeatedly also. Hope you guys can fix this in 5 days LoL.

[DarkMerc (jeffm)]

O BTW I'm running the 64 bit version of ubuntu is everyone else here too?

[bwallum (rbw2)]

Still with me 10.04 GMT Sat 24th October. I minute or so into OS load and up pops crash icon in top panel. Seems to have no effect but looks bad.

[Peter Fellin (peterfellin)]

This error has this time coincided with having changed a setting in nvidia-settings with the result that Ubuntu is now workable together with NVIDIA FOR THE FIRST TIME.

I will restart now and see if the system retains my change - something it has refused to do before.
Shall return with a report if things have - hopefully - been fixed this way.

Am using the 64 bit Gnome version and an AMD dual core with NViDIA Gforce 6150 inbuilt on the motherboard.

[b01 (shabazzk)]

I am researching some facts on why so many people are getting this error and have NON-ECC RAM, turns out ECC mode works with NON-ECC RAM (aka Parity RAM).

Here's an excerpt from the article:

     There are special ECC memory modules designed specifically for use in ECC mode, but most modern motherboards that support ECC will in fact work in that mode using standard parity memory modules as well. Since parity memory includes one extra bit for every eight bits of data, this means 64 bits worth of parity memory is 72 bits wide, which means there is enough to do ECC...

Here's a link to where I got my info: http://www.pcguide.com/ref/ram/errECC-c.html

My guess is that Ubuntu is detecting this option is available, but it is NOT turned on in the BIOS. It could be the AMD Athlon 64bit X2, or what ever DRAM modules you have installed causing this option to be available. I know that the AMD datasheet for 64bit X2s state that they have ECC mode. So maybe the CPU is the trigger.

[b01 (shabazzk)]

I notice recent BIOS updates available for the following ppl:

Person BIOS Release date Version
------------------------------------------------------------
DarkMerc 2008/10/22 F11J
Kamil Wilczek 2009/09/21 F4

I'm NOT suggesting you guys update, but updating my give you the option in the BIOS.

[BruceW (bmw-greencampaigns)]

Okay, folks, so I just kept updating and updating and it finally worked
itself out. Be sure to remove all plasmoids from the desktop. On another
machine I updated that was causing the problems. I figured it out as it kept
crashing as soon as that plasmoid tried to install. Make sure you are
getting the kernel updates. Also, KPackageKit Will hold back certain
updates for some reason. I am not sure why or the logic behind it and could
never find a reason but if you use CLI apt-get or Synaptic GUI instead, you
will have all the updates installed. Frequently do CLI "apt-get
autoremove", "apt-get autoclean" and "apt-get clean" so that you will get
fresh update files. Sometimes I find that if a file exists in the apt cache
it will get skipped when updating.

Also, be sure to have the latest video driver. If you are using nVidia, be
sure to do your research on updating. DO NOT CHOOSE THE FIRST ONE YOU FIND.
Read through several solutions first. I tend to get a little antsy and
think if the first one I see sounds good I'll try that. Just keep reading
down the search engine page. It will become blatantly clear which one to
choose by the time you get to the bottom.

Best,
Bruce

On Sat, Oct 24, 2009 at 6:20 AM, b01 <email address hidden> wrote:

> I notice recent BIOS updates available for the following ppl:
>
> Person BIOS Release date Version
> ------------------------------------------------------------
> DarkMerc 2008/10/22 F11J
> Kamil Wilczek 2009/09/21 F4
>
> I'm NOT suggesting you guys update, but updating my give you the option
> in the BIOS.
>
> --
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> https://bugs.launchpad.net/bugs/422536
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--

Ted Turner <http://www.brainyquote.com/quotes/authors/t/ted_turner.html> -
"Sports is like a war without the killing."

[Andy Whitcroft (apw)]

k. First thing to notice is that this is not an oops at all. If we
look at the oops text as detected by apport and reported to launchpad,
its not actaully a kernel oops; it is simply a WARNING: which has been
reported in the dmesg:

    6.073813] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
    Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
    Might be a BIOS bug, if BIOS says ECC is enabled
    Use of the override can cause unknown side effects.
    amd64_edac: probe of 0000:00:18.2 failed with error -22

So actually the primafacie issue here is that apport has miss categorised
this message segment as a kernel oops/warn_on when it is not.

As for the message itself it was added in the commit below which appears
first in 2.6.31-rc1, and is from a bug fix to ensure we only enable ECC
when it is enabled in the BIOS:

  commit f9431992b6227069bc54800d55531c6f78d276a7
  Author: Doug Thompson <email address hidden>
  Date: Mon Apr 27 19:46:08 2009 +0200

    amd64_edac: add ECC reporting initializers

It does appear that this message is reporting something resonable, likely
only fixable only by changing a BIOS setting. The functionality does
not appear to be changed, only that you are now warned of the previous
behaviour being non-optimal. The key issue is that apport is reporting
this as a kernel OOPS when it was actually a minor warning.

We appear to have two options:

1) fix apport to more accuratly detect oops strings and thus prevent it
   detecting this non-oops and incorrectly reporting it, or
2) modify this message to have a different form to prevent this matching
   from occuring.

Adding a task on apport to see if this is easy to fix there.

[Andy Whitcroft (apw)]

Apport appears to incorrectly reporting a minor warning as a kernel OOPS. it appears the OOPS matching is too lax in this case. We would like to know if apport could be fixed here rather than spinning the kernel.

[Sam_ (and-sam)]

Follow up: reproducable tested in the last hour
a) only happens after reboot (always two apport reports about the same issue)
b) it does not occur after shutdown and boot, it does not occur after hibernate.
c) occurs when running 'gksudo nautilus' in gnome-terminal (one apport report)

[Mike Matis (mmatis)]

Looks like I actually have 2 problems. I do have the ECC oops error, but my sluggishness is actually a separate issue which is being caused by the fact I have SLI turned on in the Nvidia binary driver. When SLI is off, there's no sluggishness, though I still get the crash reports.

[Kamil Wilczek (kamil-van-wilczek)]

I updated BIOS to F4 version, messages the same; I attached this time logs from Beta LiveCD; this time stable without messages from system about errors and possible unstability; I saw additional lines about Error Correction and Detection Code before known messages, and please see those logs, anyone see something else ;-)

                                                                         EDAC MC: Ver: 2.1.0 Sep 25 2009
Oct 25 02:16:08 ubuntu kernel: [ 71.567175] ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SOR1 [0xb00-0xb0f]
Oct 25 02:16:08 ubuntu kernel: [ 71.567179] ACPI: Device needs an ACPI driver
Oct 25 02:16:08 ubuntu kernel: [ 71.567195] piix4_smbus: probe of 0000:00:14.0 failed with error -16
Oct 25 02:16:08 ubuntu kernel: [ 71.838504] EDAC amd64_edac: Ver: 3.2.0 Sep 25 2009
Oct 25 02:16:08 ubuntu kernel: [ 71.841047] parport_pc 00:09: reported by Plug and Play ACPI
Oct 25 02:16:08 ubuntu kernel: [ 71.841099] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
Oct 25 02:16:08 ubuntu kernel: [ 71.845792] EDAC amd64: This node reports that Memory ECC is currently disabled.
Oct 25 02:16:08 ubuntu kernel: [ 71.845797] EDAC amd64: bit 0x400000 in register F3x44 of the MISC_CONTROL device (0000:00:18.3) should be enabled
Oct 25 02:16:10 ubuntu kernel: [ 71.845799] EDAC amd64: bit 0x0000000000000010 in MSR 0x0000017b of node 0 should be enabled
Oct 25 02:16:10 ubuntu kernel: [ 71.845801] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
Oct 25 02:16:10 ubuntu kernel: [ 71.845802] Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
Oct 25 02:16:10 ubuntu kernel: [ 71.845803] Might be a BIOS bug, if BIOS says ECC is enabled
Oct 25 02:16:10 ubuntu kernel: [ 71.845803] Use of the override can cause unknown side effects.
Oct 25 02:16:10 ubuntu kernel: [ 71.845824] amd64_edac: probe of 0000:00:18.2 failed with error -22

[Kamil Wilczek (kamil-van-wilczek)]

And dmidecode fragment:

Memory Controller Information
 Error Detecting Method: 64-bit ECC
 Error Correcting Capabilities:
  None
 Supported Interleave: One-way Interleave
 Current Interleave: One-way Interleave
 Maximum Memory Module Size: 1024 MB
 Maximum Total Memory Size: 4096 MB
 Supported Speeds:
  70 ns
  60 ns
 Supported Memory Types:
  Standard
  EDO
 Memory Module Voltage: 3.3 V
 Associated Memory Slots: 4
  0x0006
  0x0007
  0x0008
  0x0009
 Enabled Error Correcting Capabilities:
  None

All dmidecode attached;

[fancypiper (philsexton)]

My dmesg

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.31-14-generic (buildd@crested) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 (Ubuntu 2.6.31-14.48-generic)
[ 0.000000] Command line: root=UUID=6a15e146-a48d-420f-9b2f-a458086a31b6 ro quiet splash
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009d800 (usable)
[ 0.000000] BIOS-e820: 000000000009d800 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000007fff0000 (usable)
[ 0.000000] BIOS-e820: 000000007fff0000 - 000000007fff3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007fff3000 - 0000000080000000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] DMI 2.2 present.
[ 0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0x7fff0 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-C7FFF write-protect
[ 0.000000] C8000-FFFFF uncachable
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0000000000 mask FF80000000 write-back
[ 0.000000] 1 disabled
[ 0.000000] 2 disabled
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] Scanning 0 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000010000 (reserved)
[ 0.000000] modified: 0000000000010000 - 000000000009d800 (usable)
[ 0.000000] modified: 000000000009d800 - 00000000000a0000 (reserved)
[ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 000000007fff0000 (usable)
[ 0.000000] modified: 000000007fff0000 - 000000007fff3000 (ACPI NVS)
[ 0.000000] modified: 000000007fff3000 - 0000000080000000 (ACPI data)
[ 0.000000] modified: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] modified: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] initial memory mapped : 0 - 20000000
[ 0.000000] init_memory_mapping: 0000000000000000-000000007fff0000
[ 0.000000] Using x86 segment limits to approximate NX protection
[ 0.000000] 0000000000 - 007fe00000 page 2M
[ 0.000000] 007fe00000 - 007fff0000 page 4k
[ 0.000000] kernel direct mapping tables up to 7fff0000 @ 10000-14000
[ 0.000000] RAMDI...

[Daniel06 (dleh)]

Same problem here. Currently I'd like to install Ubuntu Karmic 64-bit RC from a USB Stick - created with ubuntu usb-creator - and I get this error at once after GDM was loaded. This error occurs reproducable at every restart.

Output of uname:
Linux ubuntu 2.6.31-14-generic #48-Ubuntu SMP x86_64

Output of dmesg/kernel.log:
Oct 25 12:11:09 ubuntu kernel: [ 25.144007] EDAC amd64_edac: Ver: 3.2.0 Oct 16 2009
Oct 25 12:11:09 ubuntu kernel: [ 25.144081] EDAC amd64: This node reports that Memory ECC is currently disabled.
Oct 25 12:11:09 ubuntu kernel: [ 25.144084] EDAC amd64: bit 0x400000 in register F3x44 of the MISC_CONTROL device (0000:00:18.3) should be enabled
Oct 25 12:11:09 ubuntu kernel: [ 25.144086] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
Oct 25 12:11:09 ubuntu kernel: [ 25.144087] Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
Oct 25 12:11:09 ubuntu kernel: [ 25.144088] Might be a BIOS bug, if BIOS says ECC is enabled
Oct 25 12:11:09 ubuntu kernel: [ 25.144088] Use of the override can cause unknown side effects.
Oct 25 12:11:09 ubuntu kernel: [ 25.144097] amd64_edac: probe of 0000:00:18.2 failed with error -22

[Alexkeny (alexkeny)]

I have the same problem, ubuntu 9.10 2.6.31-14-generic amd64
Sometimes my system just freeze, and i can't do anything, i just push reset button

EDAC amd64_edac: Ver: 3.2.0 Oct 16 2009
EDAC amd64: This node reports that Memory ECC is currently disabled.
EDAC amd64: bit 0x400000 in register F3x44 of the MISC_CONTROL device (0000:00:18.3) should be enabled
EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
Might be a BIOS bug, if BIOS says ECC is enabled
Use of the override can cause unknown side effects.
amd64_edac: probe of 0000:00:18.2 failed with error -22

[Jeff (jdorenbush)]

I am getting the same bug every time I boot up. It doesn't appear to be affecting the functionality of my system, at least not that I have noticed. All I do is click on the bug report icon in my notification area and then cancel the report and it goes away. Would like to see this resolved so I don't keep seeing the bug report icon though.

Anyone aware of if this is in fact affecting the system or causing problems?

[Cringer (jrlor63)]

Received this tonight. I am booting from a USB drive using ubuntu-9.10-rc-desktop-amd64.iso. The first time I booted with it I received no problem until I tried to install Ubuntu, in which my screen went to an odd pattern and froze.

After that I booted into it again and received it right after booting when trying to install Ubuntu. I then went back into my Ubuntu 9.04 partition, re-did the USB "Live CD" and tried again. This time I tried to install instead of going into the live session instead. The first install screen popped up briefly (choosing a language) and then it blanked out and booted into the live session. Clicking install in there again gave me this error. At the same time I received Bug #441904 and Bug #452208. Also, install never opens for me when clicking it, so unable to install the RC right now.

[Dimitris Athanasopoulos (motzin-deactivatedaccount)]

Ο πίνακας εφαρμογών αντιμετώπισε ένα πρόβλημα κατά τη φόρτωση του "OAFIID:GNOME_FastUserSwitchApplet". Θέλετε να αφαιρέσετε τη μικροεφαρμογή από τη ρύθμιση σας;

[Martin Pitt (pitti)]

Apport itself only looks for /var/crash/vmcore and generates a report for it, so I assume that those are produced by kerneloops?

[Cringer (jrlor63)]

You would know better. I have only been using linux for about five
months or so, still learning a lot. Sorry if reported incorrectly.

Martin Pitt wrote:
> Apport itself only looks for /var/crash/vmcore and generates a report
> for it, so I assume that those are produced by kerneloops?
>
> ** Package changed: apport (Ubuntu) => kerneloops (Ubuntu)
>
>

[speleovar (speleovar)]

I've upgraded an then reboot : still the same bug + vlc crashed

[thecityofgold (simon-haighmail)]

Same as above. I get the crash report on every boot and have had a couple of hard lockups requiring computer reset switch. AMD 64X2 running 64bit Karmic, 2.6.31-14 with nvidia 185.

[holysmokes (bryan2600)]

I can confirm the crash as well. 64 bit with nvidia pci-e. I don't honestly even know what ecc ram is.. I may have it but never heard of it before.. Karmic was great when I first started beta testing it, and now it runs terrible.. I checked my bios and don't find anything that mentioned the acronym ECC or anything like it.. I have been watching this thread grow each day, and we are just a couple of days from roll out of Karmic.. She's was looking really swell, but my users right now don't have any crashes on previous versions of Ubuntu, and they are not going to be too happy when they start having crashes with Karmic (oh boy!).. Should I tell my users not to upgrade (delay and watch until this is fixed) to 9.10 if they are running 64 bit and running nvidia or not? Please advise, because idk what ecc is.. Maybe put a warning on the ubuntu web site, just to let people know to hold and wait for now.. Danke!!

[manzur (sl-solaris)]

Canonical shouldn't release karmic until it is completely good, free of bugs and stable

[Sebastian Bengtsson (5ebastian)]

Confirmed on a new machine with Karmic RC1 live cd. Booted and Apport sent me here.
AMD chipset 785G (Gigabyte MA785GT-UD3H)
Athlon II X2 250
Non-ECC RAM: KVR1333D3N9K2/4G

lspci apparently sees the 785G as an 780G chipset, and SB710 as SB700.

00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge Alternate
00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (int gfx)
00:0a.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 5)
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode]
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3c)
00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Link Control
01:05.0 VGA compatible controller: ATI Technologies Inc Device 9710
01:05.1 Audio device: ATI Technologies Inc Device 970f
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
03:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

[Shaved Wookie (shavedwookie)]

@Manzure - we'd still be waiting for Warty Warthog and DOS 1.0 if that were the case...

[manzur (sl-solaris)]

I know it Mr. Shaved Wookie but it is pointless to release a buggy version, I do not see the need to have a final release, if it is as buggy as its beta or release candidate.. got me? with final releases people put their trust in the product and now more than ever that we are in some Dell PCs by default

[Shaved Wookie (shavedwookie)]

Sure. I can understand that. Just realise that "buggy" is a relative term and that there are always acceptable and unacceptable levels of bugs that differ between release types types (eg alpha vs beta vs RC vs standard release vs LTS). Every user believes their bug is *the* most important and *the One* that makes all the difference. Software though is always advanced by a balance between getting it out in real world testing with the newer code vs finding the bugs in the current code. Just look at Vista! ;)

No software ships with 0 bugs.

You just do the best you can to get the most important ones fixed as soon as possible. In this light, I'm sure that many bugs will be found and quickly patched as a result of the initial release and updates. Being fixed before release would be nice. Having the most important bugs patched as quickly as possible (including this one or not) is more important.

Anyway, if you'd like to continue this discussion on the forums or privately, that's fine, but I'd suggest we both leave this bug report clear for what we both want: getting a solution found and implemented for this.

Cheers!

[speleovar (speleovar)]

i've flashed the bios , (i had no time to do it before) : since 2 days no crash and no report for bug #422536

[b01 (shabazzk)]

@speleovar

Well, that makes 2 of us that have solved this issue with a BIOS update. Now if just a few more ppl would update to their latest BIOS to see if it solves it for them.

If everyone could help find a solution instead of guessing that it's their video drivers, this probably could have been solved by now. Not to mention that only 117 out who knows how many Ubuntu users don't have this problem.

[Till Hartmann (tillux)]

Funnily enough I got this error message only *once*, and after an upgrade (I think it was still during beta-time) and a reboot it did not appear again. (When the message first occurred it did not do any harm, btw)

Board: ASUS A8N5X (BIOS revision 1003 beta, there isn't anything newer than that)
CPU: AMD Athlon64 3500+
GPU: NVidia Geforce 7800GT
1,5GB DDR1 RAM

What somehow irritates me is the fact that this error occurred when my BIOS/Board-Battery went empty (so there was a BIOS reset to defaults before that). There isn't any option regarding ECC, though, and I'm not even sure if I have got ECC Ram.

[nolo (carl-anderson)]

Well, let me just preface this by saying that I'm a computer user with
decades of experience and have updated my BIOS dozens of times before.
 However, when I recently tried to resolve this issue by updating my BIOS I
mis-typed the downloaded filename while using the AWDFLASH utility.
 AWDFLASH hosed my BIOS and the board won't post. I had to order a new
motherboard after trying to clear the CMOS for well over an hour with no
luck. I think it would be a mistake to officially recommend a BIOS update
to even the experienced user due to the severity of screwing up. I'm still
waiting for my replacement mobo to arrive.

On Wed, Oct 28, 2009 at 7:50 AM, b01 <email address hidden> wrote:

> @speleovar
>
> Well, that makes 2 of us that have solved this issue with a BIOS update.
> Now if just a few more ppl would update to their latest BIOS to see if
> it solves it for them.
>
> If everyone could help find a solution instead of guessing that it's
> their video drivers, this probably could have been solved by now. Not to
> mention that only 117 out who knows how many Ubuntu users don't have
> this problem.
>
> --
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> https://bugs.launchpad.net/bugs/422536
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “kerneloops” package in Ubuntu: Confirmed
> Status in “linux” package in Ubuntu: Confirmed
>
> Bug description:
> ?
>
> ProblemType: KernelOops
> Annotation: Your system might become unstable now and might need to be
> restarted.
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: yoman82 3464 F.... pulseaudio
> /dev/snd/pcmC0D0p: yoman82 3464 F...m pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'SB'/'HDA ATI SB at 0xf9ff0000 irq 16'
> Mixer name : 'Realtek ALC888'
> Components : 'HDA:10ec0888,18491e01,00100001'
> Controls : 37
> Simple ctrls : 21
> Date: Tue Sep 1 07:48:00 2009
> DistroRelease: Ubuntu 9.10
> Failure: oops
> HibernationDevice: RESUME=UUID=69c64130-cc6f-4a5b-952b-3ba4c893ba48
> MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
> NonfreeKernelModules: nvidia
> Package: linux-image-2.6.31-8-generic 2.6.31-8.28
> PccardctlIdent:
>
> PccardctlStatus:
>
> ProcCmdLine: root=UUID=19f3bdd6-1b33-48e0-8081-d00e178d9f7d ro splash
> vga=792
> ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
> RelatedPackageVersions:
> linux-backports-modules-2.6.31-8-generic N/A
> linux-firmware 1.16
> RfKill:
> 0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> SourcePackage: linux
> Tags: kernel-oops
> Title: 6.073813] EDAC amd64: WARNING: ECC is NOT currently enabled by
> the BIOS. Module will NOT be loaded.
> Uname: Linux 2.6.31-8-generic x86_64
> WifiSyslog:
>
> WpaSupplicantLog:
>
> dmi.bios.date: 04/24/2009
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: P1.00
> dmi.board.name: M3A780GXH/128M
> dmi.board.vendor: ASRock
> dmi.chassis.asset.tag: To Be Filled By O.E.M.
> dmi.chassis.type: 3
> dmi.chassis.vendor: To Be Filled By O.E.M.
> dmi...

[eXlin (hirvonen-henri)]

@nolo
Yes i agree. I am professional programmer and i have updated my bios only once in lifetime.
I could think updating bios, but we should find out is mistake originally made by bios writer or
by kernel team.
  If mistake isn't made when writing bios then we shouldnt promote to update bios.
Beside this bug seems to affect so wide selection of motherboard manufacturers that it makes it hard to believe its their mistake.
Beside it would be way too risky operation to do for users without good experience from computers.

And anyway if this is fixable by us we should create a fix for this anyway.

[b01 (shabazzk)]

@nolo

Sorry to hear about your experience, I had the luxury of having a dual boot system, so all I had to do is download the utility from the mobo web site a flash from windows OS. Updating a BIOS should not be an uncommon thing these days, I did it for my XBOX, several Mobos in the last month, and also my cell phone, which I flash about every month now. But that's just me.

I do BIOS updates on a common occurrence, so I apologize if I caused anyone to have to suffer by recommending a BIOS update.

One thing I do want to make clear is that if you read up on ECC, you will know that you do NOT have to have ECC RAM in order to be able to set it in the BIOS. ECC is just a software algorithm for detecting errors in your RAM, which is possible for most all RAM today, not just ECC RAM. I think there is even ECC RAM which doesn't support ECC Mode, which again is just a way to report errors to your OS that there are problems occurring with your RAM. Linux, as well as Windows support ECC reporting to alert the user when errors in their RAM occur.

My thing is that everyone should do a little solid investigating before jumping to conclusions that drivers are at fault, as you will only waste your time and possibly a developers by steering ppl in the wrong direction. The Ubuntu team will fix this if it is on their end. Ubuntu is a community tool, so those of us having the problem should do our part to help the developers fix, as they probably have more pressing bugs to fix. It is possible to be a hardware issue, there are only 100 or so reports of this bug, which is NOT a lot, compared to all the possible hardware combos out there.

[Ben Sandee (tbsandee)]

The latest kernel updates (or some related update) resolved the problem for me. I did no BIOS updates or any such thing. I haven't seen a crash in 2-3 days. For me, this problem is resolved.

[James Westby (james-w)]

kerneloops looks for

  if (strstr(c, "WARNING:")

so it matches that message even though it isn't a WARN().

The match could probably be improved to only match what is
being produced by WARN(), but the module could also change
to be less SHOUTY about this issue.

Thanks,

James

[David Brewer (david-brewer)]

Tried updating my bios this morning in response to some earlier comments on this issue. I have an ASUS M2NPV-VM motherboard; upgraded from bios version 0705 to version 1401. This didn't seem to make any difference; I still get the error messages shortly after boot.

[Hendrik van den Boogaard (chasake)]

I get this error when I boot my Ubuntu partition in VirtualBox, so no real ECC problem there...

[Terry (terry-kryogenic)]

Seems to me this is not a crash as James Westby has found. I certainly wouldn't suggest upgrading the BIOS to anyone. Surprised this hasn't been fixed already :P

[Evertjan Garretsen (egarretsen)]

I'm experiencing this error too, starting this morning. Processor AMD Turion X2 64 BIT.

[exzemat (exzemat)]

I have this problem too.
motherboard : Gigabyte ga-m68sm-s2l (no option ECC in BIOS award)
amd 64
nvidia Gforce 8400 GS (driver 185)

Karmic 64 bit

the problem appear sometimes, not always.

[Piotr Smolarz (smopi)]

The same problem.

motherboard: GA-M68SM-S2 (GeForce 7025 / nForce 630a / Socket AM2)
CPU: AMD Athlon 64 X2 4000+

Graphics card: Asus GeForce 9600GSO 384MB DDR3 192bit PCI-E (185 driver)

Ubuntu 9.10 64bit

uname -a
Linux smopi 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux

[Jeruvy (jeruvy)]

I have the very same scenario as #22 noted above, maybe others but I gave up after about 60 comments, sorry.

I cannot change the ECC settings via bios due to overclocking, and it does appear that the error is trivial since it doesn't affect any operations. I do have other crashes occurring but I'm not convinced they are related.

[Garyu (launchpad-dan-erik)]

I got this bug when booting from the CD. Hoping installation will go fine.

It appeared after a popup about nVidia proprietary drivers being available. Here is a snippet of my kern.log:

Oct 29 23:19:45 ubuntu kernel: [ 85.798072] ACPI: I/O resource nForce2_smbus [0x600-0x63f] conflicts with ACPI region SMRG [0x600-0x6ff]
Oct 29 23:19:45 ubuntu kernel: [ 85.798076] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 29 23:19:45 ubuntu kernel: [ 85.798078] nForce2_smbus 0000:00:01.1: Error probing SMB1.
Oct 29 23:19:45 ubuntu kernel: [ 85.798081] ACPI: I/O resource nForce2_smbus [0x700-0x73f] conflicts with ACPI region SM00 [0x700-0x73f]
Oct 29 23:19:45 ubuntu kernel: [ 85.798082] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 29 23:19:45 ubuntu kernel: [ 85.798084] nForce2_smbus 0000:00:01.1: Error probing SMB2.
Oct 29 23:19:45 ubuntu kernel: [ 86.047039] EDAC MC: Ver: 2.1.0 Oct 16 2009
Oct 29 23:19:45 ubuntu kernel: [ 86.110410] Bluetooth: Generic Bluetooth USB driver ver 0.5
Oct 29 23:19:45 ubuntu kernel: [ 86.110480] usbcore: registered new interface driver btusb
Oct 29 23:19:46 ubuntu kernel: [ 87.252279] EDAC amd64_edac: Ver: 3.2.0 Oct 16 2009
Oct 29 23:19:46 ubuntu kernel: [ 87.252360] EDAC amd64: This node reports that Memory ECC is currently disabled.
Oct 29 23:19:46 ubuntu kernel: [ 87.252363] EDAC amd64: bit 0x400000 in register F3x44 of the MISC_CONTROL device (0000:00:18.3) should be enabled
Oct 29 23:19:46 ubuntu kernel: [ 87.252365] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
Oct 29 23:19:46 ubuntu kernel: [ 87.252366] Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
Oct 29 23:19:46 ubuntu kernel: [ 87.252367] Might be a BIOS bug, if BIOS says ECC is enabled
Oct 29 23:19:46 ubuntu kernel: [ 87.252368] Use of the override can cause unknown side effects.
Oct 29 23:19:46 ubuntu kernel: [ 87.252432] amd64_edac: probe of 0000:00:18.2 failed with error -22

[Mr. Aljoriz Dublin (aljoriz)]

it certain is a bios bug. Not that it hinders with desktop performance.. its just plain ANNOYING to have a pop up that says there is a crash.

[GroovyMotion (flywaver)]

Same bug here with the Final Release Karmic ISO...I am writing this from the LiveCD...I don't think I will update my 9.04 yet! ;)

[Dexhu (dx4linux33)]

I Upgraded to 9.10!
Not sure if this corrects the ERROR?

[Dario Panico (dariopnc-)]

seeing that this bug has been set to private TWO times, tell us a valid reason for that...

[Jeff (jeffrey-frasch-gmail)]

What I find incomprehensible in this «kernel oops» is the fact that it revolves around ECC RAM. Why would the OS be looking to load the kernel module for ECC RAM? My Bios does not contain any visible assignment for ECC RAM, though I believe that the Phenom II memory controller has the capacity to operate ECC RAM if this type of memory is installed. The only setting I find in the bios which might affect the operation of ECC RAM is this «ganged» and «unganged» setting under DRAM Configuration, where as far as I know «ganged» offers ECC RAM better functionality but this is not the same thing as ECC RAM enabled (for this there is no setting and I have the latest Bios for the 790FXT motherboard from Gigabyte.

Still the question remains, why does the os check the bios to see if ECC RAM is enabled? This strikes me as wrong, unless of course the RAM were actually ECC. I know that I am using non-ECC RAM so even if my bios had a setting for ECC RAM this setting would not be enabled and of course this would mean that the module should not be loaded—but then why does this trigger a kernel alert? It doesn't make any sense unless the Kernel thinks that the RAM is ECC and that therefore the kernel module for ECC RAM should be loaded but can't be loaded because the BIOS setting is not enabled—so where would the information that the RAM is ECC be coming from?

[Terry (terry-kryogenic)]

Surely it's merely telling you that ECC is NOT enabled, what's wrong with that? (Apart from being a little less verbose about it perhaps)

Seems to me it's already been established as not a real crash anyway, no big deal.

[jheaton5 (jheaton5-linuxmail)]

Same bug: Curious thing is that it happens on laptop with AMDTurion64, but not with laptop with Intel core2duo.

[Andre (andre-cadimira)]

Installing ubuntu-restricted-extras unexpectedly solved the issue for me

[Reinaldo Davanzo (davanzo-sapucaia-ms)]

Placa Asus M2N SLI de Luxe.
Processador: AMD Phenom(tm) 9550 Quad-Core Processor.
Memória Ram: 8 Gb (Não ECC).
Placa Vídeo: 2 placas Nvidia Geforce 8600 GT em modo SLI (512 Mb Ram cada).
Disco rígido Sata primário: 1,5 Tb (Windows 7 - RC).
Disco rígido Sata: 250 GB (Ubuntu 9.10).
Sistema Operacional: 64 bits
Monitor: LCD AOC HD (1920x1080)

[RickardJ (rickardj)]

Same problem for me. Clean install 9.10. Booted, enabled nvidia driver, and this bug appears.

[Strepto (victor-rossetti)]

If it were a BIOS bug, then it would have appeared even with earlier kernel versions. This bug appears when you run Karmic from RC on. Even if it seems that is not a bug itself, just an "oververbosing" of the notification system, it's pretty annoying and could prevent the early implementation of Karmic in a lot of systems with amd64 arch and nVidia video cards. I will wait until the next kernel update for installing Karmic on my main desktop.

[reygecko (reygecko)]

Here another user with the same fucking problem. :(

My PC: Gigabyte M52L-S3P, AMD Phenom 4 cores, 8 GB RAM, Nvidia GeForce GTS 250.

Using Ubuntu 9.10 AMD64, final release.

Installing ubuntu-restricted-extras DIDN'T solve the error. I'm afraid I'll continue with 9.04 until the clever boys fix this problem.

[pan323 (pantelis40)]

the problem was fixed for me when i disabled update manager from startup

[Shaved Wookie (shavedwookie)]

A number of people have stated that this is a 64bit Nvidia only problem.

This problem is not Nvidia specific.

My machine is 64 bit with all AMD graphics, and I've been getting this problem too despite being on a vanilla install without having ever installed any of the Nvidia drivers.

[Machiavelli (machiavelli)]

I experience the same problem, running AMD 64, Nvidia.

Other then that the koala looks very good and stable.

[Slogger (slogger)]

I've encountered this bug live booting a 9.10 live usb.
I have nvidia graphics, but they're running on the 'open' driver off the live usb.

I do not have ECC memory, and if my bios allows it to be enabled it's hidden somewhere in the depths of menus I don't understand.

Run an AMD X2 system.

The system seems to remain operational and stable, outside bug popups for this.

[Slogger (slogger)]

(Oh, and I'm on 64 bit.)

[manzur (sl-solaris)]

as I said... canonical shouldn't have release karmic until this and some others critical bugs were fixed... but who cares what I say?

[Søren Nielsen (nebulus)]

I have this bug too.
Running nvidia-185 on 64 bit Ubuntu 9.10

FOund the ECC option in the BIOS and turned it on but the bug still emerges.
Have no idea about what RAM is inside my machine.

[Martin Pitt (pitti)]

manzur [2009-10-31 3:22 -0000]:
> as I said... canonical shouldn't have release karmic until this and some
> others critical bugs were fixed... but who cares what I say?

It's not a critical bug; the ECC warning is not a bug in the first
place. The only bug is that kerneloops remained enabled in the final
release, and that it converts this warning into a problem report.

We'll still deal with disabling kerneloops.

--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

[Jerome R (1dahut)]

Hi !

For me too(as pan323), the problem was fixed when i disabled update manager from startup

command launched from Startup Panel : 'update-notifier --startup-delay=60'

bug appeared after 60s, and just once !

[Dave Efflandt (efflandt)]

I upgraded from 9.04 to 9.10 in place from update manager on AMD Athlon64 3200+ 2000 MHz 1024K cache. Apparently the ECC issue is kernel 2.6.31 specific having to do with "EDAC amd64_edac: Ver: 3.2.0 Oct 16 2009". It does not happen if I boot alternate kernel 2.6.28-16 (ECC not even mentioned in that). Nothing in my BIOS or CMOS settings even mentions ECC.

efflandt@efflandt-desktop:~$ ls -l /var/crash
total 6648
-rw-r--r-- 1 kernoops adm 1566 2009-10-31 01:49 linux-image-2.6.31-14-generic.105530.crash
-rw-r--r-- 1 kernoops adm 1566 2009-10-31 06:47 linux-image-2.6.31-14-generic.105532.crash
-rw------- 1 kernoops adm 519830 2009-10-31 01:01 linux-image-2.6.31-14-generic.46382.crash
-rw-r--r-- 1 kernoops adm 1118 2009-10-30 23:29 linux-image-2.6.31-14-generic.70887.crash
-rw------- 1 kernoops adm 592469 2009-10-31 01:54 linux-image-2.6.31-14-generic.81025.crash
-rw-r--r-- 1 kernoops adm 1258 2009-10-31 06:46 linux-image-2.6.31-14-generic.81027.crash
-rw------- 1 root root 5655892 2009-10-30 22:47 _usr_sbin_synaptic.0.crash
efflandt@efflandt-desktop:~$ uname -a
Linux efflandt-desktop 2.6.28-16-generic #55-Ubuntu SMP Tue Oct 20 19:48:32 UTC 2009 x86_64 GNU/Linux

The alternate kernel 2.6.28-16 seems to work fine, so I will stick with that for now.

[Ramana (ramana-b-v)]

Hi
I don't know if it helps but the bug disappeared after I cleaned up all the old logs in /var/logs. It hasn't surfaced for last three days.
Previously it was coming on every boot.

Ramana

[Nathan Murray (yotux)]

I have this error message up in my taskbar, It doesn't seem to affect the system at all. Once the fix is applied I apply but unless it effects the system or apps I would deal with other issues that are crashing the OS. Running 64bit 9.10. Did not recall seeing the error before I install the 64bit OS.

was tesing threw alpha on i386.

[GroovyMotion (flywaver)]

I installed Karmic and all was fine until I activated the Nvidia 185 drivers and rebooted!
So for me there is a direct connection with that specific driver!
AMD64 with Nvidia on Karmic 64-bit

[SirFrankie (junkert-ferenc)]

Hi, have this error too
I am after an update from clean 9.04. OS is AMD64, graphic card nvidia, HW is ASUS F5N note.
what else could i say?

[SirFrankie (junkert-ferenc)]

yeeeepp, i forgot... every of my windows upper rows (where minimize or close button is on the right side, sorry i forgot his name too) is missed. So i could not moving my working windowses....

[Yucko (ronald-vertommen)]

Well Flywaver, I didn't activate any proprietary drivers for my Nvidia 8600 card as I just got this system up to 9.10 from 9.04 (clean, no upgrade) and still I have the same 'issue' as all the other people here. So in my opinion it's not related.

And as with others, only a notification that there was some kind of crash (saw the word 'kernel' :o) but no impact on system reliability so far.

system is an AMD X2 3200 with NV 8600 card, running the x64 version of Karmic.

[matangdilis (matangdilis)]

Problem also occurs in the following specs:

installation: 9.10 upgrade from 9.04 AMD 64
motherboard: ECS GeForce100PM-M2 with Phoenix -Award Workstation BIOS
vcard: inno3D Nvidia 7200 GS PCI-E
ram: non-ECC 2 GB
processor: AMD LE 1640
vdriver: nvidia 185 proprietary activated

Would compiling a custom kernel with ECC disabled (if it is possible) work?

[Strepto (victor-rossetti)]

Probably a kernel recompile would do the job, I'll try to do the homework to see if it works

[Machiavelli (machiavelli)]

I do not suffer from this issue anymore. I'm running Nvidia driver 185.18.36.

I don't know what did it though.

[Pete24v (pete-martin)]

I was running 9.04 totally fine, and 8.10 before, no issues like this.

Did a complete fresh install of Karmic and this error is happening all the time. I have an AMD64bit processor and a MSi board with built in ATI graphics. I'm using the suggested proprietary driver too.

[Ian Sinclair (ian-sinclair)]

The ECC error notice appears when I try to print a photo from F-spot (and the printout is rubbish).

[Cyprian Guerra (cyprian-guerra)]

I see the fix is released but update manager didn't find it. How to get it?

In my case the problem occurred just after restart. When the gnome loaded it said the little thing showing if I'm online, offline, letting me restart, shutdown my gear, etc. couldn't run and asked if I want to remove it from my panel.

[Shobuz99 (shobuz99)]

In my case the problem began immediately after i upgraded to 9.10 from 9.04
I get an 'crash error' and it says kernel failure, or something..
I too, cannot get the fix from Update manager...

got any ideas?

________________________________
From: trespasser <email address hidden>
To: <email address hidden>
Sent: Sun, November 1, 2009 8:11:33 AM
Subject: [Bug 422536] Re: EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.

I see the fix is released but update manager didn't find it. How to get
it?

In my case the problem occurred just after restart. When the gnome
loaded it said the little thing showing if I'm online, offline, letting
me restart, shutdown my gear, etc. couldn't run and asked if I want to
remove it from my panel.

--
EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
https://bugs.launchpad.net/bugs/422536
You received this bug notification because you are a direct subscriber
of the bug.

Status in The Linux Kernel: Fix Released
Status in “kerneloops” package in Ubuntu: Fix Released
Status in “linux” package in Ubuntu: Fix Released

Bug description:
?

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: yoman82 3464 F.... pulseaudio
/dev/snd/pcmC0D0p: yoman82 3464 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xf9ff0000 irq 16'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,18491e01,00100001'
   Controls : 37
   Simple ctrls : 21
Date: Tue Sep 1 07:48:00 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=69c64130-cc6f-4a5b-952b-3ba4c893ba48
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-8-generic 2.6.31-8.28
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: root=UUID=19f3bdd6-1b33-48e0-8081-d00e178d9f7d ro splash vga=792
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
RelatedPackageVersions:
linux-backports-modules-2.6.31-8-generic N/A
linux-firmware 1.16
RfKill:
0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: 6.073813] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
Uname: Linux 2.6.31-8-generic x86_64
WifiSyslog:

WpaSupplicantLog:

dmi.bios.date: 04/24/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: M3A780GXH/128M
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd04/24/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A780GXH/128M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[bwallum (rbw2)]

When will the fix be available in the repos do you think? It occurs very regularly and I can't find a consistent pattern. I've been trying to get floppy drives working and the bug pops up all the time. I have absolutely no idea if the two are linked, just putting the idea across for determination.

[cyrulution (kube)]

help!

[cyrulution (kube)]

count plus one

[CupofDice (cupofdice-gmail)]

I have this same problem, on a AMD 64 with a Nvidia driver. Hoping for a fix.

[RagTimE (cragtime)]

hello still waiting for the fix please release it
i have installed some machines all "msi k9n v2 amd64 / ubuntu64" motherboards with this problem
i am on w7 at the moment ... i will use my ubuntu :)

regrets

[waterfull (waterfull)]

Not upgrade to 9.10 from 9.04.
Just upgrade in 9.10.
Becasue of locking something.

在2009-11-01，Shobuz99 <email address hidden> 写道：
>In my case the problem began immediately after i upgraded to 9.10 from 9.04
>I get an 'crash error' and it says kernel failure, or something..
>I too, cannot get the fix from Update manager...
>
>got any ideas?
>
>
>
>________________________________
>From: trespasser <email address hidden>
>To: <email address hidden>
>Sent: Sun, November 1, 2009 8:11:33 AM
>Subject: [Bug 422536] Re: EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
>
>I see the fix is released but update manager didn't find it. How to get
>it?
>
>In my case the problem occurred just after restart. When the gnome
>loaded it said the little thing showing if I'm online, offline, letting
>me restart, shutdown my gear, etc. couldn't run and asked if I want to
>remove it from my panel.
>
>--
>EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
>https://bugs.launchpad.net/bugs/422536
>You received this bug notification because you are a direct subscriber
>of the bug.
>
>Status in The Linux Kernel: Fix Released
>Status in “kerneloops” package in Ubuntu: Fix Released
>Status in “linux” package in Ubuntu: Fix Released
>
>Bug description:
>?
>
>ProblemType: KernelOops
>Annotation: Your system might become unstable now and might need to be restarted.
>Architecture: amd64
>AudioDevicesInUse:
>USER PID ACCESS COMMAND
>/dev/snd/controlC0: yoman82 3464 F.... pulseaudio
>/dev/snd/pcmC0D0p: yoman82 3464 F...m pulseaudio
>CRDA: Error: [Errno 2] No such file or directory
>Card0.Amixer.info:
>Card hw:0 'SB'/'HDA ATI SB at 0xf9ff0000 irq 16'
> Mixer name : 'Realtek ALC888'
> Components : 'HDA:10ec0888,18491e01,00100001'
> Controls : 37
> Simple ctrls : 21
>Date: Tue Sep 1 07:48:00 2009
>DistroRelease: Ubuntu 9.10
>Failure: oops
>HibernationDevice: RESUME=UUID=69c64130-cc6f-4a5b-952b-3ba4c893ba48
>MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
>NonfreeKernelModules: nvidia
>Package: linux-image-2.6.31-8-generic 2.6.31-8.28
>PccardctlIdent:
>
>PccardctlStatus:
>
>ProcCmdLine: root=UUID=19f3bdd6-1b33-48e0-8081-d00e178d9f7d ro splash vga=792
>ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
>RelatedPackageVersions:
>linux-backports-modules-2.6.31-8-generic N/A
>linux-firmware 1.16
>RfKill:
>0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>SourcePackage: linux
>Tags: kernel-oops
>Title: 6.073813] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
>Uname: Linux 2.6.31-8-generic x86_64
>WifiSyslog:
>
>WpaSupplicantLog:
>
>dmi.bios.date: 04/24/2009
>dmi.bios.vendor: American Megatrends Inc.
>dmi.bios.version: P1.00
>dmi.board.name: M3A780GXH/128M
>dmi.board.vendor: ASRock
>dmi.chassis.asset.tag: To Be Filled By O.E.M.
>dmi.chassis.type: 3
>dmi.chassis.vendor: To Be Filled By O.E.M.
>dmi.chassis.version: To Be Filled By O.E.M.
>dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd04/24/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A780GXH/128M:rvr:cvnToBeFille...

[Guilden_NL - Joop deBruin (guilden-nl)]

MSI K8n Neo4 motherboard. AMD 64, Nvidia Driver 185.

[k c davis (kcdavis)]

Not sure why the error system on my PC connected to this bug thread, but immediately on starting newly installed 9.10, on this Amd64 system with Nvidia audio and video (using, I believe ATM, the open source drivers) I'm getting persistent, essentially constant reports of "System encountered a serious kernel problem ... May be unstable" ....

Seems(?) to run okay though, so far.

No ECC memory in this box, but as someone noted, the Phenom processor might have the logic to support it.

[Jan Obrátil (obrys)]

Hello, this is not a bug I think. I have the same "problem". My motherboard can use both ECC and non-ECC RAMs. I use non-ECC ram and motherboard reports, that it use non-ECC and it can use ECC RAM. Not that it use ECC RAM as non-ECC RAM.

The bug should be corrected by lowering severity from warning to nocice or something like that in that case.

[stephan (stephan-polanski)]

On Mon, 02 Nov 2009 02:49:58 -0000
Guilden_NL - Joop deBruin <email address hidden> wrote:

> MSI K8n Neo4 motherboard. AMD 64, Nvidia Driver 185.
>

What means all about?

[Ian Sinclair (ian-sinclair)]

I could put up with the error messages if I had a useable machine, but I have found that I cannot use my accounts program (Grisbi) because of a segmentation fault when trying to save after a reconciliation. Add to thie being unable to print photos from F-spot or photoprint, and I wonder what to do now. Should I wait in the hope that it will all be sorted out (classed as "medium2, but not medium for me) or re-install 9.04 (which was stable and not significantly different otherwise in terms of useability).

[Electric Bill (electricbill)]

Biostar TF720 A2+ motherboard, AMD 8750 Phenom™ X3,M Station HT-1100 HTPC Media Center case, Antec 480 NeoPower power supply, 2GB Patriot PSD22G800KH RAM, Gigabyte GV-R467ZL 4670 1GB video card w/ATI/AMD proprietary FGLRX driver using Samsung LNS3251D HDTV as monitor.

Issues:
When booting into Karmic, using HDMI cable between GFX card and TV, I have to shut off the TV momentarily for the boot to continue - it stalls right after the Ubuntu boot selection page.
If I use a VGA cable it boots normally and I don't see theselection page.
Also having issues with wireless Mouse/keyboards dropping out soon after Ubuntu starts.

This computer had no issues with Jaunty or with Win 7 on another hard drive.

[Peter Struhar (struhlo)]

got this bug after karmic update, but i cant adjust anything mem related in bios to turn off/override ECC settings as suggsted but he bug output

my part of dmesg with appearance of the issue :
[ 11.313784] [fglrx] Maximum main memory to use for locked dma buffers: 3550 MBytes.
[ 11.313823] [fglrx] vendor: 1002 device: 9612 count: 1
[ 11.314167] [fglrx] ioport: bar 1, base 0x5000, size: 0x100
[ 11.314175] pci 0000:01:05.0: setting latency timer to 64
[ 11.314523] [fglrx] Kernel PAT support is enabled
[ 11.314561] [fglrx] module loaded - fglrx 8.66.2 [Sep 23 2009] with 1 minors
[ 11.320919] EDAC amd64_edac: Ver: 3.2.0 Oct 16 2009
[ 11.320998] EDAC amd64: This node reports that Memory ECC is currently disabled.
[ 11.321002] EDAC amd64: bit 0x400000 in register F3x44 of the MISC_CONTROL device (0000:00:18.3) should be enabled
[ 11.321005] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
[ 11.321006] Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
[ 11.321008] Might be a BIOS bug, if BIOS says ECC is enabled
[ 11.321009] Use of the override can cause unknown side effects.
[ 11.321020] amd64_edac: probe of 0000:00:18.2 failed with error -22

looks like there might be something with the module amd64_edac_mod :
user@ntb:~$ lsmod | grep -i edac
amd64_edac_mod 26688 0
edac_core 48876 1 amd64_edac_mod

which contains the suggested ecc_enable_override:
user@ntb:~$ modinfo amd64_edac_mod
filename: /lib/modules/2.6.31-14-generic/kernel/drivers/edac/amd64_edac_mod.ko
description: MC support for AMD64 memory controllers - Ver: 3.2.0 Oct 16 2009
author: SoftwareBitMaker: Doug Thompson, Dave Peterson, Thayne Harbaugh
license: GPL
srcversion: A01E9E7B99D4A25C946BF10
alias: pci:v00001022d00001302sv*sd*bc*sc*i*
alias: pci:v00001022d00001202sv*sd*bc*sc*i*
alias: pci:v00001022d00001102sv*sd*bc*sc*i*
depends: edac_core
vermagic: 2.6.31-14-generic SMP mod_unload modversions
parm: report_gart_errors:int
parm: ecc_enable_override:int
parm: edac_op_state:EDAC Error Reporting state: 0=Poll,1=NMI (int)

looks like all the amd64 processor family users in above posts have same related issue, maybe with shared mem video cards cause this. Mine is ATI HD RADEON 3200, 256MB shared.

[James Westby (james-w)]

Please refrain from changing the status of this bug report without giving
a rationale.

This bug is not yet fixed, but I just uploaded a change that will mean you
stop getting pestered about it. That change should hit your machines in
about a week after it has gone through testing.

I am well aware that this problem will go away, so reports that it is "fixed"
at that time will be useless. The problem will not be fixed, we will have just
stopped the nagging.

Thanks,

James

[Harry (harry33)]

James, is this the workaround you wrote?
"We disable apport on stable releases, but currently kerneloops still runs, which
causes apport to pop up with reports of kernel issues. We should therefore prevent
kerneloops from running as well."

[James Westby (james-w)]

Harry, that is correct.

Thanks,

James

[Ian Sinclair (ian-sinclair)]

Update today (Nov. 3) has no effect. Error message is still present, and applications are affected (Grisbi cannot save file, segmentation error; F-spot printouts area grey pattern, not of selected pix)

[Marco Massenzio (m-massenzio)]

Is anyone doing anything about this?
Hugely annoying, especially as it seems to be a bit of a red herring - system works fine and no adverse effect.

I'd be happy to know if that noisy crash detection nuisance can at least be disabled - it's lame, guys.... makes me feel like I'm using WIndows again: in terms of usefulness it's on a par with Office paperclip....

[Andy Whitcroft (apw)]

To reiterate there are two components to this issue:

1) the kernel is now producing this new WARNING: message related to chipset support for EEC where it is not enabled in the BIOS. For machines which do not have EEC at all there may not even be a BIOS option to enable it. The message itself mearly indicates that the feature is present in the chipset but not enabled; a normal situation.

2) kerneloops is falsly reporting this WARNING: message as if it was a WARN_ON; which it is not. Kerneloops needs to be fixed to more accuratly detect the correct WARN_ON output.

As is normal after release kerneloops itself is now disabled so although it might falsely trigger it will no longer trigger these errors. Kerneloops itself still needs to be fixed and as such that task remains open. The kernel is working as designed and therefore I will close it off Invalid as there is no kernel fault.

[speleovar (speleovar)]

i've just updated then upgraded kerneloops-daemon - and i've reboot too : it's same than before : same warning for this same bug.

[Electric Bill (electricbill)]

I also previously reported this bug with my Biostar rig (post 179).

Today I installed Karmic on a Foxconn A7DA-S motherboard with an AMD 940 Phenom II, Corsair CMPSU-650TX power supply, 4GB (2x1GB) G.Skill F2-8500CL5D RAM, Asus EAH 3870 512MB video card using HDMI to a Samsung LNS3251D HDTV.
Same issue and bug report.
When booting I get as far as the Grub selection screen and then I have to unplug the HDMI cable for the boot to continue.
The cable disconnect only has to last a few seconds for the boot to continue.
With the Biostar I can quickly shut the TV on and off but the Foxconn has to be momentarily disconnected.

The Bioster TF720 A2+ uses an NVIDIA nForce 720a chipset and has integrated Geforce 8100 based graphics although I'm using a Radeon 4670 discrete video card.
The Foxconn A7DA-S uses AMD® 790GX + SB750 chipsets and has integrated AMD HD3300 based graphics although I'm using a Radeon 3870 discrete video card.

Both computers will boot normally with my Samsung T220HD monitor/LCD TV using HDMI interface.
Both rigs use DDR2 SDRAM non ECC.
Both have multiple operating systems on separate hard drives.
Win 7, XP and Ubuntu Jaunty but the problems only happen with Karmic.

Hope this information helps.

[tjw (tjw-tjw)]

I have a AsRock K10N78 motherboard. Everything worked fine until I installed the qemu-kvm package then I started getting this error. To troubleshoot, I loaded the Failsafe Defaults in by BIOS and this error was gone. I went back into BIOS and re-enabled everything that I had changed previously and it turned out to be a feature called "CPU Quiet Fan" that caused the trouble. I can reproduce the error be toggling this feature on.

I don't know if this will help in diagnosing this bug, but I suggest resetting your BIOS to defaults to see if it works for you too.

[Frank Groeneveld (frankgroeneveld)]

Why is it invalid? It's happening for a lot of people and it's quite annoying...

[Giorgos Kostopoulos (giorgos67)]

My own BIOS, doesn't even have an ECC entry.
(I suspecting, that I don't even have such type of memory).

Greets!!! :-)

[Andy Whitcroft (apw)]

@Frank Groeneveld -- this bug is Invalid for the linux package, as there is no bug in the kernel. The bug is in the kerneloops package which is _incorrectly_ reporting this mild warning from the kernel as a crash; which it is not. The kernel is not to blame, the kernel task therefore should be Invalid. The kerneloops task is still open as the bug is not yet fixed in kerneloops. However, you should no longer be recieving popups for this error if you have installed the latest updates as kerneloops should now be disabled.

[Harry (harry33)]

I confirm I no longer get kerneloops popups, which report a crash and a serious kernel issue.
So now the kerneloops issue is hidden.
I have the latest kerneloops installed: kerneloops-daemon_0.12+git20090217-1ubuntu4.1

[RickardJ (rickardj)]

I STILL get this error, and my system is up to date.

[pablomme (pablomme)]

Is the kerneloops fix in the regular karmic-updates repository, or does one have to enable karmic-proposed?

[Harry (harry33)]

pablomme,

The kerneloops-daemon has been moved from Karmic-proposed to Karmic-updates on 3rd November.

[Andreas Noteng (andreas-noteng)]

This error appeared for the first time today, it also seems to slow down the system, or at least network speed. Also getting the following new errors in dmesg:
[10678.935979] ACPI: BIOS _OSI(Linux) query ignored
[10806.726460] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x00000020
[11676.858774] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x00000020

No updates installed today. I'll try to reboot and check if the message reappears.

[eunix (zen143817)]

The system which generated this error warning was a Gigabyte motherboard + AMD Socket AM2 M61P-S3. The loaded Award BIOS does NOT have an enable/disable ECC function.
eunix

[mad (hm-a-bode)]

after updating new kernel generic: img-2.6.31-15-generic
today, error warning is gone away
matze

[Martin Pitt (pitti)]

Oh, it was included in the current SRU? The changelog of linux does not seem to mention this. All the better, though.

[bwallum (rbw2)]

Fresh AMD64 Karmic install, non ECC for DDR 400 memory. Latest updates 13:35 GMT Tuesday 10th November.
Five instances of bug upon restart once all updates installed.

[fyo (fyo)]

Fresh AMD64 Karmic install, all updates, non-ECC DDR400 memory.

Bug STILL occurs.

[Jeff (jdorenbush)]

Seems to be fixed for me. I've been updating regularly. Noticed the problem stopped occurring a day or two ago.

[Shaved Wookie (shavedwookie)]

Problem seems to have disappeared for me, but then I also changed the ECC settings in my BIOS.

[dirk (dirkmeissner72)]

Yes, after the update the warning is gone.

--
oscar <email address hidden>

[bwallum (rbw2)]

2.6.31-15 kernel appears to fix the issue but I understand this just mutes reporting in the top (default) panel. Is this still the case? Where can I check to see if any log files have picked up the problem (if it is just muted)?

[bwallum (rbw2)]

Found it in System>Administration>Log File Viewer:messages

Nov 13 08:48:50 ubuntu-bob kernel: [ 13.953926] EDAC MC: Ver: 2.1.0 Nov 10 2009
Nov 13 08:48:50 ubuntu-bob kernel: [ 13.983049] EDAC amd64_edac: Ver: 3.2.0 Nov 10 2009
Nov 13 08:48:50 ubuntu-bob kernel: [ 14.001782] EDAC amd64: This node reports that Memory ECC is currently disabled.
Nov 13 08:48:50 ubuntu-bob kernel: [ 14.001789] EDAC amd64: bit 0x400000 in register F3x44 of the MISC_CONTROL device (0000:00:18.3) should be enabled
Nov 13 08:48:50 ubuntu-bob kernel: [ 14.001792] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
Nov 13 08:48:50 ubuntu-bob kernel: [ 14.001794] Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
Nov 13 08:48:50 ubuntu-bob kernel: [ 14.001795] Might be a BIOS bug, if BIOS says ECC is enabled
Nov 13 08:48:50 ubuntu-bob kernel: [ 14.001796] Use of the override can cause unknown side effects.
Nov 13 08:48:50 ubuntu-bob kernel: [ 14.001824] amd64_edac: probe of 0000:00:18.2 failed with error -22

[AndyP (mentalguitar343-nyc)]

a) I will now go into my bios and check that ECC is enabled.
Perhaps the restricted dialogue box could request this before installing the driver that should not function.
b)if Unbunto would list the recommended Nvidia driver first on the list of resticted drivers, the install would be easier for the user
Why are many software developers unable to perform pre-release usability testing? We need to be more sensiitive to the average user difficulty reading error messages!

[GroovyMotion (flywaver)]

I can confirm that the issue is gone and there is no error message in the log viewer! :D

[rajesh (bhatt-rajesh20)]

thanks to all the issue is gone.

On Sat, Nov 21, 2009 at 11:01 PM, Flywaver <email address hidden> wrote:

> I can confirm that the issue is gone and there is no error message in
> the log viewer! :D
>
> --
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> https://bugs.launchpad.net/bugs/422536
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[$lunacy (atouchoflunacy)]

Bug apparently fixed for me, too.

I was away from this computer for a while, and applied a whole pile of
updates in a row, so I'm not sure which one did it, but the problem doesn't
seem to be occurring anymore.

On Thu, Nov 12, 2009 at 4:36 PM, Jeff <email address hidden> wrote:

> Seems to be fixed for me. I've been updating regularly. Noticed the
> problem stopped occurring a day or two ago.
>
> --
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> https://bugs.launchpad.net/bugs/422536
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in KDE frontend for sudo: Invalid
> Status in The Linux Kernel: New
> Status in “kerneloops” package in Ubuntu: Triaged
> Status in “linux” package in Ubuntu: Invalid
> Status in “kerneloops” source package in Karmic: New
> Status in “linux” source package in Karmic: Fix Committed
>
> Bug description:
> The edac_amd64 module attempts to load on many systems. If the system
> doesn't have ECC
> memory, or it is disabled in the BIOS, then the module prints
>
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> Either Enable ECC in the BIOS, or use the 'ecc_enable_override'
> parameter.
> Might be a BIOS bug, if BIOS says ECC is enabled
> Use of the override can cause unknown side effects.
>
> before failing to load. This won't cause issues for most people that see
> the message.
>
> kerneloops picks this up as kernel problem as the "WARNING:" looks a lot
> like what
> you get when using WARN().
>
> There are several aspects to this issue:
>
> * linux
> - something attempts to load the module when perhaps it doesn't need to
> (unclear at this point)
> - the module looks like it is using WARN() when it isn't, and is
> arguably more SHOUTY than
> it needs to be.
> * kerneloops
> - picks up this as WARN() when it isn't.
> - Was accidentally left enabled for the stable release, people
> shouldn't be getting asked to report
> this at this point.
> - Isn't very good at dealing with repeat issues, causing more reports
> to be sent than are needed.
>
> and possibly others as well.
>
> ProblemType: KernelOops
> Annotation: Your system might become unstable now and might need to be
> restarted.
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: yoman82 3464 F.... pulseaudio
> /dev/snd/pcmC0D0p: yoman82 3464 F...m pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'SB'/'HDA ATI SB at 0xf9ff0000 irq 16'
> Mixer name : 'Realtek ALC888'
> Components : 'HDA:10ec0888,18491e01,00100001'
> Controls : 37
> Simple ctrls : 21
> Date: Tue Sep 1 07:48:00 2009
> DistroRelease: Ubuntu 9.10
> Failure: oops
> HibernationDevice: RESUME=UUID=69c64130-cc6f-4a5b-952b-3ba4c893ba48
> MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
> NonfreeKernelModules: nvidia
> Package: linux-image-2.6.31-8-generic 2.6.31-8.28
> PccardctlIdent:
>
> PccardctlStatus:
>
> ProcCmdLine: root=UUID=19f3bdd6-1b33-48e0-8081-d00e178d9f7d ro splash
...

[Jarl (jarl-dk)]

I still have this warning (I ran apt-get upgrade 2009-11-23) on my Asus M3N-HD HDMI motherboard. I see that my BIOS version is 1502 (far from the latest), could the warnings have anything to do with that?

Jarl

[Robb Munson (r.munson)]

please quit putting me as a subscriber, I do not have issues with any said
bugs that I am ever subscribed to by others. thank you.

On Tue, Nov 24, 2009 at 3:49 AM, Jarl <email address hidden> wrote:

> I still have this warning (I ran apt-get upgrade 2009-11-23) on my Asus
> M3N-HD HDMI motherboard. I see that my BIOS version is 1502 (far from
> the latest), could the warnings have anything to do with that?
>
> Jarl
>
> --
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> https://bugs.launchpad.net/bugs/422536
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in KDE frontend for sudo: Invalid
> Status in The Linux Kernel: New
> Status in “kerneloops” package in Ubuntu: Triaged
> Status in “linux” package in Ubuntu: Invalid
> Status in “kerneloops” source package in Karmic: New
> Status in “linux” source package in Karmic: Fix Committed
>
> Bug description:
> The edac_amd64 module attempts to load on many systems. If the system
> doesn't have ECC
> memory, or it is disabled in the BIOS, then the module prints
>
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> Either Enable ECC in the BIOS, or use the 'ecc_enable_override'
> parameter.
> Might be a BIOS bug, if BIOS says ECC is enabled
> Use of the override can cause unknown side effects.
>
> before failing to load. This won't cause issues for most people that see
> the message.
>
> kerneloops picks this up as kernel problem as the "WARNING:" looks a lot
> like what
> you get when using WARN().
>
> There are several aspects to this issue:
>
> * linux
> - something attempts to load the module when perhaps it doesn't need to
> (unclear at this point)
> - the module looks like it is using WARN() when it isn't, and is
> arguably more SHOUTY than
> it needs to be.
> * kerneloops
> - picks up this as WARN() when it isn't.
> - Was accidentally left enabled for the stable release, people
> shouldn't be getting asked to report
> this at this point.
> - Isn't very good at dealing with repeat issues, causing more reports
> to be sent than are needed.
>
> and possibly others as well.
>
> ProblemType: KernelOops
> Annotation: Your system might become unstable now and might need to be
> restarted.
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: yoman82 3464 F.... pulseaudio
> /dev/snd/pcmC0D0p: yoman82 3464 F...m pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info <http://card0.amixer.info/>:
> Card hw:0 'SB'/'HDA ATI SB at 0xf9ff0000 irq 16'
> Mixer name : 'Realtek ALC888'
> Components : 'HDA:10ec0888,18491e01,00100001'
> Controls : 37
> Simple ctrls : 21
> Date: Tue Sep 1 07:48:00 2009
> DistroRelease: Ubuntu 9.10
> Failure: oops
> HibernationDevice: RESUME=UUID=69c64130-cc6f-4a5b-952b-3ba4c893ba48
> MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
> NonfreeKernelModules: nvidia
> Package: linux-image-2.6.31-8-generic 2.6.31-8.28
> PccardctlIdent:
>
> PccardctlStatus:
>
> ProcCmdLine: root=UUID=19f3bdd6-1b...

[Robb Munson (r.munson)]

I keep getting subscribed to bugs such as this, can someone please tell me how to stop this? thanks (I do not have any related bugs that I personally sent in, but I keep getting subscribed to duplicates...and the duplicates lead to these bugs...which lead to others, turns into a massive chain reaction that bombards my inbox and really infuriates me.)

[Jerome R (1dahut)]

Bug apparently fixed for me, too.

i enabled update manager from startup.. And no problem !

->2.6.31-15 kernel appears to fix the issue.

[Jarl (jarl-dk)]

As follow up on comment 214, I just upgraded to the latest stable bios (ver 2102), and it didn't change anything regarding this bug. I still see this in my log.

[Jarl (jarl-dk)]

I am sorry, it seems like my comments are a bit out-of-place for this bug. To be honest I see these warnings in my /var/log/messages, but there is no kerneloops/kernel panic. So basically my system is running fine, I just kgot these misleading warnings in /var/log/messages. Tell me if this bug is concerning the more serious situation where the system is not able to boot, in which case I will mark the bug "not affecting me". I am sorry if my comments have been misleading...

[ethernet (lenski169)]

this problem was not there until i downloaded firestarter. system had no errors. i had a problem with my ethernet card it need to be reset after i uninstalled firestarter . i had not downloaded any upgrades at all. to fix the ethernet problem i uninstalled the card and rebooted. i enable it and rebooted everything works. if i boot without the ethernet plugged in the warning comes back with ethernet no warning. i ran a dio on memory and hardware everything is great.

ubuntu 9.10 rocks (outstanding product) (its years advanced to the micro shiiiiiisnt that they sell and control.) excuse the word i thought about changing it for a split second but whats true is true.

hope this helps

thank you ubuntu,
ethernet

[Carlos Andres Avila Gutierrez (andrewkdna)]

My computer hardware configuration
-->AMD Atlon X2 5200
-->Board MSI K9N6GM
-->2GB RAM
-->Hard Disk 500GB Hitachi SATA and other 320GB Hitachi SATA

I install Ubuntu 9.10.
When I put hibernation mode, then I try to startup my pc and one error message appears.

[Minux (bruno-seradzski)]

1- Message en Anglais que je ne comprend pas...
2-Grub ne me donne plus le choix de démarrage des autres OS installés sur mon ordinateur et est très long.

[Minux (bruno-seradzski)]

Le dimanche 03 janvier 2010 à 09:06 +0000, Martin Pitt a écrit :
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Fix Released
>
Merci, mais je ne comprend rien à l'Englais...

[Minux (bruno-seradzski)]

Le dimanche 03 janvier 2010 à 01:37 +0000, belzaroth a écrit :
> ** Changed in: linux (Ubuntu)
> Status: Invalid => Confirmed
>
Merci pour votre réponse, malheureusement je ne parle ni ne lis
l'Englais suffisement bien pour saisir pleinement le sense de votre
méssage.
Je vais poster celle-ci sur un forum français afin d'obtenir une
solution.

Amicalement;

Bruno Séradzski.

[pablomme (pablomme)]

@Minux: http://translate.google.com

[Martin Pitt (pitti)]

Don't change bug states without further explanation.

[Frdbrkl (frdbrkl)]

 Anecdotally speaking, I never experienced the bug until I booted my machine with the External Lacie Firewire Hard Drive plugged into the machine but "switched off" at the hard drive itself (powered down by switch in the external enclosure).

I'm not a programmer, but thought this may provide a clue (it explains the 1394 failure comments on the boot screen though).

[Minux (bruno-seradzski)]

Selon Frdbrkl <email address hidden>:

> Anecdotally speaking, I never experienced the bug until I booted my
> machine with the External Lacie Firewire Hard Drive plugged into the
> machine but "switched off" at the hard drive itself (powered down by
> switch in the external enclosure).
>
> I'm not a programmer, but thought this may provide a clue (it explains
> the 1394 failure comments on the boot screen though).
>
>
Merci pour cette réponse.
Effectivement j'ai un Disque Dur Externe branché à mon PC via une prise USB,
et celui-ci était branché au PC ( éteint) lorsque j'ai procédé à l'installation.
Je vais procédé à des testes sans ce DD externe.
Cordialement;
Bruno Séradzski.

[Shane Fagan (shanepatrickfagan)]

Please dont change the status of bugs without saying why. Please read the comments they explain its not an issue its just apport picking up on a kernel warning.

[Tolea (tolea-photo)]

i didn't felt problems with this bug.. and maibe i wownt... (after readiong the info below)
but in anny case ... it's not a normal reaction off the system...

P.S. thanks for your work in the opensource projects :)

[Minux (bruno-seradzski)]

Selon Tolea <email address hidden>:

> i didn't felt problems with this bug.. and maibe i wownt... (after readiong
> the info below)
> but in anny case ... it's not a normal reaction off the system...
>
> P.S. thanks for your work in the opensource projects :)
>
I'have install 9.04 64 bit, it's ok and update to 9.10 it's ok no problems.
Sorry for my English;
Bruno Séradzski.
> --
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> https://bugs.launchpad.net/bugs/422536
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in KDE frontend for sudo: Invalid
> Status in The Linux Kernel: Invalid
> Status in “kerneloops” package in Ubuntu: Fix Released
> Status in “linux” package in Ubuntu: Fix Released
> Status in “kerneloops” source package in Karmic: New
> Status in “linux” source package in Karmic: Fix Committed
>
> Bug description:
> The edac_amd64 module attempts to load on many systems. If the system doesn't
> have ECC
> memory, or it is disabled in the BIOS, then the module prints
>
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> Either Enable ECC in the BIOS, or use the 'ecc_enable_override'
> parameter.
> Might be a BIOS bug, if BIOS says ECC is enabled
> Use of the override can cause unknown side effects.
>
> before failing to load. This won't cause issues for most people that see the
> message.
>
> kerneloops picks this up as kernel problem as the "WARNING:" looks a lot
> like what
> you get when using WARN().
>
> There are several aspects to this issue:
>
> * linux
> - something attempts to load the module when perhaps it doesn't need to
> (unclear at this point)
> - the module looks like it is using WARN() when it isn't, and is
> arguably more SHOUTY than
> it needs to be.
> * kerneloops
> - picks up this as WARN() when it isn't.
> - Was accidentally left enabled for the stable release, people shouldn't
> be getting asked to report
> this at this point.
> - Isn't very good at dealing with repeat issues, causing more reports to
> be sent than are needed.
>
> and possibly others as well.
>
> ProblemType: KernelOops
> Annotation: Your system might become unstable now and might need to be
> restarted.
> Architecture: amd64
> AudioDevicesInUse:
>  USER PID ACCESS COMMAND
>  /dev/snd/controlC0: yoman82 3464 F.... pulseaudio
>  /dev/snd/pcmC0D0p: yoman82 3464 F...m pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
>  Card hw:0 'SB'/'HDA ATI SB at 0xf9ff0000 irq 16'
>    Mixer name : 'Realtek ALC888'
>    Components : 'HDA:10ec0888,18491e01,00100001'
>    Controls : 37
>    Simple ctrls : 21
> Date: Tue Sep 1 07:48:00 2009
> DistroRelease: Ubuntu 9.10
> Failure: oops
> HibernationDevice: RESUME=UUID=69c64130-cc6f-4a5b-952b-3ba4c893ba48
> MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
> NonfreeKernelModules: nvidia
> Package: linux-image-2.6.31-8-generic 2.6.31-8.28
> PccardctlIdent:
>
> PccardctlStatus:
>
> ProcCmdLine: root=UUID=19f3bdd6-1b33-48e0-808...

[Sense Egbert Hofstede (sense)]

Please don't assign yourself to a bug if you're not going to work on it and please don't change the status without an explanation of why you're reopening the bug.

[wesattexas (r-w-j)]

I thought this was fixed!
Just now built fresh AMD64 system from CD and got this error.
Did Complete recommended upgrade - Sunday Jan24 10 PM. -- Still Get same Error.
ASUS M2NPV-VM main board with NVIDIA GeForce .
Have not installed (ver 185) (or any) NVIDIA drivers.

I reboot and about 1 minute later: An Error Message saying system may not be stable.
If there is a fix out there, how do I get it on my system

[Shane Fagan (shanepatrickfagan)]

The fix hasnt made it on to the cd yet. So the problem is still on the cd just update the system and it will stop.

[Mark Capoferri (cmarksimon)]

I just ran into this bug which appears patched. However, it came up for me today 2010-01-25, and I thought this kind of problem auto-updated with the system package managers. I am running Ubuntu 9.10 Live. My systems including nine motherboards were attacked by a bios32/eeprom/LKM rootkit some time ago. I've only recently been able to somewhat bypass the original fully crippled state using recent Linux/Unix distros. This machine is based on a DFI Infinity socket 939 mb, AMD Opteron 170, MSI 6600GT graphics, 1GB Corsair 3200 2-3-3-6. The problems began when I first installed one of my legal OEM copies of Winders and used win up(&down)date. The bios was replaced/supplemented with the usual binary blobs created with Busybox and while trying to appear as unix, are basically embedded smbios with efi and monkeyboy fingerprints(aka ntfs) everywhere. Oh, it also has embedded a debian based kernel (I believe when I first installed openSUSE about a year ago) which has a dual root. Translated, my attempts at hard drive install always are fused into a crippled configuration with enough loops, devices, and processes to imitate HAL. The end result is basically always the same, no hardware control, and a preset network interface that appears to be part of some industry initiative in anticipation of passage of the new trade bill being fought by the EFF and others. I guess they're experimenting on people like me who have been reported by an m$ tech (falsely) as having commercially pirated a copy of WindersXP, Anyone want to tackle a core dump?? MC sorry if I've caused any problems posting this here, but I'm kind of desperate as I have a BS in Architecture, not Computer Science, and all I've written comes from what I've been able to teach myself the past year or so! Also, at 55 I'm not getting any younger and this is getting old!

[Mark Capoferri (cmarksimon)]

Here's the dmesg out that should have accompanied my prior comment:

root@ubuntu:/# dmesg
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.31-14-generic (buildd@crested) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 (Ubuntu 2.6.31-14.48-generic)
[ 0.000000] Command line: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash acpi=off noapic nolapic edd=on nodmraid apt-setup/restricted=false apt-setup/multiverse=false
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
[ 0.000000] BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 0000000040000000 (usable)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] DMI 2.2 present.
[ 0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0x40000 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-C7FFF write-protect
[ 0.000000] C8000-FFFFF uncachable
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0000000000 mask FFC0000000 write-back
[ 0.000000] 1 disabled
[ 0.000000] 2 disabled
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] Scanning 0 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000010000 (reserved)
[ 0.000000] modified: 0000000000010000 - 000000000009f400 (usable)
[ 0.000000] modified: 000000000009f400 - 00000000000a0000 (reserved)
[ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 0000000040000000 (usable)
[ 0.000000] modified: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] modified: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] initial memory mapped : 0 - 20000000
[ 0.000000] init_memory_mapping: 0000000000000000-0000000040000000
[ 0.000000] Using x86 segment limits to approximate NX protection
[ 0.000000] 0000000000 - 0040000000 page 2M
[ 0.000000] kernel direct mapping tables up to 40000000 @ 10000-12000
[ 0.000000] RAMDISK: 3fa3e000 - 3ffcf2a4
[ 0.000000] Scanning NUMA topology in Northbridge 24
[ 0.000000] No NUMA configuration found
[ ...

[Dave Morley (davmor2)]

Please Read THIS!

This bug has been fixed as a security update. It does not affect the cd in any shape or form. The patch is applied post install when you install the update.

The Patch is not on the cd it therefore will always show up in live sessions and on the initial install until such time as you have installed the update.

Post update is the only time you need comment on this bug. That is to say once the update is in place if you are still being affected by this bug then comment please.

Many Thanks for your time.

[Francisco T. (leviatan1)]

I have karmic with all updates, with kernel 2.6.31-17-generic
and the problem continues:
[ 13.016907] EDAC amd64_edac: Ver: 3.2.0 Dec 10 0009
[ 13.017153] EDAC amd64: This node reports that Memory ECC is currently disabled.
[ 13.017156] EDAC amd64: bit 0x400000 in register F3x44 of the MISC_CONTROL device (0000:00:18.3) should be enabled
[ 13.017158] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
[ 13.017159] Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
[ 13.017160] Might be a BIOS bug, if BIOS says ECC is enabled
[ 13.017160] Use of the override can cause unknown side effects.
[ 13.017169] amd64_edac: probe of 0000:00:18.2 failed with error -22

[mohand (kamezzug1)]

ça serais bien d'avoir cette page en français, j'ai rien compris merci

[mohand (kamezzug1)]

merci beaucoup mais je ne comprends pas tout en anglais .

--- En date de : Lun 1.2.10, Shane Fagan <email address hidden> a écrit :

De: Shane Fagan <email address hidden>
Objet: [Bug 422536] Re: EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
À: <email address hidden>
Date: Lundi 1 Février 2010, 12h02

** Changed in: linux (Ubuntu)
       Status: Incomplete => Fix Committed

** Changed in: linux (Ubuntu)
       Status: Fix Committed => Fix Released

** Changed in: kerneloops (Ubuntu Karmic)
       Status: New => Fix Released

--
EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
https://bugs.launchpad.net/bugs/422536
You received this bug notification because you are a direct subscriber
of the bug.

Status in KDE frontend for sudo: Invalid
Status in The Linux Kernel: Invalid
Status in “kerneloops” package in Ubuntu: Fix Released
Status in “linux” package in Ubuntu: Fix Released
Status in “kerneloops” source package in Karmic: Fix Released
Status in “linux” source package in Karmic: Fix Committed

Bug description:
The edac_amd64 module attempts to load on many systems. If the system doesn't have ECC
memory, or it is disabled in the BIOS, then the module prints

EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
    Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
    Might be a BIOS bug, if BIOS says ECC is enabled
    Use of the override can cause unknown side effects.

before failing to load. This won't cause issues for most people that see the message.

kerneloops picks this up as  kernel problem as the "WARNING:" looks a lot like what
you get when using WARN().

There are several aspects to this issue:

  * linux
     - something attempts to load the module when perhaps it doesn't need to (unclear at this point)
     - the module looks like it is using WARN() when it isn't, and is arguably more SHOUTY than
       it needs to be.
  * kerneloops
     - picks up this as WARN() when it isn't.
     - Was accidentally left enabled for the stable release, people shouldn't be getting asked to report
        this at this point.
     - Isn't very good at dealing with repeat issues, causing more reports to be sent than are needed.

and possibly others as well.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  yoman82    3464 F.... pulseaudio
 /dev/snd/pcmC0D0p:   yoman82    3464 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xf9ff0000 irq 16'
   Mixer name    : 'Realtek ALC888'
   Components    : 'HDA:10ec0888,18491e01,00100001'
   Controls      : 37
   Simple ctrls  : 21
Date: Tue Sep  1 07:48:00 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=69c64130-cc6f-4a5b-952b-3ba4c893ba48
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-8-generic 2.6.31-8.28
PccardctlIdent:

PccardctlStatus:
...

[mohand (kamezzug1)]

je vous rmerci beaucoups mais je ne comprends pas tout en anglais

--- En date de : Lun 1.2.10, Ramdas <email address hidden> a écrit :

De: Ramdas <email address hidden>
Objet: [Bug 422536] Re: EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
À: <email address hidden>
Date: Lundi 1 Février 2010, 11h34

** Changed in: linux (Ubuntu)
       Status: Fix Released => Incomplete

--
EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
https://bugs.launchpad.net/bugs/422536
You received this bug notification because you are a direct subscriber
of the bug.

Status in KDE frontend for sudo: Invalid
Status in The Linux Kernel: Invalid
Status in “kerneloops” package in Ubuntu: Fix Released
Status in “linux” package in Ubuntu: Incomplete
Status in “kerneloops” source package in Karmic: New
Status in “linux” source package in Karmic: Fix Committed

Bug description:
The edac_amd64 module attempts to load on many systems. If the system doesn't have ECC
memory, or it is disabled in the BIOS, then the module prints

EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
    Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
    Might be a BIOS bug, if BIOS says ECC is enabled
    Use of the override can cause unknown side effects.

before failing to load. This won't cause issues for most people that see the message.

kerneloops picks this up as  kernel problem as the "WARNING:" looks a lot like what
you get when using WARN().

There are several aspects to this issue:

  * linux
     - something attempts to load the module when perhaps it doesn't need to (unclear at this point)
     - the module looks like it is using WARN() when it isn't, and is arguably more SHOUTY than
       it needs to be.
  * kerneloops
     - picks up this as WARN() when it isn't.
     - Was accidentally left enabled for the stable release, people shouldn't be getting asked to report
        this at this point.
     - Isn't very good at dealing with repeat issues, causing more reports to be sent than are needed.

and possibly others as well.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  yoman82    3464 F.... pulseaudio
 /dev/snd/pcmC0D0p:   yoman82    3464 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xf9ff0000 irq 16'
   Mixer name    : 'Realtek ALC888'
   Components    : 'HDA:10ec0888,18491e01,00100001'
   Controls      : 37
   Simple ctrls  : 21
Date: Tue Sep  1 07:48:00 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=69c64130-cc6f-4a5b-952b-3ba4c893ba48
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-8-generic 2.6.31-8.28
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: root=UUID=19f3bdd6-1b33-48e0-8081-d00e178d9f7d ro splash vga=792
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-8-gen...

[aftertaf (david-wooffindin)]

errr....
Dave, post #238 : i think I am in this case
here's my dmesg as of 10 minutes ago . . .

Linux version 2.6.31-20-generic (buildd@yellow) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9) ) #57-Ubuntu

[Minux (bruno-seradzski)]

Selon aftertaf <email address hidden>:

> errr....
> Dave, post #238 : i think I am in this case
> here's my dmesg as of 10 minutes ago . . .
>
> Linux version 2.6.31-20-generic (buildd@yellow) (gcc version 4.4.1
> (Ubuntu 4.4.1-4ubuntu9) ) #57-Ubuntu
>
Après mise à jour, le bug disparait.
>
> ** Attachment added: "karmic latest kernel :Linux version 2.6.31-20-generic
> (buildd@yellow) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9) ) #57-Ubuntu"
> http://launchpadlibrarian.net/38902858/dmesg.txt
>
> --
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> https://bugs.launchpad.net/bugs/422536
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in KDE frontend for sudo: Invalid
> Status in The Linux Kernel: Invalid
> Status in “kerneloops” package in Ubuntu: Fix Released
> Status in “linux” package in Ubuntu: Fix Released
> Status in “kerneloops” source package in Karmic: Fix Committed
> Status in “linux” source package in Karmic: Fix Released
>
> Bug description:
> The edac_amd64 module attempts to load on many systems. If the system doesn't
> have ECC
> memory, or it is disabled in the BIOS, then the module prints
>
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> Either Enable ECC in the BIOS, or use the 'ecc_enable_override'
> parameter.
> Might be a BIOS bug, if BIOS says ECC is enabled
> Use of the override can cause unknown side effects.
>
> before failing to load. This won't cause issues for most people that see the
> message.
>
> kerneloops picks this up as kernel problem as the "WARNING:" looks a lot
> like what
> you get when using WARN().
>
> There are several aspects to this issue:
>
> * linux
> - something attempts to load the module when perhaps it doesn't need to
> (unclear at this point)
> - the module looks like it is using WARN() when it isn't, and is
> arguably more SHOUTY than
> it needs to be.
> * kerneloops
> - picks up this as WARN() when it isn't.
> - Was accidentally left enabled for the stable release, people shouldn't
> be getting asked to report
> this at this point.
> - Isn't very good at dealing with repeat issues, causing more reports to
> be sent than are needed.
>
> and possibly others as well.
>
> ProblemType: KernelOops
> Annotation: Your system might become unstable now and might need to be
> restarted.
> Architecture: amd64
> AudioDevicesInUse:
>  USER PID ACCESS COMMAND
>  /dev/snd/controlC0: yoman82 3464 F.... pulseaudio
>  /dev/snd/pcmC0D0p: yoman82 3464 F...m pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
>  Card hw:0 'SB'/'HDA ATI SB at 0xf9ff0000 irq 16'
>    Mixer name : 'Realtek ALC888'
>    Components : 'HDA:10ec0888,18491e01,00100001'
>    Controls : 37
>    Simple ctrls : 21
> Date: Tue Sep 1 07:48:00 2009
> DistroRelease: Ubuntu 9.10
> Failure: oops
> HibernationDevice: RESUME=UUID=69c64130-cc6f-4a5b-952b-3ba4c893ba48
> MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
> NonfreeKernelModules: nvidia
> ...

[Minux (bruno-seradzski)]

Selon Sense Hofstede <email address hidden>:

> ** Changed in: linux (Ubuntu)
> Assignee: michael (michaeljwarner) => (unassigned)
>
Après mise à jour, le bug disparait.
> --
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> https://bugs.launchpad.net/bugs/422536
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in KDE frontend for sudo: Invalid
> Status in The Linux Kernel: Invalid
> Status in “kerneloops” package in Ubuntu: Fix Released
> Status in “linux” package in Ubuntu: Fix Released
> Status in “kerneloops” source package in Karmic: Fix Committed
> Status in “linux” source package in Karmic: Fix Released
>
> Bug description:
> The edac_amd64 module attempts to load on many systems. If the system doesn't
> have ECC
> memory, or it is disabled in the BIOS, then the module prints
>
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> Either Enable ECC in the BIOS, or use the 'ecc_enable_override'
> parameter.
> Might be a BIOS bug, if BIOS says ECC is enabled
> Use of the override can cause unknown side effects.
>
> before failing to load. This won't cause issues for most people that see the
> message.
>
> kerneloops picks this up as kernel problem as the "WARNING:" looks a lot
> like what
> you get when using WARN().
>
> There are several aspects to this issue:
>
> * linux
> - something attempts to load the module when perhaps it doesn't need to
> (unclear at this point)
> - the module looks like it is using WARN() when it isn't, and is
> arguably more SHOUTY than
> it needs to be.
> * kerneloops
> - picks up this as WARN() when it isn't.
> - Was accidentally left enabled for the stable release, people shouldn't
> be getting asked to report
> this at this point.
> - Isn't very good at dealing with repeat issues, causing more reports to
> be sent than are needed.
>
> and possibly others as well.
>
> ProblemType: KernelOops
> Annotation: Your system might become unstable now and might need to be
> restarted.
> Architecture: amd64
> AudioDevicesInUse:
>  USER PID ACCESS COMMAND
>  /dev/snd/controlC0: yoman82 3464 F.... pulseaudio
>  /dev/snd/pcmC0D0p: yoman82 3464 F...m pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
>  Card hw:0 'SB'/'HDA ATI SB at 0xf9ff0000 irq 16'
>    Mixer name : 'Realtek ALC888'
>    Components : 'HDA:10ec0888,18491e01,00100001'
>    Controls : 37
>    Simple ctrls : 21
> Date: Tue Sep 1 07:48:00 2009
> DistroRelease: Ubuntu 9.10
> Failure: oops
> HibernationDevice: RESUME=UUID=69c64130-cc6f-4a5b-952b-3ba4c893ba48
> MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
> NonfreeKernelModules: nvidia
> Package: linux-image-2.6.31-8-generic 2.6.31-8.28
> PccardctlIdent:
>
> PccardctlStatus:
>
> ProcCmdLine: root=UUID=19f3bdd6-1b33-48e0-8081-d00e178d9f7d ro splash vga=792
> ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
> RelatedPackageVersions:
>  linux-backports-modules-2.6.31-8-generic N/A
>  linux-firmware 1.16
> RfKill:
>  0: p...

[tgui (eric-c-morgan)]

This constant reassignment is fun to watch. If I had the time I'd dive into
the code. Good luck to whomever finally takes this task on... or marks it as
completed.

On Sun, Feb 14, 2010 at 1:26 PM, Sense Hofstede <email address hidden> wrote:

> ** Changed in: linux (Ubuntu)
> Assignee: theangel777 (theangel12) => (unassigned)
>
> --
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> https://bugs.launchpad.net/bugs/422536
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in KDE frontend for sudo: Invalid
> Status in The Linux Kernel: Invalid
> Status in “kerneloops” package in Ubuntu: Fix Released
> Status in “linux” package in Ubuntu: Fix Released
> Status in “kerneloops” source package in Karmic: Fix Committed
> Status in “linux” source package in Karmic: Fix Released
>
> Bug description:
> The edac_amd64 module attempts to load on many systems. If the system
> doesn't have ECC
> memory, or it is disabled in the BIOS, then the module prints
>
> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
> NOT be loaded.
> Either Enable ECC in the BIOS, or use the 'ecc_enable_override'
> parameter.
> Might be a BIOS bug, if BIOS says ECC is enabled
> Use of the override can cause unknown side effects.
>
> before failing to load. This won't cause issues for most people that see
> the message.
>
> kerneloops picks this up as kernel problem as the "WARNING:" looks a lot
> like what
> you get when using WARN().
>
> There are several aspects to this issue:
>
> * linux
> - something attempts to load the module when perhaps it doesn't need to
> (unclear at this point)
> - the module looks like it is using WARN() when it isn't, and is
> arguably more SHOUTY than
> it needs to be.
> * kerneloops
> - picks up this as WARN() when it isn't.
> - Was accidentally left enabled for the stable release, people
> shouldn't be getting asked to report
> this at this point.
> - Isn't very good at dealing with repeat issues, causing more reports
> to be sent than are needed.
>
> and possibly others as well.
>
> ProblemType: KernelOops
> Annotation: Your system might become unstable now and might need to be
> restarted.
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: yoman82 3464 F.... pulseaudio
> /dev/snd/pcmC0D0p: yoman82 3464 F...m pulseaudio
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'SB'/'HDA ATI SB at 0xf9ff0000 irq 16'
> Mixer name : 'Realtek ALC888'
> Components : 'HDA:10ec0888,18491e01,00100001'
> Controls : 37
> Simple ctrls : 21
> Date: Tue Sep 1 07:48:00 2009
> DistroRelease: Ubuntu 9.10
> Failure: oops
> HibernationDevice: RESUME=UUID=69c64130-cc6f-4a5b-952b-3ba4c893ba48
> MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
> NonfreeKernelModules: nvidia
> Package: linux-image-2.6.31-8-generic 2.6.31-8.28
> PccardctlIdent:
>
> PccardctlStatus:
>
> ProcCmdLine: root=UUID=19f3bdd6-1b33-48e0-8081-d00e178d9f7d ro splash
> vga=792
> ProcVersionSignature: Ubuntu 2.6.31-8.28-ge...

[Mark Capoferri (cmarksimon)]

Thanks to everyone (and my apologies for not being multi-lingual!) I
think someone should formally close this as I was mistaken in posting
it here in the first place. However, if any reader is of this post is
interested in kernel security, feel free to contact me directly. This
error, which I've tried to update and install (64-bit) is being caused
by a rootkit embedded in my BIOS/eeprom with ms fingerprints all over
it. My repositories are configured by an embedded malware kernel
rootkit.

It has prevented me from establishing a successful inet/ethernet
connection for over two years (it infected nine separate motherboards)
and while now able to connect thanks to live Linux distros, still will
not allow non-root-compromised HD install in the case of 32-bit
versions or preventing any 64-bit install by preseeding the
bootstrap/boot config by use of an embedded kernel written with
Busybox.

I believe based on collected evidence, this is an experimental
framework devised by the folks behind the AFTA agreement, and will be
used on people who use illegal copies of software (in my case, one
illegal copy of xp installed at a business.) If you ever wonder what
happens to people who are reported to the ms anonymous piracy center
and aren't worth filing a legal case for, we're used as experimental
fodder for their latest ant-piracy techniques. And this is in full
conjunction with IANA, RIPE, IEEE, and many others who are
participating in this method of evading US Federal Statutes by
contracting the work to offshore divisions or organizations who don't
have a Constitution or Bill of Rights.

My DNS server and connection settings are included in the embedded
kernel and use an Australian DNS address despite the fact that I live
in the suburbs of Philadelphia. Kinda out of the way for a DNS lookup,
dontcha think?

Actually, you should all be worried, since it means George Orwell was
just off by 25 years.

mc
<email address hidden>

On Mon, Feb 15, 2010 at 12:55 AM, tgui <email address hidden> wrote:
> This constant reassignment is fun to watch. If I had the time I'd dive into
> the code. Good luck to whomever finally takes this task on... or marks it as
> completed.
>
> On Sun, Feb 14, 2010 at 1:26 PM, Sense Hofstede <email address hidden> wrote:
>
>> ** Changed in: linux (Ubuntu)
>>     Assignee: theangel777 (theangel12) => (unassigned)
>>
>> --
>> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
>> NOT be loaded.
>> https://bugs.launchpad.net/bugs/422536
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in KDE frontend for sudo: Invalid
>> Status in The Linux Kernel: Invalid
>> Status in “kerneloops” package in Ubuntu: Fix Released
>> Status in “linux” package in Ubuntu: Fix Released
>> Status in “kerneloops” source package in Karmic: Fix Committed
>> Status in “linux” source package in Karmic: Fix Released
>>
>> Bug description:
>> The edac_amd64 module attempts to load on many systems. If the system
>> doesn't have ECC
>> memory, or it is disabled in the BIOS, then the module prints
>>
>> EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will
>> NOT b...

[Giovanni Condello (nanomad)]

This bug is also present in Lucid (same error message, different kernel version)

[Benoit THIBAUD (frombenny)]

Don't know if it's the same problem I had before the new version of kernel. The computer froze when I was writting a "sudo" command in a terminal like "sudo update-grub". Now the xorg restart instead of freezing the computer.

[Dave Morley (davmor2)]

I have set this bug back to confirmed as it now appears to be affecting Lucids kernel.

Iso ubutnu 20100222 desktop 64bit
Kernel linux-image-2.6.32-14-generic

This happen both during the the install and once installed.

Pitti advised to reopen the bug.

[James Westby (james-w)]

Hi Dave,

Please open a new bug report. This bug is too large to be focused on the issue
at hand.

Thanks,

James

[Jim (JR) Harris (jimrh)]

Date: March 2, 2010 - appx 7:05 pm EST.

Installed 9.10 desktop on an AMD X2 64 bit system using the 64 bit distribution.

I am currently running kernel version 2.6.31-19 - with all current updates installed.

This &^%$#@!!!!! bug should be (IMHO) be rated as darn-near a show-stopper severity and "5 alarm fire" for priority.

1. It causes my system to become virtually unusable at times (randomly).
2. There seems to be no workaround available - aside from removing the O/S and installing a different one. (i.e. The only way to fix M$ Vista is to un-install it and replace it with something that works!)

I am using the NVIDIA proprietary drivers (185)

Behavior of this bug as I see it:

1. *Anything* that I do that causes a change or update in the system's configuration causes this issue to appear. (i.e. Update Manager, apt-get, software installation tools, etc.)
2. The presence of this bug can and does provoke other occurrences of the bug.
(i.e. The process of handling and reporting the bug in Apport triggers other instances of the bug - or so it seems)
3. I get 3, 4, or 5 kernel oops's fired off at a time - one clobbering (stepping on) the other as they seem to compete for desktop and browser resources! Because of this I have not been able to capture bug info to append to this.

IMHO, adding or removing software packages is a normal and expected behavior. Receiving and applying updates as they become available is also a normal and expected behavior. Launching, loading, and attempting to USE this BLASTED OPERATING SYSTEM should also be considered a normal and expected behavior. However, in this case, it provokes these problems. Like the one gentleman said, if Microsoft, (or Apple or Sun), had this problem, people would be all over their [donkey] like a dirty diaper castigating them for such a piece of GAGH! O/S they had.

The range of system responses has gone from "ho-hum, another oops" - all the way to a scrambled display, and a system frozen solid as a rock, with just about every variation in between.

/rant ( :-) )

I do appreciate everyone's efforts. It's just frustrating as *#^!! when I'm trying to get a machine with XP, Win7, and Ubuntu to multi-boot properly - and it's *Ubuntu* that's giving me the real grief here.

Any hope for a fix anytime soon?

Thanks!

Jim

[James Westby (james-w)]

On Wed, 03 Mar 2010 00:25:13 -0000, "Jim \(JR\) Harris" <email address hidden> wrote:
> Date: March 2, 2010 - appx 7:05 pm EST.
>
> Installed 9.10 desktop on an AMD X2 64 bit system using the 64 bit
> distribution.
>
> I am currently running kernel version 2.6.31-19 - with all current
> updates installed.
>
> This &^%$#@!!!!! bug should be (IMHO) be rated as darn-near a show-
> stopper severity and "5 alarm fire" for priority.
>
> 1. It causes my system to become virtually unusable at times (randomly).
> 2. There seems to be no workaround available - aside from removing the O/S and installing a different one. (i.e. The only way to fix M$ Vista is to un-install it and replace it with something that works!)
>
> I am using the NVIDIA proprietary drivers (185)
>
> Behavior of this bug as I see it:
>
> 1. *Anything* that I do that causes a change or update in the system's configuration causes this issue to appear. (i.e. Update Manager, apt-get, software installation tools, etc.)
> 2. The presence of this bug can and does provoke other occurrences of the bug.
> (i.e. The process of handling and reporting the bug in Apport triggers other instances of the bug - or so it seems)
> 3. I get 3, 4, or 5 kernel oops's fired off at a time - one clobbering (stepping on) the other as they seem to compete for desktop and browser resources! Because of this I have not been able to capture bug info to append to this.
>
> IMHO, adding or removing software packages is a normal and expected
> behavior. Receiving and applying updates as they become available is
> also a normal and expected behavior. Launching, loading, and attempting
> to USE this BLASTED OPERATING SYSTEM should also be considered a normal
> and expected behavior. However, in this case, it provokes these
> problems. Like the one gentleman said, if Microsoft, (or Apple or Sun),
> had this problem, people would be all over their [donkey] like a dirty
> diaper castigating them for such a piece of GAGH! O/S they had.
>
> The range of system responses has gone from "ho-hum, another oops" - all
> the way to a scrambled display, and a system frozen solid as a rock,
> with just about every variation in between.
>
> /rant ( :-) )
>
> I do appreciate everyone's efforts. It's just frustrating as *#^!! when
> I'm trying to get a machine with XP, Win7, and Ubuntu to multi-boot
> properly - and it's *Ubuntu* that's giving me the real grief here.
>
> Any hope for a fix anytime soon?

Hi,

I appreciate your concern with the issues that you are experiencing,
however, I think you are pointing at the wrong root cause.

This bug is a spurious warning message, that should have no effect on
your system unless you actually have ECC memory and are expecting to
make use of it. It won't make you system unusable.

Yes, there are usability issues with the oops reporting tool, but I
suggest you go ahead an file any oops reports that don't point to this
bug, as they are more likely to be the cause of the issues that you are
experiencing, and so will be much more helpful in trying to determine
what is going on.

Thanks,

James

[Sense Egbert Hofstede (sense)]

On 3 March 2010 01:25, Jim (JR) Harris <email address hidden> wrote:
> Date: March 2, 2010 - appx 7:05 pm EST.
>
> Installed 9.10 desktop on an AMD X2 64 bit system using the 64 bit
> distribution.
>
> I am currently running kernel version 2.6.31-19 - with all current
> updates installed.
>
> This &^%$#@!!!!! bug should be (IMHO) be rated as darn-near a show-
> stopper severity and "5 alarm fire" for priority.
>
> 1.  It causes my system to become virtually unusable at times (randomly).
> 2.  There seems to be no workaround available - aside from removing the O/S and installing a different one. (i.e. The only way to fix M$ Vista is to un-install it and replace it with something that works!)
>
> I am using the NVIDIA proprietary drivers (185)
>
> Behavior of this bug as I see it:
>
> 1.  *Anything* that I do that causes a change or update in the system's configuration causes this issue to appear.  (i.e.  Update Manager, apt-get, software installation tools, etc.)
> 2.  The presence of this bug can and does provoke other occurrences of the bug.
> (i.e.  The process of handling and reporting the bug in Apport triggers other instances of the bug - or so it seems)
> 3.  I get 3, 4, or 5 kernel oops's fired off at a time - one clobbering (stepping on) the other as they seem to compete for desktop and browser resources!  Because of this I have not been able to capture bug info to append to this.
>
> IMHO, adding or removing software packages is a normal and expected
> behavior.  Receiving and applying updates as they become available is
> also a normal and expected behavior.  Launching, loading, and attempting
> to USE this BLASTED OPERATING SYSTEM should also be considered a normal
> and expected behavior.  However, in this case, it provokes these
> problems.  Like the one gentleman said, if Microsoft, (or Apple or Sun),
> had this problem, people would be all over their [donkey] like a dirty
> diaper castigating them for such a piece of GAGH! O/S they had.
>
> The range of system responses has gone from "ho-hum, another oops" - all
> the way to a scrambled display, and a system frozen solid as a rock,
> with just about every variation in between.
>
> /rant  ( :-) )
>
> I do appreciate everyone's efforts.  It's just frustrating as *#^!! when
> I'm trying to get a machine with XP, Win7, and Ubuntu to multi-boot
> properly - and it's *Ubuntu* that's giving me the real grief here.
>
> Any hope for a fix anytime soon?
>
> Thanks!
>
> Jim
>

Please take into consideration that Ubuntu 10.04 Lucid Lynx is
currently an alpha release and will only be released at the very end
of April. Bugs are expected, it is not recommended to use Lucid in
production environments.

[hire900 (sagitario-frb-95)]

The edac_amd64 module attempts to load on many systems. If the system doesn't have ECC
memory, or it is disabled in the BIOS, then the module prints

EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
    Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter.
    Might be a BIOS bug, if BIOS says ECC is enabled
    Use of the override can cause unknown side effects.

[ricyaun (rickyaun)]

If this problem just popped up on you and did not appear upon installation then look to your NETSTAT command in terminal. On my machine this is caused by hackers attempting to cause a problem. The terminal command for this is netstat --inet -an. See if you get something that looks like mine.

ric@ric-desktop:~$ netstat --inet -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp 0 0 192.168.1.100:42908 72.14.204.19:80 ESTABLISHED
tcp 0 0 192.168.1.100:60936 64.233.169.166:443 ESTABLISHED
tcp 0 0 192.168.1.100:37803 91.189.89.222:443 ESTABLISHED
tcp 0 0 192.168.1.100:50939 91.189.89.225:443 ESTABLISHED
tcp 0 0 192.168.1.100:36574 64.233.169.103:443 ESTABLISHED
tcp 0 0 192.168.1.100:38757 64.233.169.138:80 ESTABLISHED
tcp 0 0 192.168.1.100:44665 72.14.204.19:443 ESTABLISHED
tcp 0 0 192.168.1.100:39014 173.194.4.20:80 ESTABLISHED
tcp 0 0 192.168.1.100:44669 72.14.204.19:443 ESTABLISHED
tcp 0 0 192.168.1.100:40278 74.125.115.97:443 ESTABLISHED
tcp 0 0 192.168.1.100:50935 91.189.89.225:443 ESTABLISHED
tcp 0 0 192.168.1.100:37806 91.189.89.222:443 ESTABLISHED
tcp 0 0 192.168.1.100:54105 74.125.113.132:443 ESTABLISHED
tcp 0 0 192.168.1.100:50938 91.189.89.225:443 ESTABLISHED
tcp 0 0 192.168.1.100:44672 72.14.204.19:443 ESTABLISHED
tcp 0 0 192.168.1.100:44673 72.14.204.19:443 ESTABLISHED
tcp 0 0 192.168.1.100:44666 72.14.204.19:443 ESTABLISHED
tcp 0 0 192.168.1.100:55331 64.233.169.103:80 ESTABLISHED
tcp 0 0 192.168.1.100:57620 72.14.204.189:443 ESTABLISHED
tcp 0 0 192.168.1.100:37805 91.189.89.222:443 ESTABLISHED
tcp 0 0 192.168.1.100:36569 64.233.169.103:443 ESTABLISHED
tcp 0 0 192.168.1.100:44667 72.14.204.19:443 ESTABLISHED
udp 0 0 0.0.0.0:5353 0.0.0.0:*
udp 0 0 0.0.0.0:34228 0.0.0.0:*
udp 0 0 0.0.0.0:68 0.0.0.0:*

I am having big hacker issues. The Canonical Addresses are not Canonical trying to help me out. I have much data on this crew. They are on me 24/7 trying to keep me from gathering data on them. Anyone wants to know exactly what is going on can contact me at <email address hidden>. The object of their activities is to cause computer replacement. If your computer is over 2 years old is their guideline.
these guys can ghost a network in nothing flat. Primarily they work Windows OS, but in my case they have learned to do Linux. They walk through Firefox security like it is nothing.
So look to your NETSTAT in terminal before blaming Ubuntu. ...

[Jeremy Foshee (jeremyfoshee)]

changed back to Fix Released.

Raemys, was there some reason for the status change?

Thanks

~JFo

[ricyaun (rickyaun)]

     In reference to #256. I realize that the 1st reaction to a statement like I made is another conspiracy nut, but that isn't true. My OS made the bug report automatically, and Firefox brought me here. I didn't know about this website existed until these things happened. What I said is true.
     Frankly as I read these postings I am reminded of the WUAUENG1.dll problem the XP Pro x64 community had in 2009. I was a contributor to the resolution of this issue. I have a blubbery thank you email from Microsoft to prove it. What was going on was the mentioned file in the system32 folder was being removed when a registry cleaner was installed. This file allows manual updating of Windows. Without it only automatic updating is allowed, which is exactly how their system works. They inject problems into the OSes through the updates. Their main update utility is HP Update, not Microsoft. Once established they generate phony Windows updates, Microsoft updates, and (I have been aware for 3 months now) phony Ubuntu updates.
Their purpose is to cause the sale of new computers since computer hardware is so much more reliable than other consumer goods. If you go to a retail outlet the average computer isn't really much different from the computers on the sales floors 4 years ago. People just don't tend to replace their computers unless they need to. As long as it does the job they are happy.
     Apparently these guys have noted an issue Karmic had in the beginning, and seized upon it. As proof of what I am saying the Bug #422536 which will show on Live CD operation as IO error on boot up, and as a crash report on HDD boot up was removed immediately upon my posting of #256. I no longer have it. This tells me in a big way they are afraid of the Linux community, and well they ought to be. The Linux community is definitely a step up from the Windows community.
     The reason for this is in 2009 I discovered a FAT16 hidden partition on my hard drive with 80 GB of their data. I was unable to open this partition. They were going in and out of my computer like it had a revolving door on it. So much so that the door never stopped spinning. Since I was unable open the data I wiped it thinking they would go away. Instead they came looking for vengeance. If they had gone away I would never have gained the knowledge I have now. Now after 8 months of 24/7 battles I have so much knowledge that they don't dare to let go. Catch 22 for them.
     I need some help finding out how to roll back my hdd, and then opening that partition. If this is done we will win a mighty battle in the freedom of the Internet war.
     I am going to contact the Ubuntu teams, Mozilla, and the FSF. If anyone here can help email me at <email address hidden> or since emails can be blocked call me at 352-468-1857 in Florida in the United States. Any help will be greatly appreciated. Any and all requests for more info will be welcomed.
     I am going to also contact Marc Capoferri reference to #247. Despite the acronyms he undoubtedly has good data to contribute.

Thank you
Ric Yaun <email address hidden> 352-468-1857 Florida, United States

[ricyaun (rickyaun)]

Postscript to #258.
I have just read #252. There is a good example. No fix can be generated for the what until the who is dealt with. No matter what you do. Not only is it affecting Karmic, but is also as I see appearing in Lucid Lynx. A brand new OS not yet in final release. Not only that I am aware of other CMOS/MBR bugs being generated to cause OS problems.

[ricyaun (rickyaun)]

Well guys here I am back again. I have another machine virtually identical to the first. It also displays this bug and a new one also. This is the machine I downloaded my copy of Karmic with. It is configured with CMOS root kit that is not only making this bug report, but also reboots if I try to install Karmic on it. This particular version of the root kit also prevents a particular brand and model of monitor from displaying Ubuntu above a particular resolution only on it. When tried on my other identical computer it works fine. This is confirmed. So if these corporate black hats try to modify my other machine it is already too late to stop a record from being created.
Again the reason they are on me so bad is I have 80GB of their data residing on a hard drive that needs to rolled back to it. I am positive this will open their entire operation up. Expose them to the daylight which is deadly to bloodsuckers like these guys.
They are plainly attempting to destabilize the Linux community. Make it like the Windows group with constant updates and problems.
I have enough exposure to these guys I even have a nickname for one of them. Mr. BBC/Canonical. Pretty bad don't you think when a person's familiarity with people who live in the shadows like they do reaches a point like that.
They have driven my 80 year old mother off of the internet, and also one of my best friends. They have neither the skills or resources to deal with the problem. I have told all of my friends not to call or email for fear of being identified with me. My email and telephone are bugged. Law enforcement has the same attitude as all of the software types I have talked to have. Arrogant, inexperienced in field service, lack hardware knowledge, and won't listen to anything outside of their experience.
It would be nice if anyone becomes interested. In the mean time keep blaming everything on Microsoft.
Sincerely
<email address hidden>

[d beng what the fuck (duncan303)]

totally confused now............ I thought i was gaining access to a fix to allow me to get a 12 year old hp parallel printer to work on amd64 karmic...................... where is the fix, how to I get it . jesus linux doesn't half make me feel dumb, which I am not.

[Alf Gaida (agaida)]

And by the way, I'am running arch with an 2.6.34 and the error appears to. Thank you guys to post so much dmsgs, so i dont do this. I read a mail discussion last week, which should declare the situation. It seems to mee, as these guys wrote so, as it was not a fault and they classified it newly. The known errors should be within the same module, but dont be affected from these messages.

Wait a little bit, i should find this post soon.

[Alf Gaida (agaida)]

https://patchwork.kernel.org/patch/78719/

<quote>
> > I think changing WARNING to a NOTICE in the log output
> would stop the oops parsing code from thinking this an OOPS
> event, when it is not
</quote>

<quote> > How about something like the following? If everyone is ok
> with that
> I'll send it to Linus and stable later since it is trivial
> enough:
>
> dmesg:
>
> EDAC amd64: ECC disabled in the BIOS or no ECC capability,
> module will not load.
> Either enable ECC checking or force module loading by
> setting 'ecc_enable_override'.
> (Note that use of the override may cause unknown side
> effects.)</quote>

And her a quote from the patch:
<quote>
-static const char *ecc_warning =
- "WARNING: ECC is disabled by BIOS. Module will NOT be loaded.\n"
- " Either Enable ECC in the BIOS, or set 'ecc_enable_override'.\n"
- " Also, use of the override can cause unknown side effects.\n";
+static const char *ecc_msg =
+ "ECC disabled in the BIOS or no ECC capability, module will not load.\n"
+ " Either enable ECC checking or force module loading by setting "
+ "'ecc_enable_override'.\n"
+ " (Note that use of the override may cause unknown side effects.)\n";
</quote>

i have the new notice instead of a warning in a 2.6.33 an 34 too ;-) If you had problems with your kernel, these notice does nothing. For me i figured out a timing problem, solved by nolapic_timer. Running a P965BE on a Gigabyte MA790FXT-UD5P

[Jeremy Foshee (jeremyfoshee)]

Please do not reopen Fix released bugs. If you feel you are affected by a bug, please open a new bug using ubuntu-bug linux.

Thanks!

~JFo

[martyfelker (martyfelker-gmail)]

Essentially the disposition of this is SPAM by now. If one looks back
50 emails or so you'll see that I first reported this bug. I'm sorry I did.

Marty Felker

On 6/29/2010 4:00 AM, Bognár Róbert wrote:
> ** Changed in: linux (Ubuntu)
> Assignee: (unassigned) => Bognár Róbert (haloszovo)
>
>

[Roy Snabilié (okkietje)]

This error will apaer on the background and will manifest with asign in the upper panel