From: David Witbrodt <dawitbro@sbcglobal•net>
To: Yinghai Lu <yhlu.kernel@gmail•com>
Cc: Bill Fink <billfink@mindspring•com>,
linux-kernel@vger•kernel.org, Ingo Molnar <mingo@elte•hu>,
"Paul E. McKenney" <paulmck@linux•vnet.ibm.com>,
Peter Zijlstra <peterz@infradead•org>,
Thomas Gleixner <tglx@linutronix•de>,
"H. Peter Anvin" <hpa@zytor•com>, netdev <netdev@vger•kernel.org>
Subject: Re: HPET regression in 2.6.26 versus 2.6.25 -- revert for 2.6.26-rc1 failed
Date: Thu, 14 Aug 2008 11:11:37 -0700 (PDT) [thread overview]
Message-ID: <798351.12728.qm@web82105.mail.mud.yahoo.com> (raw)
> can you try enable kexec and kdump in you .config.
>
> it should works. my .config have config_kexec
First, I apologize. I see that you were assuming I had KEXEC enabled when you
gave me the patch against 2.6.27-rc3. I have only posted parts of my custom
.config to LKML, thinking that posting the whole thing was not appropriate.
Did you mean CRASH_DUMP instead of "kdump" above?
[N] kexec system call (CONFIG_KEXEC) (bool) (Help)
[N] kernel crash dumps (EXPERIMENTAL) (CONFIG_CRASH_DUMP) (bool) (Help)
My custom .config has both of these disabled -- either because they default
to "N" when running 'make oldconfig', or because I read the help text with
those options and decided I would not be using those features.
> > Some experiments I did last night may render these questions moot, though.
> > My problem is very specific to the hardware on two of my machines, and it
> > has something to do with setting up the system resources that
> > insert_resource() touches.
>
> please try to bisect on current tree. and every time apply the revert patch...
I will try your patch against 2.6.27-rc3 again, with KEXEC and CRASH_DUMP
enabled, when I get home from work. I still have not retried using 'patch'
instead of 'git apply', though I am sure that 'git apply' worked just fine.
I was trying other experiments last night, and have posted the results of
those already -- and I'm guessing that your 2.6.27-rc3 patch will not work
unless it factors in what I discovered there. (But I will do all of these
changes that you asked, as well.)
I do not know how to bisect with your patch if I have a "bad" but no "good"
to start with. Can you explain how I should proceed when I _do_ get home?
(I can just enabled those config options and try the patch again, but I am
confused about the bisect you are asking me to perform.)
Does my other post, about trying to revert those February commits, mean
anything?
Thanks,
Dave W.
next reply other threads:[~2008-08-14 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 18:11 David Witbrodt [this message]
2008-08-14 18:29 ` HPET regression in 2.6.26 versus 2.6.25 -- revert for 2.6.26-rc1 failed Yinghai Lu
-- strict thread matches above, loose matches on Subject: below --
2008-08-14 22:25 David Witbrodt
2008-08-14 12:03 David Witbrodt
2008-08-14 17:39 ` Yinghai Lu
2008-08-13 15:41 David Witbrodt
2008-08-14 10:04 ` Bill Fink
2008-08-14 10:36 ` Yinghai Lu
2008-08-15 7:17 ` Bill Fink
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=798351.12728.qm@web82105.mail.mud.yahoo.com \
--to=dawitbro@sbcglobal$(echo .)net \
--cc=billfink@mindspring$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=netdev@vger$(echo .)kernel.org \
--cc=paulmck@linux$(echo .)vnet.ibm.com \
--cc=peterz@infradead$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
--cc=yhlu.kernel@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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