[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101203175401.GE28603@hmsreliant.think-freely.org>
Date: Fri, 3 Dec 2010 12:54:01 -0500
From: Neil Horman <nhorman@...hat.com>
To: Stanislaw Gruszka <sgruszka@...hat.com>
Cc: Maxim Uvarov <muvarov@...il.com>, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: kdump broken on 2.6.37-rc4
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@...hat.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
Neil
> Stanislaw
>
> _______________________________________________
> kexec mailing list
> kexec@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists