All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Maxim Uvarov <muvarov@gmail.com>,
	Neil Horman <nhorman@redhat.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: kdump broken on 2.6.37-rc4
Date: Tue, 07 Dec 2010 11:24:46 -0800	[thread overview]
Message-ID: <4CFE89FE.1090901@kernel.org> (raw)
In-Reply-To: <20101207105053.GA2803@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]

On 12/07/2010 02:50 AM, Stanislaw Gruszka wrote:
> On Fri, Dec 03, 2010 at 12:54:01PM -0500, Neil Horman wrote:
>> On Fri, Dec 03, 2010 at 06:11:48PM +0100, Stanislaw Gruszka wrote:
>>> On Fri, Dec 03, 2010 at 06:46:09PM +0300, Maxim Uvarov wrote:
>>>> 2010/12/3 Stanislaw Gruszka <sgruszka@redhat.com>:
>>>>> On my T-60 laptop, i686 system with 2.6.37-rc4 kernel,
>>>>> "echo c > /proc/sysrq-trigger" just hung the system. Kdump
>>>>> works on 2.6.36. Is this known issue? If not, what info
>>>>> I should provide to solve it (I think the easiest way
>>>>> to solve the problem would be bisect) ?
>>>>>
>>>>> Stanislaw
>>>>>
>>>>
>>>> I tested x86 QEMU yesterday with the latest git. It worked.
>>>> Might be something target specific.., What does console print?
>>>
>>> Here is the photo 
>>> http://people.redhat.com/sgruszka/20101203_005.jpg
>>>
>>> There are two BUGs, first "sleeping function called from invalid
>>> context" and then "unable to handle null pointer dereference".
>>>
>> The warning about sleeping is an artifact of the fact that we panic the box with
>> irqs disabled I think (although I would think the fault handler would have
>> re-enabled them properly).  Not sure what the NULL pointer is from
> 
> NULL pointer dereferece is ok, that's the way sysrq_handle_crash
> trigger a crash. Problem here is that secondary kdump kernel hung at
> start.
> 
> Bisection shows that bad commit is
> 
> commit 72d7c3b33c980843e756681fb4867dc1efd62a76
> Author: Yinghai Lu <yinghai@kernel.org>
> Date:   Wed Aug 25 13:39:17 2010 -0700

please check debug patches, and boot first kernel and kexec second kernel with "ignore_loglevel debug earlyprintk...."

Thanks

	Yinghai

