From: Florian Lohoff <flo@rfc822.org>
To: linux-kernel@vger.kernel.org
Subject: Boot fails with 2.6.20-rc3 / git-current Was: 2.6.20-rc3: Clocksource tsc unstable
Date: Tue, 13 Mar 2007 16:04:35 +0100 [thread overview]
Message-ID: <20070313150435.GA26303@paradigm.rfc822.org> (raw)
In-Reply-To: <4af2d03a0703090941hfebc1e5u5def6152847c965a@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2981 bytes --]
On Fri, Mar 09, 2007 at 06:41:45PM +0100, Jiri Slaby wrote:
> Hi.
>
> I got this message after suspend;resume on my notebook
> Clocksource tsc unstable (delta = -154983451 ns)
>
I am getting the exact same line on bootup on my Fujitsu Siemens
Lifebook E8110. After that line the boot halts with current git:
Last lines on current git were:
IPMI System Interface driver
Clocksource tsc unstable ( delta = -160251929ns )
Now running:
Linux laptop 2.6.21-rc2 #1 SMP PREEMPT Thu Mar 1 07:41:52 CET 2007 i686 GNU/Linux
which comes up with the same line when initializing IDE but continues
to run:
[ 9.912917] ICH7: IDE controller at PCI slot 0000:00:1f.1
[ 9.913025] ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 20
[ 9.913210] ICH7: chipset revision 2
[ 9.913300] ICH7: not 100% native mode: will probe irqs later
[ 9.913403] ide0: BM-DMA at 0x1810-0x1817, BIOS settings: hda:DMA, hdb:pio
[ 9.913637] Probing IDE interface ide0...
[ 9.997936] Clocksource tsc unstable (delta = -430882190 ns)
[ 10.002393] hda: MATSHITAUJ-841Db, ATAPI CD/DVD-ROM drive
[ 10.003539] ieee1394: Host added: ID:BUS[0-00:1023] GUID[00000e10036532e4]
[ 10.052945] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
CPU info:
flo@laptop:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2400 @ 1.83GHz
stepping : 8
cpu MHz : 1333.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor vmx est tm2 xtpr
bogomips : 3662.23
clflush size : 64
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2400 @ 1.83GHz
stepping : 8
cpu MHz : 1333.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor vmx est tm2 xtpr
bogomips : 3657.63
clflush size : 64
--
Florian Lohoff flo@rfc822.org +49-171-2280134
Those who would give up a little freedom to get a little
security shall soon have neither - Benjamin Franklin
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-03-13 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 17:41 2.6.20-rc3: Clocksource tsc unstable Jiri Slaby
2007-03-13 15:04 ` Florian Lohoff [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070313150435.GA26303@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).