From: CAI Qian <caiqian@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: torvalds@linux-foundation.org, linux-next@vger.kernel.org,
kexec <kexec@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: kdump regression compared to v2.6.35
Date: Sun, 29 Aug 2010 07:56:45 -0400 (EDT) [thread overview]
Message-ID: <1236896997.1479691283083005518.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <171172387.1479581283082093912.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
----- caiqian@redhat.com wrote:
> ----- "Tejun Heo" <tj@kernel.org> wrote:
>
> > Hello,
> >
> > On 08/29/2010 01:24 PM, CAI Qian wrote:
> > >> On 08/29/2010 09:01 AM, caiqian@redhat.com wrote:
> > >>> Further bisect indicated this bad commit from the merge. Given
> kdump
> > >>> kernel was running with maxcpus=1, I guess this work caused
> > fs/bio.c
> > >>> hung in the workqueue on UP. Reverted the whole merge let kdump
> > work
> > >>> again.
> > >>
> > >> Can you please pull from the following git tree and see whether
> it
> > >> fixes the problem? There was a bug in nr_active accounting.
> > >
> > > It had the same problem.
> >
> > I see. Hmm... a different issue then. Can you please tell me how
> to
> > reproduce the problem?
It is easy to reproduce by passing maxcpus=1 to the first kernel.
> First, to configure kdump - see Documentation/kdump/kdump.txt. It
> might be easier if you are using a distro that provide advanced kdump
> tools. Then, to trigger the kdump - echo c >/proc/sysrq-trigger. In
> case needed, here is the system information,
> # lscpu
> Architecture: x86_64
> CPU op-mode(s): 32-bit, 64-bit
> CPU(s): 64
> Thread(s) per core: 2
> Core(s) per socket: 8
> CPU socket(s): 4
> NUMA node(s): 4
> Vendor ID: GenuineIntel
> CPU family: 6
> Model: 46
> Stepping: 6
> CPU MHz: 1064.000
> Virtualization: VT-x
> L1d cache: 32K
> L1i cache: 32K
> L2 cache: 256K
> L3 cache: 18432K
> NUMA node0 CPU(s): 0,4,8,12,16,20,24,28,32,36,40,44,48,52,56,60
> NUMA node1 CPU(s): 1,5,9,13,17,21,25,29,33,37,41,45,49,53,57,61
> NUMA node2 CPU(s): 2,6,10,14,18,22,26,30,34,38,42,46,50,54,58,62
> NUMA node3 CPU(s): 3,7,11,15,19,23,27,31,35,39,43,47,51,55,59,63
>
> > Thanks.
> >
> > --
> > tejun
> >
> > _______________________________________________
> > kexec mailing list
> > kexec@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-08-29 11:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <123671462.1479561283081998014.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-29 11:41 ` caiqian
2010-08-29 11:56 ` CAI Qian [this message]
2010-08-29 11:52 ` Tejun Heo
2010-08-29 12:03 ` CAI Qian
2010-08-29 12:36 ` Tejun Heo
2010-08-30 3:42 ` CAI Qian
2010-08-30 8:29 ` Tejun Heo
2010-08-30 10:24 ` CAI Qian
2010-08-30 12:50 ` Tejun Heo
2010-08-30 14:02 ` CAI Qian
2010-08-30 14:21 ` Tejun Heo
2010-08-30 14:47 ` CAI Qian
2010-08-30 14:51 ` CAI Qian
2010-08-30 14:55 ` Tejun Heo
[not found] <71887879.1606161283215975799.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-31 0:53 ` caiqian
2010-08-31 9:22 ` Tejun Heo
[not found] <373987879.1541191283181021800.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-30 15:10 ` caiqian
2010-08-30 16:38 ` Tejun Heo
2010-08-30 17:31 ` Tejun Heo
[not found] <2142316909.1477341283065016062.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-29 7:01 ` caiqian
2010-08-29 8:57 ` Tejun Heo
2010-08-29 11:24 ` CAI Qian
2010-08-29 11:21 ` Tejun Heo
[not found] <229468156.1475641283020469212.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-28 18:36 ` caiqian
[not found] <2082161789.1474781283008521258.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-28 15:19 ` caiqian
2010-08-27 12:35 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=1236896997.1479691283083005518.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com \
--to=caiqian@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome