Real Time Clock Driver V1 12ac
CONFIG_RTC_CLASS, CONFIG_RTC_LIB and CONFIG_RTC_DRV_CMOS. There might Real Time Clock Driver v1.12ac rtc_cmos : rtc core: registered rtc_cmos.
Toggle useless messages
View this report as an mbox folder, status mbox, maintainer mbox
Report forwarded to debian-bugs-dist lists.debian.org, Debian kernel team :
Bug 277298; Package kernel-image-2.6.7-1-686-smp.
Full text and rfc822 format available.
Acknowledgement sent to W. Borgert :
New Bug report received and forwarded. Copy sent to Debian kernel team.
Message 5 received at submit bugs.debian.org full text, mbox, reply :
Package: kernel-image-2.6.7-1-686-smp
Version: 2.6.7-2
Severity: important
On a Dell server, the 2.6.7 kernel kernel-image-2.6.7-1-686-smp hangs
during boot at the real time clock driver loading phase. It seems, this
problem is specific to the Debian package - self-compiled kernels or
Knoppix kernels seem to work fine.
aceroni writes in
postid 1188223 post1188223
I have problem on a Dell Precision 670.
I have installed the kernel 2.6.8 using the debian Sarge net installation.
The boot hangs after loading the driver for the Real Time Clock.
The hardware configuration is a dual P4 3Ghz with a Intel ICH5 controller.
I have a SATA hard drive. Everything works fine with the 2.4.25 kernel.
ZacBowling writes in
after its first reboot, it would always hang on the Real Time Clock
Driver. I figured it a bug in the 2.6 kernel so I rolled back to woody
and I would just compile my own kernel and then upgrade.
..
After booting up, I recompiled my kernel with new features and stuff and
applied the debian patches. Never had an issues. To this day, I still
cannot get any Debian binary kernel images to load correctly, even the
new releases.
Information forwarded to debian-bugs-dist lists.debian.org, Debian kernel team :
Extra info received and forwarded to list. Copy sent to Debian kernel team.
Message 10 received at 277298 bugs.debian.org full text, mbox, reply :
Similar discussion in this thread:
22046
Note: The kernel seems to boot fine with acpi off, which is not
really nice for a Dual-XEON hyper-threading machine.
Acknowledgement sent to Horms :
Message 15 received at 277298 bugs.debian.org full text, mbox, reply :
On Tue, Oct 19, 2004 at :58PM 0200, W. Borgert wrote:
Package: kernel-image-2.6.7-1-686-smp
Version: 2.6.7-2
Severity: important
On a Dell server, the 2.6.7 kernel kernel-image-2.6.7-1-686-smp hangs
during boot at the real time clock driver loading phase. It seems, this
problem is specific to the Debian package - self-compiled kernels or
Knoppix kernels seem to work fine.
I have installed the kernel 2.6.8 using the debian Sarge net installation.
The boot hangs after loading the driver for the Real Time Clock.
The hardware configuration is a dual P4 3Ghz with a Intel ICH5 controller.
I have a SATA hard drive. Everything works fine with the 2.4.25 kernel.
Driver. I figured it a bug in the 2.6 kernel so I rolled back to woody
and I would just compile my own kernel and then upgrade.
. .
After booting up, I recompiled my kernel with new features and stuff and
applied the debian patches. Never had an issues. To this day, I still
cannot get any Debian binary kernel images to load correctly, even the
new releases.
That does seem to be a bit of a problem.
I had a look around and couldn t see any fix at hand.
As I don t have any hardware that exhibits this behaviour
it is a little hard to reproudce.
Do you have any indication of weather the problem occurs when
initiating the real-time clock driver, or immediately afterwards.
Did the kernel that you built by hand include this driver.
--
Horms
Message 20 received at 277298 bugs.debian.org full text, mbox, reply :
Quoting Horms :
Do you have any indication of weather the problem occurs when
initiating the real-time clock driver, or immediately afterwards.
I m relatively sure, that it is the RTC. Is there an easy
way to disable the RTC only. Maybe by setting something at
the grub command line or by creating a new initrd.
Did the kernel that you built by hand include this driver.
I didn t try a self-made kernel, ZacBowling did.
I asked her/him to send her/his config to this bug report.
Btw.: Kernel boots fine with acpi off, but does not with
acpi ht.
Acknowledgement sent to Kari Asikainen :
Message 25 received at 277298 bugs.debian.org full text, mbox, reply :
I can confirm that this bug affects the Dell PowerEdge 1850 also, tried
kernel-image-2.6.8-9-em64t-4-smp, kernel-image-2.6.8-1-686-smp and
kernel-image-2.6-386. All work fine with acpi off and hang on the RTC
otherwise.
I tried to build a custom 2.6.9 but had similiar results with the first
try, but I can try different configurations with the 1850 if it helps.
-Kari A.
Message 30 received at 277298 bugs.debian.org full text, mbox, reply :
On Tue, Oct 26, 2004 at :30PM 0300, Kari Asikainen wrote:
I can confirm that this bug affects the Dell PowerEdge 1850 also, tried
kernel-image-2.6.8-9-em64t-4-smp, kernel-image-2.6.8-1-686-smp and
kernel-image-2.6-386. All work fine with acpi off and hang on the RTC
otherwise.
I tried to build a custom 2.6.9 but had similiar results with the first
try, but I can try different configurations with the 1850 if it helps.
Thanks for the additional information.
I actually suspect it is an ACPI problem not a RTC problem.
Acknowledgement sent to Zac Bowling :
Message 35 received at 277298 bugs.debian.org full text, mbox, reply :
I just noticed the comment on my page:
The RTC driver wasn t the issue because I compiled full support for RTC
into my kernel and it works great.
I did a lot of investigation and I found that most Dell machines have a
slightly different setup chipset in their RTC setup on the motherboard
then the OEM releases to everyone else that the Dell chip is based on.
I can get pictures of it later. They said its because they are doing
something special I don t remember what the Dell Linux team said and at
the time didn t understand what it was exactly but that makes the
machine work better then most standard boards. From memory, I recall him
saying its suppost to be 100 compatable with all the documented
archatecture. They also said because of that, if you call it in some
unexpected special way or order, it can cause some unpredicticted
problems. They said they see it in very rare cases in the 2.6 kernels
and recommended upgrading my kernel to the latest version from
kernel.org going back to how they submit code back to the kernel team
all the time or using their custom one for RedHat.
I can t seem to reproduce the issue with the kernels I compile. I don t
program at that low of a level yet. I ve tired just about
everything. I ve gotten it to crash for other reasons, but I can t
reproduce that error even with that exact version of the 2.6 kernel with
all the kernel patches. I m going to the office this week, but I will
send in my. config when I can get on that machine. You can figure out
exactly what I did on my site:
Another place to look is here:
I busy right not trying to bring 8 woody machines up at my colo to being
able to run Mono, PHP5, and Horde by backporting packages and
dependencies and installing new packages without breaking or taking down
any applications currently running for our customers, but after I m done
I can focus a bit more time on this issue.
I m sorry I couldn t help anymore then that, but I hope that helps you
get on the right direction.
Thanks.
Zac Bowling
Tags added: patch
Request was from Horms
to control bugs.debian.org.
Acknowledgement sent to Brecht Samyn :
Message 42 received at 277298 bugs.debian.org full text, mbox, reply :
I installed sarge kernel 2.6.8-1-686-smp to my PE 2850 and have the
same problem:
kernel stops after saying Real Time Clock Driver v1.12.
When I press ctrl-c, the booting continues until the hwclock.sh
scripts runs, then it stops again. After another ctrl-c, the boot is
complete.
The same behaviour when halting: the hwclock.sh stop hangs and now
ctrl-c doesn t work anymore ;- .
I can t run hwclock too:
hwclock -r
hangs also while configuring the timezone during install.
brecht
Message 47 received at 277298 bugs.debian.org full text, mbox, reply :
On Thu, Nov 04, 2004 at :37PM 0100, Brecht Samyn wrote:
I installed sarge kernel 2.6.8-1-686-smp to my PE 2850 and have the
same problem:
scripts runs, then it stops again. After another ctrl-c, the boot is
complete.
The same behaviour when halting: the hwclock.sh stop hangs and now
ctrl-c doesn t work anymore ;- .
I can t run hwclock too:
hangs also while configuring the timezone during install.
Can you please take a moment to test the patch logged against bug 270426
which I believe is related.
270426
Message 52 received at 277298 bugs.debian.org full text, mbox, reply :
Horms wrote:
On Thu, Nov 04, 2004 at :37PM 0100, Brecht Samyn wrote:
Can you please take a moment to test the patch logged against bug 270426
which I believe is related.
I was never able to reproduce the error when I compiled the kernel
myself. Only the binary version has this issue it seems like. I ve tried
nearly 100 different variations in the way I compiled various versions
of the kernel. different configuration options, with and without Debian
patches, with the Debian source package or the kernel.org package,
etc While I was able to get it to fail for other common things
though no USB HID support, no support for SATA, etc but I could
never get that error.
I don t have direct access to my machine right now, and I won t until
monday. Also my hard drive got totally fragged from someone in my
company who was learning the basic linux tools and ran fsck from gnome
trying to figure out what it was over a week ago, so I have to restore
from my backups. Shouldn t take to long since I backup to a machine
with a gigabit link and I m using all 10k rpm SATA drives Just going
to a bit of fun getting it all done.
Message 57 received at 277298 bugs.debian.org full text, mbox, reply :
No luck with kernel-source-2.6.8 and this patch: I get exactly the same
result.
I also tried the 2.6.9-1-686-smp kernel from sid, but I get the same error.
Message 62 received at 277298 bugs.debian.org full text, mbox, reply :
Quoting Brecht Samyn :
No luck with kernel-source-2.6.8 and this patch: I get exactly the same
result.
I also tried the 2.6.9-1-686-smp kernel from sid, but I get the same error.
Does it work with acpi off for you. which disables HT, unfortunately
My server is now in production, so I cannot easily test new kernels on
it, as I have to coordinate with my admins.
Message 67 received at 277298 bugs.debian.org full text, mbox, reply :
W. Borgert wrote:
Quoting Brecht Samyn :
Does it work with acpi off for you. which disables HT, unfortunately
Yes, it does.
Acknowledgement sent to Faheem Mitha :
Message 72 received at 277298 bugs.debian.org full text, mbox, reply :
I m get the behaviour described when trying to install Debian on a Dell
machine with the pre-rc2 Debian Installer. At boot it hangs at the message
Real Time Clock Driver v1.1.2
and Ctrl-C does not seem to shift it. This machine is a Dell Optiplex
which I am installing for a friend.
Does anyone want more information about this.
I ll try with the acpi off option, which I presume is a option I pass to
the kernel at boot.
Faheem.
Message 77 received at 277298 bugs.debian.org full text, mbox, reply :
FYI
When I use a vanilla kernel 2.6.9 with the. config file of Debian, I
still have the same problem.
Same thing when I made a kernel starting from debian. config file from
debian 2.6.9-1 kernel, and compiled the scsi driver, ext2, raid1 in the
kernel so I don t need an initrd.
Message 82 received at 277298 bugs.debian.org full text, mbox, reply :
On Fri, Nov 19, 2004 at :02AM -0500, Faheem Mitha wrote:
I m get the behaviour described when trying to install Debian on a Dell
machine with the pre-rc2 Debian Installer. At boot it hangs at the message
Real Time Clock Driver v1.1.2
and Ctrl-C does not seem to shift it. This machine is a Dell Optiplex
which I am installing for a friend.
Does anyone want more information about this.
I ll try with the acpi off option, which I presume is a option I pass to
the kernel at boot.
As I think is mentioned in the Bug s log,
the problem is reportedly fixed upstream but
I have not had any luck isolating the fix and
thus patching the Debian Kernel. Help isolating
the fix would be greatly appreciated.
Bug 277298; Package kernel-source-2.6.8.
Message 91 received at 277298 bugs.debian.org full text, mbox, reply :
Message part 1 text/plain, inline
I just installed it too on my machine and got it again. Maybe its
because we both have chipsets based on AMD64/EM64T to run both 64 bit
applications and 32 bit applications at the same time but it works with
the AMD64 kernel and the new EM64T kernels in sid. Very weird stuff.
Brecht Samyn wrote:
FYI
When I use a vanilla kernel 2.6.9 with the. config file of Debian, I
still have the same problem.
Same thing when I made a kernel starting from debian. config file
from debian 2.6.9-1 kernel, and compiled the scsi driver, ext2, raid1
in the kernel so I don t need an initrd.
brecht
zac.vcf text/x-vcard, attachment
Acknowledgement sent to slchen borcim.wustl.edu Chen, Swaine :
Message 96 received at 277298 bugs.debian.org full text, mbox, reply :
I had the same problem with stock kernels hanging on bootup at the Real
Time Clock driver step.
I had installed Debian Sarge using rc1 of the debian-installer. Machine
is a Dell Dimension 4700 with a 3.0GHz HT P4. Installation went ok until
rebooting for the first time into the newly installed Debian system.
Hitting Control-C to skip the RTC driver and again to skip Setting the
Hardware clock to System clock or whatever would allow booting but then
on the initial base-setup the system would hang and no longer accept any
keyboard input.
Using the acpi off option would get me past the RTC and Setting the
Hardware clock steps but then I got some IRQ 193 error, which said No
one cares.
Finally found this web site:
This is just a workaround but it now allows me to boot Debian stock
kernels with no problem. So far I ve tried 2.6.8-1-686 and
2.6.8-1-686-smp. All files listed below were modified by adding a
--directisa option to the hwclock command. The files and line numbers
modified were:
/etc/init.d/hwclock.sh
lines 72, 104, 119
/etc/init.d/hwclockfirst.sh
lines 62, 75, 77, 80, 82
/usr/sbin/tzsetup
line 148
The /usr/sbin/tzsetup was what was causing the base-config to hang.
Package versions installed for me now:
ii util-linux 2.12-10 Miscellaneous system utilities
ii base-config 2.53.4 Debian base system configurator
ii kernel-image-2 2.6.8-10 Linux kernel image for version 2.6.8 on
PPro
uname -a
Linux sh-slchen 2.6.8-1-686-smp 1 SMP Thu Nov 25 :00 UTC 2004 i686
Hope that helps. I m not sure if there is any other relevant information
that is needed, if so please let me know.
Swaine Chen
slchen users sourceforge net
Message 101 received at 277298 bugs.debian.org full text, mbox, reply :
Thanks a bunch Swaine. Thats the first thing I heard that even gives an
idea of what is happening and it seems to work for me.
Thanks a bunch.
zac ocs-tx.com
Online Computer Solutions
972 889-1475
Toll free: 1-87-PROVIDER
Acknowledgement sent to Javier Fernández-Sanguino Peña :
Message 106 received at 277298 bugs.debian.org full text, mbox, reply :
I have recently helped out an installation of a Dell personal workstation
I believe it s an Optiplex desktop and have been bitten by the same
issue kernel will freeze when loading with a message related to the RTC
driver
After changing /etc/init.d/hwclock, first. sh and /usr/sbin/tzsetup so that
all /sbin/hwclock calls used --directisa the bug would go away. This seems
to be an issue in the 2.6 kernels, however the installer used the 2.6.8
kernel image, I later installed the 2.6.9 but did not try wether it would
break with the hwclock calls
There seems to be a number of bugs open related to hwclock in util-linux
related to this, even though it s a kernel issue, maybe hwclock could work
around it See 186973, 22478, 127975, 22478
Regards
Javier
signature.asc application/pgp-signature, inline
Acknowledgement sent to stappers stappers.nl Geert Stappers :
Message 111 received at 277298 bugs.debian.org full text, mbox, reply :
On Thu, Dec 16, 2004 at :37AM 0100, David Schmitt wrote:
Package: installation-reports
INSTALL REPORT
Machine: Dell Precision 370
hwclock: can be solved by generous applicance of C and killall -9
hwclock.
You encountered bugreport 277298 1
Cheers
Geert Stappers
1 277298
Acknowledgement sent to David Schmitt :
Message 116 received at 277298 bugs.debian.org full text, mbox, reply :
On Fri, Dec 17, 2004 at :14PM 0100, Geert Stappers wrote:
On Thu, Dec 16, 2004 at :37AM 0100, David Schmitt wrote:
You encountered bugreport 277298 1
Probably. Interestingly, though, after upgrading to unstable and rolling
my own kernel from 2.6.8 debianized sources, hwclock now timeouts the
select call. This of course is not optimal, but it allows the boot
without being at the console.
Regards, David
Customer: My palmtop won t turn on.
Tech Support: Did the battery run out, maybe.
Customer: No, it doesn t use batteries. It s Windows powered.
--
Message 121 received at 277298 bugs.debian.org full text, mbox, reply :
Hello,
In this bugreport there is the hint to modify the hwclock.sh files.
But that is a change at several places. I m not fond of that.
However the addition of --directisa is indeed where it seems to hurt.
kernel, hwclock and hardware mismatch
I have this untested workaround in mind:
cd /sbin
. /hwclock --version
hwclock from util-linux-2.12
mv hwclock hwclock-2.12
cat hwclock HERE
. /bin/bash
/sbin/hwclock-2.12 --directisa
HERE
chmod x hwclock
it is a wrapper for the hwclock binary which appends directisa
That is is untested is because I have currently no access
to this Dell who is affect by this bug.
Acknowledgement sent to Erik van Konijnenburg :
Message 126 received at 277298 bugs.debian.org full text, mbox, reply :
Tested on Dell GX280, ICH6 instead of ICH5; your workaround seems to work:
framboos: hwclock --show
Tue 21 Dec 2004 :02 AM CET -0.672601 seconds
framboos: hwclock-2.12 --show
select to /dev/rtc to wait for clock tick timed out
framboos:
Notes:
- util-linux-2.12h no longer hangs on broken rtc but times out.
That test was done with a business card CD when debian installer rc2 was
two days old; see 282861
so there s a decent chance a non-hanging hwclock on the full ISO.
- hwclock 8 states --directisa has no effect except
on i386 and alpha, so risk for other architectures from your workaround seems limited.
- As noted by debacle in 277298
selfcompiled kernels seem to work fine. I tested this only with 2.6.10-rc2,
with make-kpkg, but without debian patches.
On Mon, Dec 20, 2004 at :05PM 0100, Geert Stappers wrote:
Hello,
In this bugreport there is the hint to modify the hwclock.sh files.
But that is a change at several places. I m not fond of that.
However the addition of --directisa is indeed where it seems to hurt.
I have this untested workaround in mind:
hwclock from util-linux-2.12
. /bin/bash
/sbin/hwclock-2.12 --directisa
HERE
it is a wrapper for the hwclock binary which appends directisa
That is is untested is because I have currently no access
to this Dell who is affect by this bug.
Cheers
Geert Stappers
Message 131 received at 277298 bugs.debian.org full text, mbox, reply :
On Tue, Dec 21, 2004 at :04AM 0100, Erik van Konijnenburg wrote:
Tested on Dell GX280, ICH6 instead of ICH5; your workaround seems to work:
Okay, that is the easy part :-
Does the workaround allow reboot without apci off
and without pressing Control-C.
Message 136 received at 277298 bugs.debian.org full text, mbox, reply :
On Tue, Dec 21, 2004 at :19AM 0100, Geert Stappers wrote:
On Tue, Dec 21, 2004 at :04AM 0100, Erik van Konijnenburg wrote:
Okay, that is the easy part :-
Does the workaround allow reboot without apci off
and without pressing Control-C.
That worked already, util-linux-2.12h has working timeout on rtc
failures. In d-i rc2 the hang is gone, so the only motivation
for the workaround would be to create a working hwclock.
Just tested reboot: as expected the timeout error is gone now.
Regards, Erik
Message 141 received at 277298 bugs.debian.org full text, mbox, reply :
On Tue, Dec 21, 2004 at :55PM 0100, Erik van Konijnenburg wrote:
On Tue, Dec 21, 2004 at :19AM 0100, Geert Stappers wrote:
That worked already, util-linux-2.12h has working timeout on rtc
failures. In d-i rc2 the hang is gone, so the only motivation
for the workaround would be to create a working hwclock.
Just tested reboot: as expected the timeout error is gone now.
Yes, I confirm that workaround works fine. including reboot
The manual page of hwclock says:
--directisa
is meaningful only on an ISA machine or an Alpha which imple-
ments enough of ISA to be, roughly speaking, an ISA machine for
hwclock s purposes. For other machines, it has no effect.
This option tells hwclock to use explicit I/O instructions to
access the Hardware Clock. Without this option, hwclock will
try to use the /dev/rtc device which it assumes to be driven by
the rtc device driver. If it is unable to open the device for
read, it will use the explicit I/O instructions anyway.
The rtc device driver was new in Linux Release 2.
So this bugreport, currently filed against kernel-source,
is IMNSHO not bug a kernel bug.
It is about special hardware that needs special treatment.
And the special treatment is provided by the hwclock programm.
Erik: Dank je wel.
None Dutch: Thank you very much.
Message 146 received at 277298 bugs.debian.org full text, mbox, reply :
On Sat, Jan 01, 2005 at :20AM 0100, Frans Pop wrote:
On Saturday 01 January 2005 , Asirvatham Kripps wrote:
I just bought a Dell poweredge SC-420 system with a 80
mmm, another candidate for
bugreport 277298
GB SATA hard drive. When trying to install Debian
linux, I get a message saying no partitionable media
found.
I called Dell support and they say that Debian linux
doesn t support the hard drive and Red Hat Enterprise
version does. I hope this is not true :-
That s bullshit or, if you prefer, untrue.
The question is not does Debian support it, but does the kernel that
Debian currently uses support it.
Try booting with linux26.
That will work, but read on.
However, be aware that SATA in some respects is still under development.
We see quite a few installation reports with problems on SATA hardware.
Changing BIOS settings or cable connections sometimes helps.
IIRC the Dell SC420 has no such option in it is BIOS but it is not needed,
the standard Debian 2.6 Kernel has ata_piix support
Things are sure to improve with time maybe even using patches from Red
Hat that trickle back into the kernel sources.
Asirvatham and others don t need to wait for ata_piix support
in the 2.4 kernel, booting Debian-Installer with linux26 will do the
After the base install, Dell SC420 users will encounter bug 277298 1
Meanwhile is a workaround available. For easy installation I have made
a script, fetch it with
wget stappers/w/277298.sh
then run it with
sh 277298.sh
and please confirm that it worked 2
1 http:/bugs.debian.org/277298
2 or needs some fine tuning
P.S.
Tell your hardware vendor which software you prefer.
Acknowledgement sent to Asirvatham Kripps :
Message 151 received at 277298 bugs.debian.org full text, mbox, reply :
Hi,
The Dell SC-420 is a new machine with nothing on it
and I m trying to install Debian from scratch. And I m
not sure how I can use the 277298.sh patch, since
I m stuck in the installation process.
More info:
1. The problem of No partitionable media were found
was on the latest version of Sarge.
2. I tried linux-30r3 and the installation hangs
after the following message:
hde: wdb wd800jd-75 HKA1, ATA Disk Drive
ide0 at 0x1f0-0x1f7, 0x3f6 on irq 14
3. Although the Dell SC-420 supports RAID, I have only
one primary hard drive in the system.
I m a newbie on installing Debian, so I m assuming
Sarge has linux26.
Thanks,
Kripps/-
--- Geert Stappers wrote:
On Sat, Jan 01, 2005 at :20AM 0100, Frans Pop
wrote:
On Saturday 01 January 2005 , Asirvatham
Kripps wrote:
I just bought a Dell poweredge SC-420 system
with a 80
GB SATA hard drive. When trying to install
linux, I get a message saying no partitionable
media
I called Dell support and they say that Debian
doesn t support the hard drive and Red Hat
Enterprise
The question is not does Debian support it, but
does the kernel that
That will work, but read on.
However, be aware that SATA in some respects is
still under development.
We see quite a few installation reports with
problems on SATA hardware.
Changing BIOS settings or cable connections
sometimes helps.
IIRC the Dell SC420 has no such option in it is BIOS
but it is not needed,
the standard Debian 2.6 Kernel has ata_piix support
Things are sure to improve with time maybe even
using patches from Red
Asirvatham and others don t need to wait for
ata_piix support
in the 2.4 kernel, booting Debian-Installer with
linux26 will do the
After the base install, Dell SC420 users will
encounter bug 277298 1
Meanwhile is a workaround available. For easy
installation I have made
a script, fetch it with
stappers/w/277298.sh
then run it with
and please confirm that it worked 2
P.S.
Tell your hardware vendor which software you prefer.
ATTACHMENT part 2 application/pgp-signature
name signature.asc
Acknowledgement sent to 277298 bugs.debian.org:
Message 156 received at 277298 bugs.debian.org full text, mbox, reply :
On Sat, Jan 01, 2005 at :57PM -0800, Asirvatham Kripps wrote:
Hi,
Thanks much for the help. I was able to complete the
installation with linux26. And of course I encountered
the problem with the installation hanging after Real
Time Clock Driver v1.12. But after I modified the
hwclock as mentioned in the resolution for bug
277298, everything went through perfectly.
Would you please do another install.
And wget 277298 sh 277298 in the ALT-F2 console
before the reboot of the debian-installer.
Thanks a lot,
Kripps/-
Acknowledgement sent to csmall enc.com.au Craig Small :
Message 161 received at 277298 bugs.debian.org full text, mbox, reply :
I successfully installed Debian Sarge on a Dell SC420 using the
linux26 command. You certainly need to turn RAID off though or it just
won t even detect the PATA CDROM.
Anyway I can happily say that the patch supplied by Geert which fixes
hwclock works for me. It works best if you wait until the installer
spits out the CDROM and asks if it can reboot. Flick to the F2 screen
and wget and run Geert s patch.
Thanks all.
- Craig
Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
Eye-Net Consulting MIEE Debian developer
csmall at : enc.com.au ieee.org debian.org
Message 166 received at 277298 bugs.debian.org full text, mbox, reply :
On Tue, Jan 04, 2005 at :55PM 1100, Craig Small wrote:
Anyway I can happily say that the patch supplied by Geert which fixes
hwclock works for me. It works best if you wait until the installer
spits out the CDROM and asks if it can reboot. Flick to the F2 screen
and wget and run Geert s patch.
:-
Thanks all.
TNX for confirming
Message 171 received at 277298 bugs.debian.org full text, mbox, reply :
According to 294938 this problem is fixed in 2.6.10 kernels.
I don t know if it would be possible to identify the fix and backport it
to 2.6.8 I understand this is generally quite hard for ACPI problems.
Cheers,
FJP
Acknowledgement sent to John Zaitseff :
Message 179 received at 277298 bugs.debian.org full text, mbox, reply :
Dear Kernel maintainers,
I have just compiled and am now running the kernel-source-2.6.10-5
package available for Debian unstable on my Dell PowerEdge SC1425
server running Debian Sarge. I can confirm that the Debian version
of 2.6.10 does NOT fix the RTC problem with hwclock.
Yours truly,
John Zaitseff
John Zaitseff , --_ The ZAP Group
Phone: 61 2 9643 7737 / Sydney, Australia
E-mail: J.Zaitseff zap.org.au _,--._
Finger: john zap.org.au v
GnuPG fingerprint: 8FD2 8962 7768 2546 FE07 DE7C 61A8 4486 C9A6 69B0
Message 184 received at 277298 bugs.debian.org full text, mbox, reply :
Dear kernel maintainers,
I wrote:
I have just compiled and am now running the kernel-source-2.6.10-5
package available for Debian unstable on my Dell PowerEdge
SC1425 server running Debian Sarge. I can confirm that the Debian
version of 2.6.10 does NOT fix the RTC problem with hwclock.
I should have mentioned that I am running the 32-bit SMP-capable
version of the kernel, not the 64-bit one ie, I compiled for
CONFIG_MPENTIUM4. I am attaching the config file, just in case
config-2.6.10 text/plain, attachment
Message 189 received at 277298 bugs.debian.org full text, mbox, reply :
This seems relevant.
mail.gnhlug.org/msg08579.html
It makes reference to an eratum from Intel which docouments
that the 8208CA may return eroneous values in some under
some circumstances.
Acknowledgement sent to Michael Stone :
Message 194 received at 277298 bugs.debian.org full text, mbox, reply :
I saw this:
which suggests that the RTC hang issue can be solved by setting
CONFIG_HPET_RTC_IRQ y
I have confirmed that on a dell 1850, which used to hang when hwclock
ran, the above configuration setting allows a normal boot. I suspect,
but have not yet confirmed, that disabling HPET may also prevent hangs.
Mike Stone
Acknowledgement sent to Lee Azzarello :
Message 199 received at 277298 bugs.debian.org full text, mbox, reply :
I had the same rtc lockups with a PowerEdge SC1425 and the Sarge netinst
2.6 kernel. After updating the system, installing
kernel-image-2.6.8-2-686-smp and adding genrtc to /etc/modules there are
no more lockup.
-lee
Notification sent to W. Borgert :
Bug acknowledged by developer.
Message 204 received at 277298-done bugs.debian.org full text, mbox, reply :
On Thu, Apr 21, 2005 at :41PM -0400, Lee Azzarello wrote:
I had the same rtc lockups with a PowerEdge SC1425 and the Sarge netinst
2.6 kernel. After updating the system, installing
kernel-image-2.6.8-2-686-smp and adding genrtc to /etc/modules there are
no more lockup.
Thanks, I am closing this bug.
Please reopen if pain persists.
Message 209 received at 277298 bugs.debian.org full text, mbox, reply :
I am doing some investigations into a problem that has been reported
with RTC on some Dell Machines. It seems to be relate exclusively to
machines that have the 8208CA ICH3 I/O Hub. I have been able to
reproduce this on a Dell 8400, which I have access to today while I am
on holidays. The output of lspci -v -x is attached.
For reference this problem is being tracked at
277298
There are various user-space work arounds for this problem, but I would
like to offer what I have discovered from a brief poke-around in rtc.c.
An strace of hwclock looks a bit like this
open /dev/rtc, O_RDONLY O_LARGEFILE ;
ioctl 3, RTC_UIE_ON, 0 ;
read 3,
the read never returns.
If my reading of the code is correct, what is occuring is that
rtc_read is in its do/while loop, waiting to be rescheduled. This
should occur once an interupt is handled by rtc_interrupt, but I guess
that this is not occuring. Any insights into why this might be happening
would be more than welcome.
The kernel in question is Ubuntu s 2.6.8.1, the rtc.c is identical from
what was in linus tree this morning. The config is also attached.
Please CC me on replies
Thanks
dell.8400.lspci text/plain, attachment
config-2.6.8.1-4-686 text/plain, attachment
Acknowledgement sent to Paul Gortmaker :
Message 214 received at 277298 bugs.debian.org full text, mbox, reply :
At a glance this sounds like the case of having the HPET enabled causes
the RTC IRQ functionality to become crippled or non-functional. The
concept of hwclock using alarm or similar to handle broken and
misconfigured hardware is a sensible idea.
Paul.
--- Horms wrote:
I am doing some investigations into a problem that has been reported
with RTC on some Dell Machines. It seems to be relate exclusively to
machines that have the 8208CA ICH3 I/O Hub. I have been able to
reproduce this on a Dell 8400, which I have access to today while I am
on holidays. The output of lspci -v -x is attached.
For reference this problem is being tracked at
There are various user-space work arounds for this problem, but I would
like to offer what I have discovered from a brief poke-around in rtc.c.
An strace of hwclock looks a bit like this
open /dev/rtc, O_RDONLY O_LARGEFILE ;
ioctl 3, RTC_UIE_ON, 0 ;
read 3,
the read never returns.
If my reading of the code is correct, what is occuring is that
rtc_read is in its do/while loop, waiting to be rescheduled. This
should occur once an interupt is handled by rtc_interrupt, but I guess
that this is not occuring. Any insights into why this might be happening
would be more than welcome.
The kernel in question is Ubuntu s 2.6.8.1, the rtc.c is identical from
what was in linus tree this morning. The config is also attached.
Please CC me on replies
Thanks
__________________________________________________
Do You Yahoo..
Tired of spam. Yahoo. Mail has the best spam protection around
Message 219 received at 277298 bugs.debian.org full text, mbox, reply :
reassign 277298 util-linux
tags 277298 sarge
thanks
The implemention of a user-space timeout for buggy RTC chips,
suggested by Paul Gortmaker, is in the hwclock supplied
by util-linux as of 2.12b-1 upstream as of 2.12a. This
appears to be in unstable but not sarge. Accordingly
I am reassigning this bug to util-linux and marking it sarge.
On Tue, May 03, 2005 at :41PM -0700, Paul Gortmaker wrote:
At a glance this sounds like the case of having the HPET enabled causes
the RTC IRQ functionality to become crippled or non-functional. The
concept of hwclock using alarm or similar to handle broken and
misconfigured hardware is a sensible idea.
Paul.
--- Horms wrote:
__________________________________________________
Do You Yahoo..
Tired of spam. Yahoo. Mail has the best spam protection around
Message 224 received at 277298 bugs.debian.org full text, mbox, reply :
Thanks for the advice. I guess I was holding onto an idea
that it could be fixed in the kernel - but you are right,
the user-space work around is a simple solution to this
buggy hardware.
Bug reopened, originator not changed.
Tags added: sarge
Information forwarded to debian-bugs-dist lists.debian.org, LaMont Jones :
Bug 277298; Package util-linux.
Acknowledgement sent to Ilguiz Latypov :
Extra info received and forwarded to list. Copy sent to LaMont Jones.
Message 235 received at 277298 bugs.debian.org full text, mbox, reply :
The problem with /dev/rtc on Dell machines will cause an erroneous
assumption about the current time in the scripts
/etc/init.d/hwclock. To fix that, add the line
HWCLOCKPARS --directisa
to /etc/default/rcS. Make sure that every invokation of hwclock in
/etc/init.d/hwclock contains HWCLOCKPARS.
Without the above fix, the hwclock scripts will assume that the
system time was updated from the hardware clock and that the
hardware clock is UTC-based. Then the scripts will apply a
timezone shift. This will make the current system time shifted
incorrectly.
Ilguiz Latypov
programmer at DiskStream
Waterloo, Ontario, Canada
Acknowledgement sent to Lokkju :
Message 240 received at 277298 bugs.debian.org full text, mbox, reply :
This exact issue, with rtc timing out an easy test is with rtctest
from rtc.txt, btw, is still occuring in the stock binary Debian Sarge
2.6.16-1-686 image.
The hardware is a Dell PowerEdge 850, so this does seem to be an
almost dell specific issue.
In my case, since I have some. ko drivers that depend on rtc,
disabling it, or loading genrtc, is not an option. I will try
acpi off, or try enabling the HPET RTC option in a custom kernel.
A final solution to this would be wonderful.
Acknowledgement sent to Jerry Quinn :
Message 245 received at 277298 bugs.debian.org full text, mbox, reply :
Package: util-linux
Version: 2.12r-10
Followup-For: Bug 277298
I see the same /dev/rtc timeouts on my Thinkpad T60p. I have stock debian
linux-image-2.6.17-1-686 version 2.6.17-5
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: 990, testing, 500, unstable
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: LANG en_US.UTF-8, LC_CTYPE en_US.UTF-8 charmap UTF-8
Versions of packages util-linux depends on:
ii libc6 2.3.6-15 GNU C Library: Shared libraries
ii libncurses5 5.5-2 Shared libraries for terminal hand
ii libslang2 2.0.6-2 The S-Lang programming library - r
ii libuuid1 1.39-1 universally unique id library
ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip
ii zlib1g 1:1.2.3-13 compression library - runtime
util-linux recommends no packages.
-- no debconf information
Acknowledgement sent to Celejar :
Message 250 received at 277298 bugs.debian.org full text, mbox, reply :
hwclock --show still returns select to /dev/rtc to wait for clock
tick timed out on the above machine with the above Debian binary
kernel. This breaks /etc/init.d/hwclock.sh and causes the time to be
set incorrectly on every boot. Adding --directisa to HWCLOCKPARS in
hwclock.sh fixes the problem, as discussed above.
util-linux is 2.12r-17.
Celejar
Acknowledgement sent to Anders Ellenshøj Andersen :
Message 255 received at 277298 bugs.debian.org full text, mbox, reply :
I am having this problem on
Model: ASUS F3F AP157E
Chipset: Mobile Intel 945GM Express / 667 MHz
Processor: Intel Core 2 Duo 1.83 GHz
Debian unstable, kernel version 2.6.18-4-686
The --directisa switch works for me.
Anders
Acknowledgement sent to Carlos C Soto :
Message 260 received at 277298 bugs.debian.org full text, mbox, reply :
Confirmig that this problem exists on my HP Compaq nx7400 with kernel
2.6.21-2-686
Also the workaround of hwclock wrapper works great for me.
hwclock --version
hwclock from util-linux-2.12r
Carlos C Soto :: SIA Solutions
Tel: 52 722 2078949
Acknowledgement sent to Leonardo :
Message 265 received at 277298 bugs.debian.org full text, mbox, reply :
Model: ACER aspire 5514
Chipset: Mobile Intel 915GM Express
Processor: Intel Centrino 2.0 GHz
Debian unstable, kernel version 2.6.22-1-686
leonardo
Acknowledgement sent to Peter Gruener :
Message 270 received at 277298 bugs.debian.org full text, mbox, reply :
I can confirm this problem for
Model: DELL Latitude D820
Intel 82801G ICH7 based system
with
linux-image-2.6.22-2-686 2.6.22-4
util-linux 2.13-8
--directisa also works for me.
cu
Peter
Request was from LaMont Jones
Wed, 24 Oct 2007 :04 GMT Full text and rfc822 format available.
Acknowledgement sent to Juan Garabana Barro :
Message 277 received at 277298 bugs.debian.org full text, mbox, reply :
Version: 2.13-8
The system hang in hwclock command anyone option.
hwclock.sh script hang the system.
unique option is reset system.
lspci -vv :
.0 RAM memory: nVidia Corporation C51 Host Bridge rev a2
Subsystem: Hewlett-Packard Company Unknown device 30b7
Control: I/O- Mem BusMaster SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap 66MHz UDF- FastB2B ParErr- DEVSEL fast TAbort-
SERR- PERR-
Latency: 0
Capabilities: 44 HyperTransport: Slave or Primary Interface
Command: BaseUnitID 0 UnitCnt 15 MastHost- DefDir- DUL-
Link Control 0: CFlE CST- CFE- LkFail- Init EOC- TXO-
CRCErr 0 IsocEn- LSEn ExtCTL- 64b-
Link Config 0: MLWI 16bit DwFcIn- MLWO 16bit DwFcOut-
LWI 16bit DwFcInEn- LWO 16bit DwFcOutEn-
Link Control 1: CFlE CST- CFE- LkFail- Init EOC- TXO-
Link Config 1: MLWI 16bit DwFcIn- MLWO 16bit DwFcOut-
LWI 8bit DwFcInEn- LWO 8bit DwFcOutEn-
Revision ID: 1.03
Link Frequency 0: 800MHz
Link Error 0: Prot- Ovfl- EOC- CTLTm-
Link Frequency Capability 0: 200MHz 300MHz 400MHz 500MHz
600MHz 800MHz 1.0GHz 1.2GHz- 1.4GHz- 1.6GHz- Vend-
Feature Capability: IsocFC LDTSTOP CRCTM- ECTLT- 64bA-
UIDRD-
Link Frequency 1: 800MHz
Link Error 1: Prot- Ovfl- EOC- CTLTm-
Link Frequency Capability 1: 200MHz 300MHz 400MHz 500MHz
Error Handling: PFlE OFlE PFE- OFE- EOCFE- RFE- CRCFE-
SERRFE- CF- RE- PNFE- ONFE- EOCNFE- RNFE- CRCNFE- SERRNFE-
Prefetchable memory behind bridge Upper: 00-00
Bus Number: 00
Capabilities: e0 HyperTransport: MSI Mapping
.1 RAM memory: nVidia Corporation C51 Memory Controller 0 rev a2
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Status: Cap- 66MHz UDF- FastB2B- ParErr- DEVSEL fast TAbort-
.2 RAM memory: nVidia Corporation C51 Memory Controller 1 rev a2
.3 RAM memory: nVidia Corporation C51 Memory Controller 5 rev a2
Status: Cap- 66MHz UDF- FastB2B ParErr- DEVSEL fast TAbort-
.4 RAM memory: nVidia Corporation C51 Memory Controller 4 rev a2
.5 RAM memory: nVidia Corporation C51 Host Bridge rev a2
Capabilities: 44 00 00fe
Capabilities: fc 00 0000
.6 RAM memory: nVidia Corporation C51 Memory Controller 3 rev a2
.7 RAM memory: nVidia Corporation C51 Memory Controller 2 rev a2
Stepping- SERR- FastB2B-
SERR- PERR-
.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge rev a1
prog-if 00 Normal decode
Control: I/O Mem BusMaster SpecCycle- MemWINV- VGASnoop- ParErr-
Status: Cap 66MHz- UDF- FastB2B- ParErr- DEVSEL fast TAbort-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary 00, secondary 01, subordinate 01, sec-latency 0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: b4000000-b5ffffff
Prefetchable memory behind bridge: 00000000d0000000-00000000d01fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL fast TAbort-
TAbort- MAbort- SERR- PERR-
Capabilities: 40 Subsystem: nVidia Corporation Unknown device 0000
Capabilities: 48 Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent 0mA
PME D0, D1, D2, D3hot, D3cold
Status: D0 PME-Enable- DSel 0 DScale 0 PME-
Capabilities: 50 Message Signalled Interrupts: Mask- 64bit
Queue 0/1 Enable
Address: 00000000fee0300c Data: 4149
Capabilities: 60 HyperTransport: MSI Mapping
Capabilities: 80 Express Root Port Slot IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0,
ExtTag-
Device: Latency L0s 512ns, L1 4us
Device: Errors: Correctable Non-Fatal Fatal Unsupported
Device: RlxdOrd ExtTag- PhantFunc- AuxPwr- NoSnoop
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 2
Link: Latency L0s 512ns, L1 4us
Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x1
Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug-
Surpise-
Slot: Number 0, PowerLimit 0.000000
Slot: Enabled AtnBtn PwrFlt MRL- PresDet- CmdCplt- HPIrq
Slot: AttnInd Off, PwrInd On, Power-
Root: Correctable- Non-Fatal- Fatal- PME-
Capabilities: 100 Virtual Channel
Bus: primary 00, secondary 03, subordinate 03, sec-latency 0
I/O behind bridge: 00005000-00005fff
Memory behind bridge: b6000000-b7ffffff
Prefetchable memory behind bridge: 00000000d0200000-00000000d03fffff
BridgeCtl: Parity- SERR- NoISA VGA- MAbort- Reset- FastB2B-
Address: 00000000fee0300c Data: 4151
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 1
.0 VGA compatible controller: nVidia Corporation C51 PCI Express Bridge
rev a2 prog-if 00 VGA
Interrupt: pin A routed to IRQ 18
Region 0: Memory at b2000000 32-bit, non-prefetchable size 16M
Region 1: Memory at c0000000 64-bit, prefetchable size 256M
Region 3: Memory at b1000000 64-bit, non-prefetchable size 16M
virtual Expansion ROM at 88000000 disabled size 128K
PME D0-,D1-,D2-,D3hot-,D3cold-
Queue 0/0 Enable-
Address: 0000000000000000 Data: 0000
.0 RAM memory: nVidia Corporation MCP51 Host Bridge rev a2
Command: BaseUnitID 9 UnitCnt 15 MastHost- DefDir- DUL-
Link Config 0: MLWI 8bit DwFcIn- MLWO 8bit DwFcOut- LWI 8bit
DwFcInEn- LWO 8bit DwFcOutEn-
Link Control 1: CFlE- CST- CFE- LkFail Init- EOC TXO
CRCErr 0 IsocEn- LSEn- ExtCTL- 64b-
Link Config 1: MLWI 8bit DwFcIn- MLWO 8bit DwFcOut- LWI 8bit
Link Frequency 1: 200MHz
Link Frequency Capability 1: 200MHz- 300MHz- 400MHz- 500MHz-
600MHz- 800MHz- 1.0GHz- 1.2GHz- 1.4GHz- 1.6GHz- Vend-
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge rev a3
Control: I/O Mem BusMaster SpecCycle MemWINV- VGASnoop- ParErr-
Region 0: I/O ports at 1d00 size 128
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus rev a3
Control: I/O Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Interrupt: pin A routed to IRQ 10
Region 4: I/O ports at 3040 size 64
Region 5: I/O ports at 3000 size 64
Capabilities: 44 Power Management version 2
PME D0-,D1-,D2-,D3hot, D3cold
00:0a.3 Co-processor: nVidia Corporation MCP51 PMU rev a3
Latency: 0 750ns min, 250ns max
Interrupt: pin B routed to IRQ 10
Region 0: Memory at b0040000 32-bit, non-prefetchable size 256K
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller rev a3
prog-if 10 OHCI
Interrupt: pin A routed to IRQ 22
Region 0: Memory at b0004000 32-bit, non-prefetchable size 4K
Flags: PMEClk- DSI- D1 D2 AuxCurrent 0mA
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller rev a3
prog-if 20 EHCI
Interrupt: pin B routed to IRQ 22
Region 0: Memory at b0005000 32-bit, non-prefetchable size 256
Capabilities: 44 Debug port
Capabilities: 80 Power Management version 2
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE rev f1 prog-if 8a
Master SecP PriP
Control: I/O Mem- BusMaster SpecCycle- MemWINV- VGASnoop- ParErr-
Region 0: virtual Memory at 000001f0 32-bit, non-prefetchable
disabled size 8
Region 1: virtual Memory at 000003f0 type 3, non-prefetchable
disabled size 1
Region 2: virtual Memory at 00000170 32-bit, non-prefetchable
Region 3: virtual Memory at 00000370 type 3, non-prefetchable
Region 4: I/O ports at 3080 size 16
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller rev
f1 prog-if 85 Master SecO PriO
Interrupt: pin A routed to IRQ 23
Region 0: I/O ports at 30c0 size 8
Region 1: I/O ports at 30b4 size 4
Region 2: I/O ports at 30b8 size 8
Region 3: I/O ports at 30b0 size 4
Region 4: I/O ports at 3090 size 16
Region 5: Memory at b0006000 32-bit, non-prefetchable size 4K
Capabilities: b0 Message Signalled Interrupts: Mask- 64bit
Queue 0/2 Enable-
Capabilities: cc HyperTransport: MSI Mapping
.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge rev a2 prog-if 01
Subtractive decode
Bus: primary 00, secondary 07, subordinate 07, sec-latency 64
Memory behind bridge: b8000000-b80fffff
Secondary status: 66MHz- FastB2B ParErr- DEVSEL medium TAbort-
TAbort- MAbort- SERR- PERR
Capabilities: b8 Subsystem: Gammagraphx, Inc. Unknown device 0000
Capabilities: 8c HyperTransport: MSI Mapping
.1 Audio device: nVidia Corporation MCP51 High Definition Audio rev
a2
Latency: 0 500ns min, 1250ns max
Interrupt: pin B routed to IRQ 21
Region 0: Memory at b0000000 32-bit, non-prefetchable size 16K
Capabilities: 50 Message Signalled Interrupts: Mask 64bit
Masking: 00000000 Pending: 00000000
Capabilities: 6c HyperTransport: MSI Mapping
.0 Bridge: nVidia Corporation MCP51 Ethernet Controller rev a3
Latency: 0 250ns min, 5000ns max
Interrupt: pin A routed to IRQ 20
Region 0: Memory at b0008000 32-bit, non-prefetchable size 4K
Region 1: I/O ports at 30e0 size 8
.0 Host bridge: Advanced Micro Devices AMD K8 Athlon64/Opteron
HyperTransport Technology Configuration
Capabilities: 80 HyperTransport: Host or Secondary Interface
Possibly incomplete decoding
Command: WarmRst DblEnd-
Link Control: CFlE- CST- CFE- LkFail- Init EOC- TXO-
CRCErr 8
Link Config: MLWI 16bit MLWO 16bit LWI 16bit LWO 16bit
Revision ID: 1.02
.1 Host bridge: Advanced Micro Devices AMD K8 Athlon64/Opteron
Address Map
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL fast TAbort-
.2 Host bridge: Advanced Micro Devices AMD K8 Athlon64/Opteron DRAM
Controller
.3 Host bridge: Advanced Micro Devices AMD K8 Athlon64/Opteron
Miscellaneous Control
Capabilities: f0 0f 0010
.0 FireWire IEEE 1394 : Ricoh Co Ltd Unknown device 0832 prog-if 10
Stepping- SERR FastB2B-
Status: Cap 66MHz- UDF- FastB2B- ParErr- DEVSEL medium TAbort-
Latency: 64 500ns min, 1000ns max
Interrupt: pin A routed to IRQ 5
Region 0: Memory at b8000000 32-bit, non-prefetchable size 2K
Capabilities: dc Power Management version 2
Status: D0 PME-Enable- DSel 0 DScale 2 PME
.1 Generic system peripheral 0805 : Ricoh Co Ltd R5C822
SD/SDIO/MMC/MS/MSPro Host Adapter rev 19
Latency: 64
Interrupt: pin B routed to IRQ 7
Region 0: Memory at b8000800 32-bit, non-prefetchable size 256
Status: D0 PME-Enable- DSel 0 DScale 2 PME-
.2 System peripheral: Ricoh Co Ltd Unknown device 0843 rev 01
Interrupt: pin B routed to IRQ 11
Region 0: Memory at b8000c00 32-bit, non-prefetchable size 256
.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter
rev 0a
Control: I/O- Mem BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Region 0: Memory at b8001000 32-bit, non-prefetchable size 256
.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller rev 05
Region 0: Memory at b8001400 32-bit, non-prefetchable size 256
dmidecode:
dmidecode 2.9
SMBIOS 2.4 present.
20 structures occupying 822 bytes.
Table at 0x000F1C80.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Hewlett-Packard
Version: F.3A
Release Date: 07/19/2007
Address: 0xE6A30
Runtime Size: 103888 bytes
ROM Size: 1024 kB
Characteristics:
ISA is supported
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
Print screen service is supported int 5h
8042 keyboard services are supported int 9h
Serial services are supported int 14h
Printer services are supported int 17h
ACPI is supported
USB legacy is supported
AGP is supported
Smart battery is supported
BIOS boot specification is supported
Targeted content distribution is supported
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Hewlett-Packard
Product Name:
Version: Rev 1
Serial Number:
UUID: Not Settable
Wake-up Type: Power Switch
SKU Number:
Family: 103C_5335KV
Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Quanta
Product Name: 30B7
Version: 65.28
Serial Number: None
Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
Type: Notebook
Lock: Not Present
Version: N/A
Asset Tag:
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: Unknown
OEM Information: 0x00000000
Handle 0x0004, DMI type 4, 35 bytes
Processor Information
Socket Designation: Socket S1
Type: Central Processor
Family: Opteron
Manufacturer: AMD
ID: 82 0F 04 00 FF FB 8B 17
Signature: Family 15, Model 72, Stepping 2
Flags:
FPU Floating-point unit on-chip
VME Virtual mode extension
DE Debugging extension
PSE Page size extension
TSC Time stamp counter
MSR Model specific registers
PAE Physical address extension
MCE Machine check exception
CX8 CMPXCHG8 instruction supported
APIC On-chip APIC hardware supported
SEP Fast system call
MTRR Memory type range registers
PGE Page global enable
MCA Machine check architecture
CMOV Conditional move instruction supported
PAT Page attribute table
PSE-36 36-bit page size extension
CLFSH CLFLUSH instruction supported
FXSR Fast floating-point save and restore
SSE Streaming SIMD extensions
SSE2 Streaming SIMD extensions 2
HTT Hyper-threading technology
Version: AMD Turion tm 64 X2 Mobile TL50
Voltage: 1.6 V
External Clock: 200 MHz
Max Speed: 1600 MHz
Current Speed: 1600 MHz
Status: Populated, Enabled
Upgrade: None
L1 Cache Handle: 0x0005
L2 Cache Handle: 0x0006
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Handle 0x0005, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1 Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 64 KB
Maximum Size: 64 KB
Supported SRAM Types:
Burst
Pipeline Burst
Asynchronous
Installed SRAM Type: Asynchronous
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x0006, DMI type 7, 19 bytes
Socket Designation: L2 Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Through
Installed Size: 512 KB
Maximum Size: 512 KB
Synchronous
Installed SRAM Type: Synchronous
System Type: Unified
Handle 0x0007, DMI type 9, 13 bytes
System Slot Information
Designation: PCI Express Slot 1
Type: 64-bit PCI Express
Current Usage: Available
Length: Short
ID: 0
5.0 V is provided
3.3 V is provided
Handle 0x0008, DMI type 9, 13 bytes
Designation: PCI Express Slot 2
PME signal is supported
Hot-plug devices are supported
Handle 0x0009, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Enabled
Description: 64
Handle 0x000A, DMI type 11, 5 bytes
OEM Strings
String 1: HP
String 2: LOC
Handle 0x000B, DMI type 15, 29 bytes
System Event Log
Area Length: 16 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: General-purpose non-volatile data functions
Access Address: 0x0000
Status: Valid, Not Full
Change Token: 0x00000002
Header Format: Type 1
Supported Log Type Descriptors: 3
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: Single-bit ECC memory error
Data Format 2: Multiple-event
Descriptor 3: Multi-bit ECC memory error
Data Format 3: Multiple-event
Handle 0x000C, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 2 GB
Error Information Handle: Not Provided
Number Of Devices: 2
Handle 0x000D, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x000C
Error Information Handle: No Error
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: 1
Locator: DIMM 1
Bank Locator: Bank 0,1
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz 1.5 ns
Manufacturer: F7F7F7B000000000
Serial Number: 0702C114
Part Number: NT1GT64U8HA0BN-3C
Handle 0x000E, DMI type 17, 27 bytes
Locator: DIMM 2
Bank Locator: Bank 2,3
Type Detail: Unknown
Serial Number: 4002C144
Handle 0x000F, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Array Handle: 0x000C
Partition Width: 0
Handle 0x0010, DMI type 20, 19 bytes
Memory Device Mapped Address
Ending Address: 0x0003FFFFFFF
Range Size: 1 GB
Physical Device Handle: 0x000D
Memory Array Mapped Address Handle: 0x000F
Partition Row Position: 2
Interleave Position: 2
Interleaved Data Depth: 2
Handle 0x0011, DMI type 20, 19 bytes
Starting Address: 0x00040000000
Physical Device Handle: 0x000E
Handle 0x0012, DMI type 32, 20 bytes
System Boot Information
Status:
Handle 0x0013, DMI type 127, 4 bytes
End Of Table
Debian Release: lenny/sid
APT policy: 900, testing, 700, unstable
Kernel: Linux 2.6.23.12 SMP w/2 CPU cores
Locale: LANG es_ES euro, LC_CTYPE es_ES euro charmap ISO-8859-15 ignored: LC_ALL set to es_ES euro
ii libc6 2.7-5 GNU C Library: Shared libraries
ii libncurses5 5.6 20071124-1 Shared libraries for terminal hand
ii libselinux1 2.0.15-2 b1 SELinux shared libraries
ii libslang2 2.0.7-3 The S-Lang programming library - r
ii libuuid1 1.40.3-1 universally unique id library
ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip
ii tzdata 2007j-3 time zone and daylight-saving time
ii zlib1g 1:1.2.3.3.dfsg-8 compression library - runtime
Acknowledgement sent to Christopher David Desjardins :
Your message did not contain a Subject field. They are recommended and
useful because the title of a gBug is determined using this field.
Please remember to include a Subject field in your messages in future.
Message 282 received at 277298 bugs.debian.org full text, mbox, reply :
This is also happening on a Lenovo 3000 N100 w/ linux kernel 2.6.22-3-686 and
util-linux version 2.13.1-1. I can also confirm that Geert Stappers
workaround works for me.
Chris
Acknowledgement sent to Guillaume JAOUEN :
Message 287 received at 277298 bugs.debian.org full text, mbox, reply :
Version: 2.13.1-2
I fill this bug repot as I can t find any solution to this bug.
hwclock return this output :
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access
method.
Linux dell-xps 2.6.24-1-amd64 1 SMP Mon Feb 11 :43 UTC 2008 x86_64
dell-xps:/dev dmesg egrep -i clock hpet
ACPI: HPET 7FEDB700, 0038 r1 DELL M07 1 ASL 61
ACPI: HPET id: 0x8086a201 base: 0xfed00000
hpet clockevent registered
TSC calibrated against HPET
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
hpet0: 3 64-bit timers, 14318180 Hz
Time: hpet clocksource has been installed.
Real Time Clock Driver v1.12ac
hpet_resources: 0xfed00000 is busy
Clocksource tsc unstable delta -333964267 ns
Best regards,
Guillaume JAOUEN.
APT prefers unstable
APT policy: 500, unstable
Kernel: Linux 2.6.24-1-amd64 SMP w/2 CPU cores
Locale: LANG fr_FR euro, LC_CTYPE fr_FR euro charmap ISO-8859-15
ii libc6 2.7-9 GNU C Library: Shared libraries
ii libncurses5 5.6 20080203-1 Shared libraries for terminal hand
ii libselinux1 2.0.35-1 SELinux shared libraries
ii libslang2 2.1.3-2 The S-Lang programming library - r
ii libuuid1 1.40.7-1 universally unique id library
ii lsb-base 3.2-4 Linux Standard Base 3.2 init scrip
ii tzdata 2008a-1 time zone and daylight-saving time
ii zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime
Acknowledgement sent to Paul Menzel :
Message 292 received at 277298 bugs.debian.org full text, mbox, reply :
Version: 2.13.1-3
--- Please enter the report below this line. ---
Dear DDs,
I am experiencing this problem, too. I think, I did not have this
problem with linux 2.6.22 installed.
Linux xxx 2.6.24-1-686 1 SMP Thu Mar 27 :04 UTC 2008 i686
lspci
.0 Host bridge: Intel Corporation 82875P/E7210 Memory Controller Hub rev 02
.0 PCI bridge: Intel Corporation 82875P Processor to AGP Controller rev 02
.0 PCI bridge: Intel Corporation 82875P/E7210 Processor to PCI to CSA Bridge rev 02
.0 System peripheral: Intel Corporation 82875P/E7210 Processor to I/O Memory Interface rev 02
00:1d.0 USB Controller: Intel Corporation 82801EB/ER ICH5/ICH5R USB UHCI Controller 1 rev 02
00:1d.1 USB Controller: Intel Corporation 82801EB/ER ICH5/ICH5R USB UHCI Controller 2 rev 02
00:1d.2 USB Controller: Intel Corporation 82801EB/ER ICH5/ICH5R USB UHCI Controller 3 rev 02
00:1d.3 USB Controller: Intel Corporation 82801EB/ER ICH5/ICH5R USB UHCI Controller 4 rev 02
00:1d.7 USB Controller: Intel Corporation 82801EB/ER ICH5/ICH5R USB2 EHCI Controller rev 02
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge rev c2
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER ICH5/ICH5R LPC Interface Bridge rev 02
00:1f.1 IDE interface: Intel Corporation 82801EB/ER ICH5/ICH5R IDE Controller rev 02
00:1f.2 IDE interface: Intel Corporation 82801EB ICH5 SATA Controller rev 02
00:1f.3 SMBus: Intel Corporation 82801EB/ER ICH5/ICH5R SMBus Controller rev 02
.0 VGA compatible controller: nVidia Corporation NV31 GeForce FX 5600 rev a1
.0 Ethernet controller: Intel Corporation 82547EI Gigabit Ethernet Controller
.0 FireWire IEEE 1394 : VIA Technologies, Inc. IEEE 1394 Host Controller rev 80
03:0c.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24/30 CrystalClear SoundFusion Audio Accelerator rev 01
Thanks a lot.
Paul
PS: Since some people say, this bug should be fixed in Linux, maybe this
report should be reassigned.
1 410328 10
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.24-1-686
500 unstable debian.tu-bs.de
--- Package information. ---
Depends Version Installed
- -
lsb-base 3.0-6 3.2-7
tzdata 2006c-2 2008b-1
Acknowledgement sent to Alain Guibert :
Message 297 received at 277298 bugs.debian.org full text, mbox, reply :
Hello Paul,
On Thursday, April 10, 2008 at :45 0200, Paul Menzel wrote:
I am experiencing this problem, too.
It can be a hardware bug, a kernel bug, or something else. What is your
computer exactly. And what is the output of:
hwclock --rtc /dev/rtc0 --debug
Since some people say, this bug should be fixed in Linux, maybe this
report should be reassigned.
The same timeout symptom can hide different problems. Only one of these
problems is a kernel /dev/rtc device driver bug. We can imagine various
possible workarounds, in hwclock install, or in Debian kernel setup.
But the real fix is for the kernel, right.
Alain.
Message 302 received at 277298 bugs.debian.org full text, mbox, reply :
Dear Alain,
thank you for your response.
Am Sonntag, den 13.04.2008, 0200 schrieb Alain Guibert:
It can be a hardware bug, a kernel bug, or something else. What is your
computer exactly.
The motherboard is an ASUS P4C 800-E Deluxe. What other information do
you need.
And what is the output of:
LANG C sudo hwclock --rtc /dev/rtc0 --debug
hwclock from util-linux-ng 2.13.1
hwclock: Open of /dev/rtc0 failed, errno 2: No such file or directory.
Using direct I/O instructions to ISA clock.
Last drift adjustment done at 1208104267 seconds after 1969
Last calibration done at 1208104267 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick
got clock tick
Time read from Hardware Clock: 2008/04/13 :03
Hw clock time : 2008/04/13 :03 1208118663 seconds since 1969
Sun Apr 13 :03 2008 -0.130754 seconds
LANG C sudo hwclock --rtc /dev/rtc --debug
Using /dev interface to clock.
select to /dev/rtc to wait for clock tick timed out
The same timeout symptom can hide different problems. Only one of these
problems is a kernel /dev/rtc device driver bug. We can imagine various
possible workarounds, in hwclock install, or in Debian kernel setup.
But the real fix is for the kernel, right.
Understood.
Acknowledgement sent to Ross Burton :
Message 307 received at 277298 bugs.debian.org full text, mbox, reply :
I m seeing this on a Lenovo ThinkPad X60, adding --directisa fixed it
for me too.
Ross
Ross Burton mail: ross burtonini.com
jabber: ross burtonini.com
www:
PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF
Information forwarded
to debian-bugs-dist lists.debian.org, LaMont Jones :
Sat, 20 Dec 2008 :02 GMT Full text and rfc822 format available.
Acknowledgement sent
to zlinuxman wowway.com:
Message 312 received at 277298 bugs.debian.org full text, mbox, reply :
I have a similar problem on a Dell Optiplex GX280. I have been doing some
extensive research on this problem, and I d like to share what I ve found.
The problem is definitely the HPET High Precision Event Timer.
See for more
information on the HPET.
Check your boot log with dmesg less. If you see a message that starts with
ACPI: HPET
Then your machine has an HPET and you will have this problem. Booting
with the kernel boot parameter
acpi off
causes the HPET to not be recognized, and therefore the RTC module can
grab IRQ 8. But booting with acpi off causes a lot of other devices to
not be recognized and/or configured too. And that s usually not good.
The problem is that both the HPET and the legacy RTC want to use IRQ 8.
And with Etch 2.6.18 kernel and earlier releases, the kernel does not
allow IRQ 8 to be shared between the HPET and the RTC. I haven t tried
Lenny, with it s 2.6.26 kernel, and for reasons I don t want to get into,
I m not going to. But the long term solution is for the kernel to allow
IRQ 8 to be shared between the HPET and the legacy RTC. Of course, the
hardware itself has to allow interrupt sharing too, or there s not much the
kernel can do about it.
If the hardware doesn t allow interrupt sharing, perhaps the kernel people can
write a replacement for the RTC driver that emulates a legacy RTC using the
HPET. But with Etch at least, here are the alternatives that I have found:
1. Configure a custom kernel that has all support for the HPET disabled.
When you re all done, look through the. config file and make sure that all
configuration options containing the character string HPET are commented out.
If not, you missed something. Go back and try again. Unlike the RTC
driver, which can be made a module, support for the HPET is built into the
kernel. This will allow full use of the legacy RTC driver, whether it is
built in to the kernel or whether it is a module. Of course, the HPET
cannot be used at all. This was my solution.
2. In some cases, you may be able to use the genrtc driver rather than the
rtc driver. The genrtc driver emulates interrupts in software. To do this,
add genrtc to /etc/initramfs-tools/modules and run update-initramfs -uv.
Then shutdown and reboot. genrtc cannot emulate all the functions of the
legacy rtc driver.
3. Another option with Etch anyway is using the CONFIG_HPET_RTC_IRQ y
option when you build a custom kernel. This tells the legacy rtc driver
to assume that the HPET has stolen IRQ 8 and to not use interrupts.
This allows the kernel to use the HPET. However, the legacy RTC driver
has reduced function this way.
4. As mentioned earlier, forcing the use of the --directisa option in
hwclock, either through a wrapper or by editing the hwclock.sh script, may be
sufficient.
5. Finally, there s acpi off as a last resort.
Again, the long term solution is interrupt sharing. If this cannot be done,
then perhaps Debian should consider changing their stock kernel to not
include HPET support. Users who need HPET support would then have to
build their own custom kernel and deal with the RTC issue somehow.
Added tag s moreinfo.
Request was from Phillip Susi
to control bugs.debian.org.
Mon, 10 Feb 2014 :04 GMT Full text and rfc822 format available.
Message sent on
to W. Borgert :
Bug 277298.
Mon, 10 Feb 2014 :08 GMT Full text and rfc822 format available.
Message 317 received at 277298-submitter bugs.debian.org full text, mbox, reply :
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
tags 277298 moreinfo
I m not sure why this was reassigned from the kernel. Is this still
an issue today with a modern kernel.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 GNU/Linux
Comment: Using GnuPG with Thunderbird -
iQEcBAEBCgAGBQJS EjbAAoJEI5FoCIzSKrwf2QH/jrkATx9fcoYXfQj9aST9kg0
Oh8CsNYlmSL25VZeO2mnLKf/bGWNzCKygElg brdB49Y/w qa8pVczrTwmuOcwxX
nRGnE9XHWqfZ9dnTiT2Th2YLHZViVuTKzLvXjO4A4cZd3ZuwwL4L1ja5qUc1GNN4
nzsBqDxlA/pC/xyzKecsLOSlQ/jjADX3Vp2UcdvbwVi9AV2AViAwu6GfrzjlZ3tC
JRjeUhdBvDo0EGaDVP8MzHuWWMeRB Ios0N1daTCD050u60Q3R7MTJcxDOm3b3QC
MdvwrdO1s5VPTuJo 3HjDixQ3JT0IoCOtOwbaleuusVfhk23OBMnzq0pTkLugok
HGfX
-----END PGP SIGNATURE-----
Sun, 22 Jun 2014 :05 GMT Full text and rfc822 format available.
to Andreas Henriksson :
Message 322 received at 277298 bugs.debian.org full text, mbox, reply :
Control: tags -1 - moreinfo
On Sun, Feb 09, 2014 at :51PM -0500, Phillip Susi wrote:
I m not sure why this was reassigned from the kernel. Is this still
an issue today with a modern kernel.
This bug report sure has alot of posts in it so I think it s a good
idea to post a summary shining some light on the uncertanty about
why this bug was reassigned.
The reason this was reassigned from the kernel to util-linux
is found in:
https://bugs.debian.org/cgi-bin/bugreport.cgi.bug 277298 219
Basically, people where starting to give up on finding a
solution in the kernel and where discussing a userspace workaround
for broken rtc drivers.
The bug should have been cloned and the clone reassigned
or a brand new bug report opened instead, because the kernel bug
was not solved and who knows if it still is.
At the same time, the bug should probably have been retitled
to something like Please implement workaround/timeout for broken rtc
and the severity lowered to wishlist.
I d argue that a good enough workaround already exists today,
with the possibility of adding the --directisa switch in
/etc/default/hwclock.
I think this strikes a good balance between not hiding
the bug while at the same time allowing a convenient way
to work around the problem for users who don t need to hack
the init script.
If it was up to me, I d close this bug with the above explanation
about /etc/default/hwclock.
Regards,
Andreas Henriksson
Removed tag s moreinfo.
Request was from Andreas Henriksson
to 277298-submit bugs.debian.org.
Reply sent
You have taken responsibility.
Sat, 02 Aug 2014 :05 GMT Full text and rfc822 format available.
Notification sent
Message 329 received at 277298-done bugs.debian.org full text, mbox, reply :
Hello.
I m closing this bug report now, please see my previous summary 0
about this and if you want to work around a broken rtc driver
you can use the --directisa option via /etc/default/hwclock.
0 : https://bugs.debian.org/cgi-bin/bugreport.cgi.bug 277298 322
Sat, 02 Aug 2014 :06 GMT Full text and rfc822 format available.
to Jérôme Bertorelle :
Bug archived.
Request was from Debbugs Internal Request
to internal_control bugs.debian.org.
Sun, 31 Aug 2014 :03 GMT Full text and rfc822 format available.
Send a report that this bug log contains spam.
Debian bug tracking system administrator owner bugs.debian.org.
Last modified:
Thu Jan 7 :55 2016;
Machine Name:
buxtehude
Debian Bug tracking system
Copyright C 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.
VESA VGA frame buffer device Real Time Clock Driver v1.12ac I have no idea, 2007 PM To: xen-users xxxxxxxxxxxxxxxxxxx Subject: Xen.
, boot the kernel with HZ at 1000 but the real Specifically the acpi_pm clock, which manages to keep very good time on.
The system clock doesn t work correctly. From: 6 Real Time Clock Driver v1.12ac 6 Time: You see that the clock is running fine with pit.
Real Time Clock Driver v1.12ac Linux-Kernel Re: Help. Major Memory Installation Issue the HD Audio Driver and Application option. all on my C or F.
Kernel stops after saying Real Time Clock Driver v1.12. Real Time Clock Driver v1.12ac hpet_resources: 0xfed00000 is busy Clocksource tsc unstable.
From: David Madore
Date: Fri Nov 09 2007 - :50 EST
Hi all,
I m extremely confused as to what all the RTC-related config variables
in the kernel mean and what I m supposed to do with them, and I wonder
if someone can help me or point me to some doc beside rtc.txt which
I ve read, of course.
I understand from reading Documentation/rtc.txt that there are two
different RTC driver systems for Linux: an old one, supporting only
one PC-AT-compatible RTC source, which drives /dev/rtc, and a new
one, supporting different sources, which drives /dev/rtc 0123.
But I m not sure which configuration variables enable which, whether
they should be enabled together or whether I should choose between the
twain, and what I should be using on my system anyway.
I sort of gathered I hope not too incorrectly that the genrtc
module is brought by the CONFIG_GEN_RTC configuration choice and that
it contains the old driver, whereas the new driver is split
between modules such as rtc, rtc_lib, rtc_core and actual
drivers like rtc_cmos - right. - and configured by such switches as
CONFIG_RTC_CLASS, CONFIG_RTC_LIB and CONFIG_RTC_DRV_CMOS. There might
also be a CONFIG_RTC variable, about which I m not sure.
I m also very confused about how HPET s tie into this, and what
CONFIG_HPET_EMULATE_RTC does, for example.
Now how do I know what s on my system. It s an ASUS P5W64 WS Pro
based x86_64. I certainly have some kind of CMOS clock that I can
configure in my BIOS, but I don t know about HPET s or other kind of
RTC sources.
I tried using the following config this is all with 2.6.22.10 :
CONFIG_RTC m
CONFIG_GEN_RTC m
CONFIG_GEN_RTC_X y
CONFIG_HPET y
CONFIG_HPET_RTC_IRQ is not set
CONFIG_RTC_LIB m
CONFIG_RTC_CLASS m
CONFIG_RTC_INTF_SYSFS y
CONFIG_RTC_INTF_PROC y
CONFIG_RTC_INTF_DEV y
CONFIG_RTC_INTF_DEV_UIE_EMUL y
CONFIG_RTC_DRV_TEST m
CONFIG_RTC_DRV_CMOS m
CONFIG_RTC_DRV_DS1553 is not set
CONFIG_RTC_DRV_DS1742 is not set
CONFIG_RTC_DRV_M48T86 is not set
CONFIG_RTC_DRV_V3020 is not set
Now if I load the genrtc module to use the old driver., I get a
/dev/rtc which may or may not be satisfactory but the
dev.rtc.max-user-freq sysctl does not exist and ALSA does not use
snd_rtctimer. If I try unloading genrtc and instead loading the rtc,
rtc_lib, rtc_core and rtc_cmos modules to use the new driver., I
get the following error in dmesg:
Real Time Clock Driver v1.12ac
rtc_cmos : rtc core: registered rtc_cmos as rtc0
rtc_cmos: probe of failed with error -16
After what attempts to, e.g., play a MIDI file with ALSA, fail only a
single note is played and the following error occurs in dmesg:
rtc: lost some interrupts at 1024Hz.
So, why does rtc_cmos fail that way. And how am I supposed to
configure RTC as a whole. I will, of course, gladly provide more
information if requested.
Thanks for any help.
--
David A. Madore
david.madore xxxxxx,
david/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majordomo xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at.
any help on RTC-related config? (and "rtc_cmos: probe of 00:03 failed with error -16" error message)
