public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix•de>
To: Alexander Beregalov <a.beregalov@gmail•com>
Cc: LKML <linux-kernel@vger•kernel.org>,
	linux-next@vger•kernel.org, mingo@elte•hu
Subject: Re: next-20081119: general protection fault: get_next_timer_interrupt()
Date: Wed, 19 Nov 2008 13:14:37 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0811191308030.3119@localhost.localdomain> (raw)
In-Reply-To: <a4423d670811190714k13721ae8s125e63d520892440@mail.gmail.com>

Alexander,

On Wed, 19 Nov 2008, Alexander Beregalov wrote:
> 
> It is 4way X86_64
> The kernel does not boot.
 
> RIP: 0010:[<ffffffff80240061>]  [<ffffffff80240061>]
> get_next_timer_interrupt+0x11b/0x1f0

Can you please enable:

CONFIG_DEBUG_OBJECTS=y
CONFIG_DEBUG_OBJECTS_FREE=y
CONFIG_DEBUG_OBJECTS_TIMERS=Y

and add "debug_objects" to the kernel command line ?

Thanks,

	tglx

  reply	other threads:[~2008-11-19 21:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 15:14 next-20081119: general protection fault: get_next_timer_interrupt() Alexander Beregalov
2008-11-19 21:14 ` Thomas Gleixner [this message]
2008-11-21 10:50   ` Alexander Beregalov
2008-11-24 17:43     ` Thomas Gleixner
2008-11-24 19:15       ` James Bottomley
2008-11-24 19:31         ` Thomas Gleixner
2008-11-24 21:35           ` Mike Anderson
2008-11-24 22:33             ` Thomas Gleixner
2008-11-24 23:42               ` malahal
2008-11-25  0:09               ` malahal
2008-11-25  0:57                 ` Stephen Rothwell
2008-11-25  2:08                   ` malahal
2008-11-25  8:51                     ` Jens Axboe
2008-11-25 16:59                       ` malahal
2008-11-25 17:14                         ` Alexander Beregalov
2008-11-25 17:43                           ` Jens Axboe

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.2.00.0811191308030.3119@localhost.localdomain \
    --to=tglx@linutronix$(echo .)de \
    --cc=a.beregalov@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mingo@elte$(echo .)hu \
    /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