EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crash report icon
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'ICH'/'Intel ICH with ALC655 at irq 23'
Mixer name : 'Realtek ALC655 rev 0'
Components : 'AC97a:414c4760'
Controls : 41
Simple ctrls : 26
CurrentDmesg:
[ 37.114383] usplash:399 freeing invalid memtype ffffffffd000000
[ 42.730028] eth0: no IPv6 routers present
[ 119.950019] Clocksource tsc unstable (delta = -237128716 ns)
[ 143.331339] EXT3-fs error (device sdc2): ext3_check_
[ 143.331934] EXT3-fs: group descriptors corrupted!
Date: Sat Oct 17 15:17:48 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
Lsusb:
Bus 002 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0840:00a9 Argosy Research, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: root=UUID=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.23
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
Uname: Linux 2.6.31-14-generic x86_64
WpaSupplicantLog:
dmi.bios.date: 11/02/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: C51MCP51
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixT
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 422536, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.