Bug#343227: marked as done (linux-image-2.6.12-1-amd64-k8-smp: clock running much too fast)
Your message dated Thu, 12 Jan 2006 14:57:07 +0100
with message-id <20060112135707.GM12351@mail.lowpingbastards.de>
and subject line linux-image-2.6.12-1-amd64-k8-smp: clock running much too fast
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 13 Dec 2005 19:55:12 +0000
>From martin.hans@targit.de Tue Dec 13 11:55:12 2005
Return-path: <martin.hans@targit.de>
Received: from s-targit2.sdsl-speedway.de ([213.155.74.62] helo=sgate.targit01.de)
by spohr.debian.org with esmtp (Exim 4.50)
id 1EmGEr-0005zh-1t
for submit@bugs.debian.org; Tue, 13 Dec 2005 11:55:07 -0800
Received: from sgate (localhost [127.0.0.1])
by sgate (Postfix) with SMTP
id 94B5C5288C; Tue, 13 Dec 2005 20:55:03 +0100 (CET)
Received: from beamer.targit01.de (beamer.targit01.de [192.168.2.12])
by sgate.targit01.de (Postfix) with ESMTP
id 6A6EB52886; Tue, 13 Dec 2005 20:55:03 +0100 (CET)
Received: by beamer.targit01.de (Postfix, from userid 0)
id 9F53F5E559; Tue, 13 Dec 2005 20:55:03 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Martin Hans <martin.hans@targit.de>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: linux-image-2.6.12-1-amd64-k8-smp: clock running much too fast
Message-ID: <20051213195503.29906.42237.reportbug@beamer.targit01.de>
X-Mailer: reportbug 3.18
Date: Tue, 13 Dec 2005 20:55:03 +0100
X-Anti-Virus: Kaspersky Anti-Virus for MailServers 5.5.2/RELEASE, bases: 13122005 #155020, status: clean
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: linux-image-2.6.12-1-amd64-k8-smp
Version: 2.6.12-10
Severity: minor
Regarding my own installation (bug) report #341096
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341096)
I just want to file my kernel issue directly to the related linux-2.6 package
to clarify if it is a bug or not and if the solution is the proper way
to handle the issue.
Here the iimportant part my original installation report:
I changed to a smp kernel and got problems with the clock running much
too fast. I found some kernel options in some forums which solved the
problem:
notsc no_timer_check
http://groups.google.de/group/linux.debian.ports.x86-64/browse_frm/thread/4aae438ff566835a/d3db60cab325acc6?lnk=st&q=linux+amd+dual+core+clock&rnum=6&hl=de#d3db60cab325acc6
---
I'm not sure if this is the correct solution for the clock problem.
But I have a productive system working fine since two weeks with the
notsc no_timer_check options.
Cheers
Martin Hans
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-amd64-k8-smp
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages linux-image-2.6.12-1-amd64-k8-smp depends on:
ii coreutils [fileutils] 5.2.1-2.1 The GNU core utilities
ii e2fsprogs 1.38-2 ext2 file system utilities and lib
ii initrd-tools 0.1.84 tools to create initrd image for p
ii module-init-tools 3.2-pre9-4 tools for managing Linux kernel mo
linux-image-2.6.12-1-amd64-k8-smp recommends no packages.
-- no debconf information
---------------------------------------
Received: (at 343227-done) by bugs.debian.org; 12 Jan 2006 13:57:17 +0000
>From freddy@lowpingbastards.de Thu Jan 12 05:57:17 2006
Return-path: <freddy@lowpingbastards.de>
Received: from defiant.lowpingbastards.de
([213.178.77.226] helo=mail.lowpingbastards.de ident=UNKNOWN)
by spohr.debian.org with esmtp (Exim 4.50)
id 1Ex2x0-0003YI-Aq
for 343227-done@bugs.debian.org; Thu, 12 Jan 2006 05:57:16 -0800
Received: from defiant.lowpingbastards.de (freddy@localhost.lowpingbastards.de [127.0.0.1])
by mail.lowpingbastards.de (8.13.4/8.13.4/Debian-3) with ESMTP id k0CDv87o007834
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Thu, 12 Jan 2006 14:57:08 +0100
Received: (from freddy@localhost)
by defiant.lowpingbastards.de (8.13.4/8.13.4/Submit) id k0CDv78U007833;
Thu, 12 Jan 2006 14:57:08 +0100
Date: Thu, 12 Jan 2006 14:57:07 +0100
From: Frederik Schueler <fs@debian.org>
To: 343227-done@bugs.debian.org
Subject: RE: linux-image-2.6.12-1-amd64-k8-smp: clock running much too fast
Message-ID: <20060112135707.GM12351@mail.lowpingbastards.de>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="6o78gXsyQHm68LY/"
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: by amavisd-new
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
--6o78gXsyQHm68LY/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hello,
this seems to be a hardware problem, and as you already found the kernel
workaround parameters (notsc no_timer_check), I am closing the bug.
Best regards
Frederik Schueler
--=20
ENOSIG
--6o78gXsyQHm68LY/
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDxmAz6n7So0GVSSARAlBuAJ97buViUszRwwetjCdfPXbjVe89YgCfX88c
rERLsm+xvGcYLBW4OfuS7Bk=
=5xzP
-----END PGP SIGNATURE-----
--6o78gXsyQHm68LY/--
Reply to: