From: Zachary Amsden <zach@vmware.com>
To: Marcos Pinto <markybob@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VMware, x86_64 and 2.6.21.
Date: Tue, 01 May 2007 15:38:07 -0700 [thread overview]
Message-ID: <4637C14F.3050702@vmware.com> (raw)
In-Reply-To: <62eb359a0704302350m5e639c17t8517865c885c9ba9@mail.gmail.com>
Marcos Pinto wrote:
> I'm having the same problem. I think it has to do with timer problems...
> Does /sbin/hwclock --show freeze your box? It "sometimes" works on
> mine, but it more often than not locks it hard (especially as user,
> not root) with no hints in syslog or anywhere else as to what
> happened. This is a turion x2 with nvidia mcp51
/sbin/hwclock freezes the whole box for me turion x2 with nvidia mcp51
(HP Pavillion dv9210us), but only when syncing hwclock to system time.
I suspect it could be a hwclock IOPL bug, but I will have to check
source to be sure. But I see this with 2.6.20 Gentoo kernel, not just
2.6.21, so I think it is a different bug.
Zach
next prev parent reply other threads:[~2007-05-01 22:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 6:50 VMware, x86_64 and 2.6.21 Marcos Pinto
2007-05-01 7:06 ` Nigel Cunningham
2007-05-01 22:38 ` Zachary Amsden [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-01 5:42 Nigel Cunningham
2007-05-01 6:13 ` Jeff Chua
2007-05-01 6:33 ` Nigel Cunningham
2007-05-01 11:09 ` Jan Engelhardt
2007-05-01 12:51 ` Jeff Chua
2007-05-01 7:24 ` Michael Gerdau
2007-05-01 7:36 ` Nigel Cunningham
2007-05-01 11:10 ` Jan Engelhardt
2007-05-01 11:54 ` Nigel Cunningham
2007-05-01 13:46 ` Mark Lord
2007-05-01 15:09 ` Nigel Cunningham
2007-05-01 14:57 ` Arjan van de Ven
2007-05-01 15:14 ` Nigel Cunningham
2007-05-02 9:30 ` Petr Vandrovec
2007-05-04 11:40 ` Eric W. Biederman
2007-05-04 15:08 ` Zachary Amsden
2007-05-04 20:14 ` Eric W. Biederman
2007-05-04 21:04 ` Zachary Amsden
2007-05-05 9:56 ` Christoph Hellwig
2007-05-05 18:06 ` John Anthony Kazos Jr.
2007-05-06 7:16 ` Valdis.Kletnieks
2007-05-06 11:08 ` Christoph Hellwig
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=4637C14F.3050702@vmware.com \
--to=zach@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markybob@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.