mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Timo Schroeter" <timsch@gmx.net>
To: <linux-kernel@vger.kernel.org>
Subject: Re: AMD64 X2 lost ticks on PM timer
Date: Mon, 6 Mar 2006 22:36:57 +0100	[thread overview]
Message-ID: <000001c64166$1853c2d0$0100000a@xin> (raw)
In-Reply-To: <20060306173659.GA12970@halcrow.us>

Hi,

I have the same problem with my Tyan K8E Board. I've connected 2 WD raptor
to the onboard SATA ports (nForce 4, RAID0 md). I noticed that my server
hung up this night, after reboot and checking the logfiles I found the same
messages:

time.c: Lost 141 timer tick(s)! rip poll_idle+0x14/0x19)
time.c: Lost 127 timer tick(s)! rip poll_idle+0xa/0x19)
time.c: Lost 92 timer tick(s)! rip poll_idle+0x14/0x19)
time.c: Lost 64 timer tick(s)! rip poll_idle+0xa/0x19)

I dont use the onboard nFORCE4 NIC but the BROADCOM one. 

I ran ./trtc with the following results:

1141680789:835638: rtc 256 int 0 0 (=0)
1141680790:104663: rtc 464 int 269 0 (=269)
1141680790:604729: rtc 448 int 501 0 (=501)
1141680791:104795: rtc 464 int 500 0 (=500)
1141680791:604862: rtc 448 int 500 0 (=500)
1141680792:104927: rtc 464 int 500 0 (=500)
1141680792:604994: rtc 448 int 500 0 (=500)
1141680793:105060: rtc 464 int 500 0 (=500)
1141680793:605126: rtc 448 int 500 0 (=500)
1141680794:105192: rtc 464 int 501 0 (=501)
1141680794:605259: rtc 448 int 500 0 (=500)
1141680795:105326: rtc 464 int 500 0 (=500)
1141680795:605392: rtc 448 int 500 0 (=500)
1141680796:105458: rtc 464 int 500 0 (=500)
1141680796:605525: rtc 448 int 500 0 (=500)
1141680797:105592: rtc 464 int 500 0 (=500)
1141680797:605658: rtc 448 int 501 0 (=501)
1141680798:105725: rtc 464 int 500 0 (=500)

I wonder if my server was frozen because of this error. If there will be no
fix soon, I think ist better to get a PCIexpress SATA2 card :(

Regards,

Timo Schroeter


  reply	other threads:[~2006-03-06 21:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 10:31 [RFC] Encrypting file system V Bhanu Chandra
2006-03-06 12:17 ` Mario 'BitKoenig' Holbe
2006-03-06 13:05   ` Eduard Bloch
2006-03-06 17:37 ` Michael Halcrow
2006-03-06 21:36   ` Timo Schroeter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-27 21:22 AMD64 X2 lost ticks on PM timer bubshait
2006-02-27 22:21 ` Bill Rugolsky Jr.
2006-02-27 22:47   ` Jason Baron
2006-02-28  7:41     ` Abdulla Bubshait
2006-02-28 22:00       ` Bill Rugolsky Jr.
2006-02-28 23:53         ` Andi Kleen
2006-03-01 14:46           ` Bill Rugolsky Jr.
2006-03-01 14:56             ` Andi Kleen
2006-03-01 15:43               ` Bill Rugolsky Jr.
2006-03-01 15:47                 ` Andi Kleen
2006-03-01 18:07                   ` Bill Rugolsky Jr.
2006-03-01 18:29                     ` Andi Kleen
2006-03-01 19:16                       ` Lee Revell
2006-03-03 19:18                         ` Bill Rugolsky Jr.
2006-03-03 21:26                           ` Lee Revell
2006-03-03 22:09                             ` Jeff Garzik
2006-03-03 23:43                               ` Bill Rugolsky Jr.
2006-03-03 23:46                                 ` Jeff Garzik
2006-03-03 23:49                                   ` Lee Revell
2006-03-04  0:08                                   ` Andi Kleen
2006-03-04  0:07                                 ` Andi Kleen
2006-03-04 12:06                                 ` Martin Schlemmer
2006-03-05  7:07                                   ` Alexander Samad
2006-03-02 15:47                 ` Gabor Gombas
2006-02-28 21:17     ` Abdulla Bubshait

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='000001c64166$1853c2d0$0100000a@xin' \
    --to=timsch@gmx.net \
    --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

Powered by JetHome