From: David Witbrodt <dawitbro@sbcglobal.net>
To: paulmck@linux.vnet.ibm.com
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Yinghai Lu <yhlu.kernel@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH diagnostic] Re: HPET regression in 2.6.26 versus 2.6.25 -- RCU problem
Date: Mon, 11 Aug 2008 11:22:21 -0700 (PDT) [thread overview]
Message-ID: <173065.89301.qm@web82104.mail.mud.yahoo.com> (raw)
> > Well, I was hoping to see something interesting. I ran it with parameters
> > "debug initcall_debug", and it locked up at the same place. I let it for
> > 15 minutes, in case of some delayed reaction. Nada.
>
> Interesting. The causes could be:
>
> o Scheduling-clock interrupts aren't happening, as Ingo suggested.
Does anyone have a short answer to this question: Were the changes between
2.6.25 and 2.6.26 so major that interrupts are NOW being used that were not
being used before?
Again, I don't even pretend to understand the kernel's inner workings, but
2.6.25 _did_ work on this hardware... and with HPET enabled.
DW
next reply other threads:[~2008-08-11 18:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 18:22 David Witbrodt [this message]
2008-08-11 19:27 ` [PATCH diagnostic] Re: HPET regression in 2.6.26 versus 2.6.25 -- RCU problem Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2008-08-11 18:13 David Witbrodt
2008-08-11 16:22 David Witbrodt
2008-08-11 16:29 ` Paul E. McKenney
2008-08-11 16:04 David Witbrodt
2008-08-11 16:22 ` Paul E. McKenney
2008-08-09 22:35 David Witbrodt
2008-08-10 15:15 ` Paul E. McKenney
2008-08-11 1:35 ` [PATCH diagnostic] " Paul E. McKenney
2008-08-11 1:38 ` Paul E. McKenney
2008-08-11 11:38 ` Ingo Molnar
2008-08-11 13:17 ` Paul E. McKenney
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=173065.89301.qm@web82104.mail.mud.yahoo.com \
--to=dawitbro@sbcglobal.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@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 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).