registry team mailing list archive

[Alf Gaida <info@xxxxxxxx>]

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

-- 
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 member of Registry
Administrators, which is the registrant for NULL Project.