rtc_cmos error reported in /var/log/dmesg

Bug #983292 reported by Franz Nisswandt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

We have been building EC2 AMIs based upon official cononical AMIs for 10.04LTS, 11.10, and 12.04 beta.
Beginning with 11.10 and continuing with 12.04 beta canonical AMIs, we are seeing the following messages in /var/log/dmesg

rtc_cmos: probe of rtc_cmos failed with error -38

Our cluster initialization code relies on clean startup logs (to ascertain whether or not nodes properly initialized/etc.)
This reported error requires us to put custom "ignore error" code in our cluster initialization in order to bring up our EC2 clusters.

Can the underlying issue generating this message be fixed in 11.10 and 12.04?

Thanks
---
AcpiTables:

AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDmesg: [13429635.221470] eth0: no IPv6 routers present
DistroRelease: Ubuntu 12.04
Ec2AMI: ami-7eec604e
Ec2AMIManifest: hpccsystems-amis-us-west-2/hpccsystems-community-03.6.2-4rcprecise_amd64-20120403-1438.manifest.xml
Ec2AvailabilityZone: us-west-2b
Ec2InstanceType: m1.large
Ec2Kernel: aki-98e26fa8
Ec2Ramdisk: unavailable
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0
ProcModules:
 acpiphp 24231 0 - Live 0x0000000000000000
 isofs 40257 0 - Live 0x0000000000000000
ProcVersionSignature: User Name 3.2.0-21.34-virtual 3.2.13
RfKill: Error: [Errno 2] No such file or directory
Tags: precise ec2-images
Uname: Linux 3.2.0-21-virtual x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip floppy netdev plugdev video

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 983292

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Franz Nisswandt (franz-nisswandt) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected ec2-images precise
description: updated
Revision history for this message
Franz Nisswandt (franz-nisswandt) wrote : BootDmesg.txt

apport information

Revision history for this message
Franz Nisswandt (franz-nisswandt) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Franz Nisswandt (franz-nisswandt) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Franz Nisswandt (franz-nisswandt) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Franz Nisswandt (franz-nisswandt) wrote : UdevDb.txt

apport information

Revision history for this message
Franz Nisswandt (franz-nisswandt) wrote : UdevLog.txt

apport information

Revision history for this message
Franz Nisswandt (franz-nisswandt) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: bot-stop-nagging kernel-da-key
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.