Bug#694012: marked as done (xen-hypervisor-4.1-amd64: powernow-k8: transition frequency failed [filling the syslog])
Your message dated Sat, 1 May 2021 16:53:00 +0200
with message-id <YI1rTMdcrdcCn0sh@eldamar.lan>
and subject line Re: Bug#694012: [Pkg-xen-devel] Bug#694012: xen-hypervisor-4.1-amd64: powernow-k8: transition frequency failed [filling the syslog]
has caused the Debian Bug report #694012,
regarding xen-hypervisor-4.1-amd64: powernow-k8: transition frequency failed [filling the syslog]
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
694012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694012
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: xen-hypervisor-4.1-amd64: powernow-k8: transition frequency failed [filling the syslog]
- From: Axel Beckert <abe@debian.org>
- Date: Fri, 23 Nov 2012 00:28:08 +0100
- Message-id: <873901b4l3.fsf@acromantula.ethz.ch>
Package: xen-hypervisor-4.1-amd64
Version: 4.1.3-3
Severity: normal
Forwarded: http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1789
Dear Debian Xen Team,
after an upgrade from Squeeze to Wheezy I see about ten of these per
second filling my system log (about 8 MB/h):
Nov 23 00:15:37 acromantula kernel: [ 462.544193] powernow-k8: fid trans failed, fid 0x2, curr 0x0
Nov 23 00:15:37 acromantula kernel: [ 462.546919] powernow-k8: transition frequency failed
This seems to be a known upstream issue, see
http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1789
It also has been reported against Ubuntu Precise:
https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1038332
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (600, 'testing'), (200, 'unstable'), (110, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
xen-hypervisor-4.1-amd64 depends on no packages.
Versions of packages xen-hypervisor-4.1-amd64 recommends:
ii xen-utils-4.1 4.1.3-3
Versions of packages xen-hypervisor-4.1-amd64 suggests:
ii xen-docs-4.1 4.1.3-3
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: Axel Beckert <abe@debian.org>, 694012-done@bugs.debian.org
- Subject: Re: Bug#694012: [Pkg-xen-devel] Bug#694012: xen-hypervisor-4.1-amd64: powernow-k8: transition frequency failed [filling the syslog]
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Sat, 1 May 2021 16:53:00 +0200
- Message-id: <YI1rTMdcrdcCn0sh@eldamar.lan>
- In-reply-to: <20121123134747.GC15534@sym.noone.org>
- References: <873901b4l3.fsf@acromantula.ethz.ch> <20121123095235.GA6606@waldi.eu.org> <20121123134747.GC15534@sym.noone.org>
Source: linux
Source-Version: 3.4.4-1~experimental.1
On Fri, Nov 23, 2012 at 02:47:48PM +0100, Axel Beckert wrote:
> Hi Waldi,
>
> Bastian Blank wrote:
> > Control: reassign -1 src:linux 3.2.32-1
> > Control: severity -1 important
> >
> > On Fri, Nov 23, 2012 at 12:28:08AM +0100, Axel Beckert wrote:
> > > after an upgrade from Squeeze to Wheezy I see about ten of these per
> > > second filling my system log (about 8 MB/h):
> > > Nov 23 00:15:37 acromantula kernel: [ 462.544193] powernow-k8: fid trans failed, fid 0x2, curr 0x0
> > > Nov 23 00:15:37 acromantula kernel: [ 462.546919] powernow-k8: transition frequency failed
> > > This seems to be a known upstream issue, see
> > > http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1789
> >
> > This is a bug in the kernel. The hypervisor correctly denies access to
> > the hardware.
>
> Ah, thanks for the summary.
>
> Workaround for me to stop log file filling: "rmmod powernow_k8"
If I understand correctly this has been fixed on kernel side around
3.4~rc1, correct? I'm closing the bug for now, but please reopen if
the hardware is still in use and the problem reproducible.
Regards,
Salvatore
--- End Message ---
Reply to: