From: Mattia Dongili <malattia@linux.it>
To: john stultz <johnstul@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: first bisection results in -mm3 [was: Re: 2.6.15-mm2: reiser3 oops on suspend and more (bonus oops shot!)]
Date: Wed, 25 Jan 2006 00:04:54 +0100 [thread overview]
Message-ID: <20060124230453.GA6174@inferi.kami.home> (raw)
In-Reply-To: <1138141635.15682.92.camel@cog.beaverton.ibm.com>
On Tue, Jan 24, 2006 at 02:27:14PM -0800, john stultz wrote:
> On Wed, 2006-01-18 at 11:47 +0100, Mattia Dongili wrote:
> > On Tue, January 17, 2006 11:49 pm, Mattia Dongili said:
> > [...]
> > > the stall is still there, tomorrow I'll reapply your debug-patch and
> > > report the full dmesg (with the finished_booting-hack enabled).
> >
> > Full dmesg attached.
> > Stalls happened between in the 16.39-16.55 interval, in 16.70-16.96 and
> > 17.89-18.64. They were all much longer than stated in the log timestamp
> > (I'd say ~10:1 ratio).
> >
> > Sorry again for my previous false notice about the bug being solved...
>
> Hey Mattia,
> Sorry I've been so quiet recently, I'm still working on this one. The
No problem.
> difficult spot is that if the cpufreq notification driver is a module,
> then there will always be a window between the point at which we start
> using the TSC to the point where we find out that the TSC is changing
> frequency. Not sure what to do here just yet.
I was wondering if you could force an do_gettimeofday call quite early
in order to lower tsc priority as soon as possible, but maybe I'm not
entirely into that code :)
> Although I'm curious: Did the recent changes in 2.6.16-rc1-mm2 had any
> effect on this issue?
no, I'm currently running it and the same behaviour still applies.
ciao
--
mattia
:wq!
next prev parent reply other threads:[~2006-01-24 23:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 23:55 2.6.15-mm2: reiser3 oops on suspend and more (bonus oops shot!) Mattia Dongili
2006-01-11 1:00 ` Andrew Morton
2006-01-11 10:00 ` Pavel Machek
2006-01-11 11:24 ` Mattia Dongili
2006-01-11 18:40 ` Mattia Dongili
2006-01-12 22:08 ` first bisection results in -mm3 [was: Re: 2.6.15-mm2: reiser3 oops on suspend and more (bonus oops shot!)] Mattia Dongili
2006-01-12 23:26 ` john stultz
2006-01-14 12:08 ` Mattia Dongili
2006-01-16 20:16 ` john stultz
2006-01-16 20:40 ` Mattia Dongili
2006-01-16 21:42 ` john stultz
2006-01-16 22:19 ` Andi Kleen
2006-01-16 22:41 ` john stultz
2006-01-17 16:43 ` Mattia Dongili
2006-01-17 16:45 ` Mattia Dongili
2006-01-17 0:49 ` john stultz
2006-01-17 17:49 ` Mattia Dongili
2006-01-17 19:11 ` john stultz
2006-01-17 22:49 ` Mattia Dongili
2006-01-18 10:47 ` Mattia Dongili
2006-01-24 22:27 ` john stultz
2006-01-24 23:04 ` Mattia Dongili [this message]
2006-01-24 23:48 ` john stultz
2006-01-25 0:12 ` john stultz
2006-01-25 18:12 ` Mattia Dongili
2006-01-11 10:02 ` 2.6.15-mm2: reiser3 oops on suspend and more (bonus oops shot!) Pavel Machek
2006-01-11 14:27 ` Mattia Dongili
2006-01-15 22:14 ` 2.6.15-mm3 bisection: git-xfs.patch makes reiserfs oops Mattia Dongili
2006-01-15 22:48 ` Nathan Scott
2006-01-15 23:22 ` Mattia Dongili
2006-01-16 9:29 ` Hans Reiser
2006-01-16 11:48 ` Christoph Hellwig
2006-01-16 15:50 ` Mattia Dongili
2006-01-17 3:27 ` Hans Reiser
2006-01-16 11:51 ` Mattia Dongili
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=20060124230453.GA6174@inferi.kami.home \
--to=malattia@linux.it \
--cc=akpm@osdl.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).