From: Thomas Gleixner <tglx@linutronix.de>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Adrian Bunk <bunk@kernel.org>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Subject: Re: 2.6.24-rc6-git12: Reported regressions from 2.6.23
Date: Tue, 8 Jan 2008 09:02:21 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.0.99999.0801080900160.31637@localhost.localdomain> (raw)
In-Reply-To: <82e4877d0801071649vd0af3a0h7cb7cbd0b58353ed@mail.gmail.com>
On Mon, 7 Jan 2008, Parag Warudkar wrote:
> On Jan 7, 2008 6:54 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>
> > Well, now you're saying 2.6.23.12 is also affected, so this doesn't seem to
> > be a recent regression in fact?
> >
>
> I have run 2.6.23 series before but my usage pattern seems to have not
> triggered the bug before.
> But yes, this is a 6 month old regression based on today's findings.
> (2.6.22 which doesn't have this issue was released on July 8).
Hmm. Can you try plain 2.6.23 ? If it does not show the problem we
know that it is caused by one of the patches in the stable series.
Thanks,
tglx
prev parent reply other threads:[~2008-01-08 8:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 19:42 Rafael J. Wysocki
2008-01-05 20:06 ` Alan Cox
2008-01-05 23:39 ` Rafael J. Wysocki
2008-01-05 23:45 ` Mark Lord
2008-01-06 9:55 ` Ingo Molnar
2008-01-06 22:23 ` Arjan van de Ven
2008-01-06 22:36 ` Rafael J. Wysocki
2008-01-06 9:38 ` Ingo Molnar
2008-01-06 12:56 ` Rafael J. Wysocki
2008-01-06 14:24 ` Stefano Brivio
2008-01-06 9:45 ` Ingo Molnar
2008-01-06 12:57 ` Rafael J. Wysocki
2008-01-06 16:21 ` Parag Warudkar
2008-01-06 19:11 ` Rafael J. Wysocki
2008-01-07 23:21 ` Parag Warudkar
2008-01-07 23:54 ` Rafael J. Wysocki
2008-01-08 0:49 ` Parag Warudkar
2008-01-08 8:02 ` Thomas Gleixner [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=alpine.LFD.0.99999.0801080900160.31637@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=parag.warudkar@gmail.com \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
--cc=venkatesh.pallipadi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®