Comment 253 for bug 422536

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