From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Vegard Nossum" <vegard.nossum@gmail.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
"Mike Travis" <travis@sgi.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Steven Rostedt" <rostedt@goodmis.org>
Subject: Re: per-cpu related?
Date: Sun, 13 Jul 2008 11:34:04 -0700 [thread overview]
Message-ID: <86802c440807131134i351f967dh3a2b94d687c767ee@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0807130455w516d73cfi80161c345564464@mail.gmail.com>
On Sun, Jul 13, 2008 at 4:55 AM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
> Hi,
>
> On Sun, Jul 13, 2008 at 10:16 AM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
>> calling pcie_portdrv_init+0x0/0x77
>> BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
>> IP: [<ffffffff802557de>] hrtick_start_fair+0x8e/0x178
>> PGD 0
>> Oops: 0000 [1] SMP
>> CPU 4
>> Modules linked in:
>> Pid: 103, comm: events/4 Not tainted 2.6.26-rc9-tip-01834-g99e624f-dirty #354
>> RIP: 0010:[<ffffffff802557de>] [<ffffffff802557de>]
>> hrtick_start_fair+0x8e/0x178
>
> I find that this corresponds to timer->base being NULL:
>
> static inline int hrtimer_is_hres_active(struct hrtimer *timer)
> {
> return timer->base->cpu_base->hres_active;
> }
>
> Apparently timer->base can legitimately be NULL in some cases:
thanks
could be caused by max_low_pfn_mapped patch...because hpet still use
fixmap address that is cleared by others.
will check that.
YH
next prev parent reply other threads:[~2008-07-13 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 8:16 Yinghai Lu
2008-07-13 9:26 ` Ingo Molnar
2008-07-13 10:46 ` Vegard Nossum
2008-07-13 11:55 ` Vegard Nossum
2008-07-13 18:34 ` Yinghai Lu [this message]
2008-07-13 18:55 ` Ingo Molnar
2008-07-13 21:01 ` Yinghai Lu
2008-07-13 21:04 ` Ingo Molnar
2008-07-13 22:20 ` Yinghai Lu
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=86802c440807131134i351f967dh3a2b94d687c767ee@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=vegard.nossum@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
all inboxes | Powered by JetHome®