public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, kernel-testers@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: Re: 2.6.30-rc6: Reported regressions from 2.6.29
Date: Tue, 26 May 2009 20:48:12 +0200	[thread overview]
Message-ID: <200905262048.13325.rjw@sisk.pl> (raw)
In-Reply-To: <200905261730.53041.elendil@planet.nl>

On Tuesday 26 May 2009, Frans Pop wrote:
> On Tuesday 26 May 2009, Rafael J. Wysocki wrote:
> > On Monday 25 May 2009, Frans Pop wrote:
> > > Rafael J. Wysocki wrote:
> > > > If you know of any other unresolved regressions from 2.6.29, please
> > > > let me know either and I'll add them to the list.
> > >
> > > It may be worth tracking a possible regression introduced with -rc6
> > > as a result of http://bugzilla.kernel.org/show_bug.cgi?id=13259.
> > >
> > > A new warning that was added in drivers/acpi/processor_throttling.c
> > > (commit 4973b22a: 'ACPI processor: reset the throttling state once
> > > it's invalid') may be triggering in cases where it shouldn't. It
> > > seems to trigger during boot and on 'cat
> > > /proc/acpi/processor/*/throttling'. Otherwise it's probably
> > > relatively harmless.
> > >
> > > See the comments starting at #23 for details.
> >
> > Hmm.  It's really better if you file a separate bug for that with a
> > reference to the previous discussion.
> 
> Done (after doing additional debugging):
> http://bugzilla.kernel.org/show_bug.cgi?id=13389
> 
> Marked as regression and set as blocking for #13070.

Thanks!

Best,
Rafael

      reply	other threads:[~2009-05-26 18:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-16 19:14 2.6.30-rc6: Reported regressions from 2.6.29 Rafael J. Wysocki
2009-05-17  7:33 ` Ingo Molnar
     [not found]   ` <20090517073327.GC1583-X9Un+BFzKDI@public.gmane.org>
2009-05-17 10:34     ` Rafael J. Wysocki
2009-05-18 14:57   ` Oleg Nesterov
2009-05-18 15:11     ` Ingo Molnar
2009-05-18 15:31       ` Oleg Nesterov
2009-05-18 15:32       ` Linus Torvalds
2009-05-18 15:45         ` Oleg Nesterov
2009-05-22 16:40 ` Linus Torvalds
     [not found]   ` <alpine.LFD.2.01.0905220926150.3555-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-05-23  0:10     ` Rafael J. Wysocki
2009-05-25 20:24 ` Frans Pop
     [not found]   ` <200905252224.37012.elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
2009-05-25 23:02     ` Rafael J. Wysocki
2009-05-26 15:30       ` Frans Pop
2009-05-26 18:48         ` Rafael J. Wysocki [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=200905262048.13325.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=elendil@planet.nl \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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