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

[benbloom]

 "amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded." occasionally brings up the apport crash icon.

"Clocksource tsc unstable" ALWAYS appears in dmesg at around at around 81.5 in dmesg

ata3.00: qc timeout repeats every 4-12 typically looks like this:
[ 343.370259] ata3.00: qc timeout (cmd 0xa0)
[** only appears once **] ata3.00: limiting speed to UDMA/66:PIO4
[ 343.370292] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 343.370301] ata3.00: irq_stat 0x40000001
[ 343.370326] ata3.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 343.370329] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 343.370332] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
[ 343.370341] ata3.00: status: { DRDY ERR }
[ 343.370353] ata3: hard resetting link
[ 343.900060] ata3: softreset failed (device not ready)
[ 343.900073] ata3: applying SB600 PMP SRST workaround and retrying
[ 344.080101] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 344.094989] ata3.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 344.110934] ata3.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 344.110946] ata3.00: configured for UDMA/100
[ 344.112994] ata3: EH complete

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: benbloom 1823 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xf0500000 irq 16'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,107b0184,00100101'
   Controls : 17
   Simple ctrls : 11
Date: Tue Feb 9 10:48:34 2010
DistroRelease: Ubuntu 9.10
Failure: oops
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 5515
NonfreeKernelModules: wl
Package: linux-image-2.6.31-19-generic 2.6.31-19.56
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-19-generic root=UUID=10022602-092d-4a49-b13d-34b2d2d7ed5f ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-19-generic N/A
 linux-firmware 1.24
RfKill:

SourcePackage: linux
Tags: kernel-oops
Title: amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
Uname: Linux 2.6.31-19-generic x86_64
dmi.bios.date: 12/03/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.00
dmi.board.name: Nile
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV1.00:bd12/03/2008:svnAcer:pnAspire5515:pvrV1.00:rvnAcer:rnNile:rvrN/A:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5515
dmi.product.version: V1.00
dmi.sys.vendor: Acer

[Jeremy Foshee (jeremyfoshee)]

benbloom,
       I realize this is an obvious question, but is ECC enabled in the BIOS?

Thanks,

-Jeremy

[benbloom (benbloom)]

I have to assume ECC is enabled in BIOS. I was unable to find any switch or info on it. I only receive this error occasionally. I did just find another person who is having the identical problem with "qc timeout" on his acer Aspire 5515. If you think I'm conflating these two issues let me know and I will create a unique bug report

[benbloom (benbloom)]

I should clarify-- when i say i receive this error occasionally, I mean on occasional boots. once the system is running without the error, it does not present later

[Leann Ogasawara (leannogasawara)]

This actually looks to be a duplicate of bug 422536 so I am marking it as such. Please continue to track this issue at that report. Thanks.