All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amerigo Wang <amwang@redhat.com>
To: CAI Qian <caiqian@redhat.com>
Cc: nhorman@redhat.com, kexec@lists.infradead.org
Subject: Re: Kdump Failed with 2.6.31 i386
Date: Fri, 09 Oct 2009 15:44:53 +0800	[thread overview]
Message-ID: <4ACEE9F5.2020306@redhat.com> (raw)
In-Reply-To: <20091009.120533.370613410103983527.caiqian@redhat.com>

CAI Qian wrote:
> Hallo!
> 
> Is it a known issue that kdump failed with 2.6.31 i386 systems? The
> kdump kernel seems hang here.
> 
> ...
> Spurious LAPIC timer interrupt on cpu 0
> Console: colour VGA+ 80x25
> console handover: boot [earlyser0] -> real [ttyS0]
> Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
> ... MAX_LOCKDEP_SUBCLASSES:  8
> ... MAX_LOCK_DEPTH:          48
> ... MAX_LOCKDEP_KEYS:        8191
> ... CLASSHASH_SIZE:          4096
> ... MAX_LOCKDEP_ENTRIES:     16384
> ... MAX_LOCKDEP_CHAINS:      32768
> ... CHAINHASH_SIZE:          16384
>  memory used by lock dependency info: 3743 kB
>  per task-struct memory footprint: 1920 bytes
> HPET: 3 timers in total, 0 timers will be used for per-cpu timer
> Clocksource tsc unstable (delta = 577041676100 ns)
> 


This case hangs on setup_irq(0, &irq0). We already knew this.

> or
> 
> Spurious LAPIC timer interrupt on cpu 0
> Console: colour VGA+ 80x25
> console [ttyS0] enabled
> Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
> ... MAX_LOCKDEP_SUBCLASSES:  8
> ... MAX_LOCK_DEPTH:          48
> ... MAX_LOCKDEP_KEYS:        8191
> ... CLASSHASH_SIZE:          4096
> ... MAX_LOCKDEP_ENTRIES:     16384
> ... MAX_LOCKDEP_CHAINS:      32768
> ... CHAINHASH_SIZE:          16384
>  memory used by lock dependency info: 3743 kB
>  per task-struct memory footprint: 1920 bytes
> allocated 2621440 bytes of page_cgroup
> please try 'cgroup_disable=memory' option if you don't want memory cgroups
> Calibrating delay loop (skipped), value calculated using timer frequency.. 
> 5986.01 BogoMIPS (lpj=2993008)

This case hangs after calibrate_delay() which already passed 
late_time_init(), and probably before security_init()...
(since probably you have CONFIG_SECURITY=y)

Did you meet these two cases on the same machine? Or on different machines?

Thanks.



_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2009-10-09  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09  4:05 Kdump Failed with 2.6.31 i386 CAI Qian
2009-10-09  7:44 ` Amerigo Wang [this message]
2009-10-09  7:58   ` CAI Qian

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=4ACEE9F5.2020306@redhat.com \
    --to=amwang@redhat.com \
    --cc=caiqian@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=nhorman@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.