[-- Attachment #2: mb_debug.patches.tar.bz2 --]
[-- Type: application/x-bzip, Size: 11774 bytes --]

[-- Attachment #3: Type: text/plain, Size: 143 bytes --]

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

WARNING: multiple messages have this Message-ID (diff)
From: Yinghai Lu <yinghai@kernel.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Maxim Uvarov <muvarov@gmail.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	Neil Horman <nhorman@redhat.com>
Subject: Re: kdump broken on 2.6.37-rc4
Date: Tue, 07 Dec 2010 11:24:46 -0800	[thread overview]
Message-ID: <4CFE89FE.1090901@kernel.org> (raw)
In-Reply-To: <20101207105053.GA2803@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]

On 12/07/2010 02:50 AM, Stanislaw Gruszka wrote:
> On Fri, Dec 03, 2010 at 12:54:01PM -0500, Neil Horman wrote:
>> On Fri, Dec 03, 2010 at 06:11:48PM +0100, Stanislaw Gruszka wrote:
>>> On Fri, Dec 03, 2010 at 06:46:09PM +0300, Maxim Uvarov wrote:
>>>> 2010/12/3 Stanislaw Gruszka <sgruszka@redhat.com>:
>>>>> On my T-60 laptop, i686 system with 2.6.37-rc4 kernel,
>>>>> "echo c > /proc/sysrq-trigger" just hung the system. Kdump
>>>>> works on 2.6.36. Is this known issue? If not, what info
>>>>> I should provide to solve it (I think the easiest way
>>>>> to solve the problem would be bisect) ?
>>>>>
>>>>> Stanislaw
>>>>>
>>>>
>>>> I tested x86 QEMU yesterday with the latest git. It worked.
>>>> Might be something target specific.., What does console print?
>>>
>>> Here is the photo 
>>> http://people.redhat.com/sgruszka/20101203_005.jpg
>>>
>>> There are two BUGs, first "sleeping function called from invalid
>>> context" and then "unable to handle null pointer dereference".
>>>
>> The warning about sleeping is an artifact of the fact that we panic the box with
>> irqs disabled I think (although I would think the fault handler would have
>> re-enabled them properly).  Not sure what the NULL pointer is from
> 
> NULL pointer dereferece is ok, that's the way sysrq_handle_crash
> trigger a crash. Problem here is that secondary kdump kernel hung at
> start.
> 
> Bisection shows that bad commit is
> 
> commit 72d7c3b33c980843e756681fb4867dc1efd62a76
> Author: Yinghai Lu <yinghai@kernel.org>
> Date:   Wed Aug 25 13:39:17 2010 -0700

please check debug patches, and boot first kernel and kexec second kernel with "ignore_loglevel debug earlyprintk...."

Thanks

	Yinghai

[-- Attachment #2: mb_debug.patches.tar.bz2 --]
[-- Type: application/x-bzip, Size: 11774 bytes --]

  reply	other threads:[~2010-12-07 19:28 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 11:16 kdump broken on 2.6.37-rc4 Stanislaw Gruszka
2010-12-03 11:16 ` Stanislaw Gruszka
2010-12-03 15:46 ` Maxim Uvarov
2010-12-03 15:46   ` Maxim Uvarov
2010-12-03 17:11   ` Stanislaw Gruszka
2010-12-03 17:11     ` Stanislaw Gruszka
2010-12-03 17:54     ` Neil Horman
2010-12-03 17:54       ` Neil Horman
2010-12-07 10:50       ` Stanislaw Gruszka
2010-12-07 10:50         ` Stanislaw Gruszka
2010-12-07 19:24         ` Yinghai Lu [this message]
2010-12-07 19:24           ` Yinghai Lu
2010-12-08 14:19           ` Stanislaw Gruszka
2010-12-08 14:19             ` Stanislaw Gruszka
2010-12-09  7:16             ` Yinghai Lu
2010-12-09  7:16               ` Yinghai Lu
2010-12-09 12:41               ` Stanislaw Gruszka
2010-12-09 12:41                 ` Stanislaw Gruszka
2010-12-09 20:09                 ` Yinghai Lu
2010-12-09 20:09                   ` Yinghai Lu
2010-12-13 10:08                   ` Stanislaw Gruszka
2010-12-13 10:08                     ` Stanislaw Gruszka
2010-12-13 18:20                     ` Yinghai Lu
2010-12-13 19:47                       ` H. Peter Anvin
2010-12-14 22:41                         ` Vivek Goyal
2010-12-15 10:39                           ` Stanislaw Gruszka
2010-12-15 22:41                             ` Yinghai Lu
2010-12-16  4:29                             ` Yinghai Lu
2010-12-16 10:00                               ` Stanislaw Gruszka
2010-12-16 16:16                                 ` H. Peter Anvin
2010-12-16 16:22                                   ` Vivek Goyal
2010-12-16 16:53                                     ` H. Peter Anvin
2010-12-18 21:50                                 ` Yinghai Lu
2010-12-16 14:39                               ` Vivek Goyal
2010-12-16 16:28                                 ` H. Peter Anvin
2010-12-16 17:28                                   ` Yinghai Lu
2010-12-16 19:58                                     ` H. Peter Anvin
2010-12-16 22:57                                       ` Yinghai Lu
2010-12-16 23:30                                       ` Yinghai Lu
2010-12-16 23:49                                         ` Yinghai Lu
2010-12-17  0:39                                           ` Yinghai Lu
2010-12-17  1:06                                             ` H. Peter Anvin
2010-12-17  1:21                                             ` H. Peter Anvin
2010-12-17  1:51                                             ` H. Peter Anvin
2010-12-17  3:05                                               ` Yinghai Lu
2010-12-17  3:07                                               ` Yinghai Lu
2010-12-17  3:19                                                 ` [tip:x86/urgent] x86-32: Make sure we can map all of lowmem if we need to tip-bot for H. Peter Anvin
2010-12-17 14:33                                                   ` Stanislaw Gruszka
2010-12-16 22:01                                     ` kdump broken on 2.6.37-rc4 Vivek Goyal
2010-12-16 22:58                                       ` Yinghai Lu
2010-12-17 16:15                                         ` Vivek Goyal
2010-12-17  1:15                                       ` H. Peter Anvin
2010-12-17  3:31                               ` H. Peter Anvin
2010-12-17  3:58                                 ` Yinghai
2010-12-17  4:08                                   ` H. Peter Anvin
2010-12-17  4:46                                     ` Yinghai Lu
2010-12-17  5:16                                       ` H. Peter Anvin
2010-12-17 17:01                                   ` Vivek Goyal
2010-12-17 17:56                                     ` H. Peter Anvin
2010-12-17 18:02                                       ` Vivek Goyal
2010-12-17 18:21                                         ` Yinghai Lu
2010-12-17 18:35                                           ` Vivek Goyal
2010-12-17 19:39                                           ` H. Peter Anvin
2010-12-17 19:46                                             ` Yinghai Lu
2010-12-17 19:50                                               ` Vivek Goyal
2010-12-17 19:52                                                 ` Yinghai Lu
2010-12-17 20:01                                                   ` Vivek Goyal
2010-12-17 20:06                                                     ` Yinghai Lu
2010-12-17 20:34                                                       ` Vivek Goyal
2010-12-17 23:51                                                         ` Vivek Goyal
2010-12-17 19:56                                                 ` H. Peter Anvin
2010-12-17 20:11                                                   ` Vivek Goyal
2010-12-17 20:59                                                     ` H. Peter Anvin
2010-12-17 21:13                                                       ` Vivek Goyal
2010-12-20 16:31                                                   ` Stanislaw Gruszka
2010-12-18  4:34                                                 ` [tip:x86/urgent] x86, kexec: Limit the crashkernel address appropriately tip-bot for H. Peter Anvin
2010-12-17 19:50                                               ` kdump broken on 2.6.37-rc4 H. Peter Anvin
2010-12-13 10:25                   ` Américo Wang
2010-12-13 10:25                     ` Américo Wang
2010-12-05 14:35 ` Maciej Rutecki
2010-12-05 14:35   ` Maciej Rutecki

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=4CFE89FE.1090901@kernel.org \
    --to=yinghai@kernel.org \
    --cc=hpa@zytor.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muvarov@gmail.com \
    --cc=nhorman@redhat.com \
    --cc=sgruszka@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.