From: "Paweł Zuzelski" <pawelz@pld-linux.org>
To: James Dingwall <james.dingwall@amdocs.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: Re: PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot
Date: Thu, 23 Sep 2010 19:53:50 +0200 [thread overview]
Message-ID: <20100923175350.GA4737@davabel.xatka.net> (raw)
In-Reply-To: <3B7AEC3C7FCC864282DFAC9A56A7BA363D81475787@UKLNDMAIL1.corp.amdocs.com>
On Thu, 23 Sep 2010, James Dingwall wrote:
> > I was experiencing the same immediate crash with a null pointer
> > dereference (log below) on boot with 2.6.35.5. Reverting
> > fb412a178502dc498430723b082a932f797e4763 also resolved the problem for
> > me.
>
> Checking the diff from this commit it looks like there is a typo in the patch. With the following (probably mangled by my client) I get 2.6.35.5 to boot. Suggest it should be a candidate for .32 and .35 stable trees.
I confirm. This patch works for me. Thanks.
--
Regards,
Paweł Zuzelski
next prev parent reply other threads:[~2010-09-23 18:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 15:23 James Dingwall
2010-09-23 17:53 ` Paweł Zuzelski [this message]
2010-09-24 18:00 ` Jeremy Fitzhardinge
2010-09-27 2:40 ` Kyle McMartin
2010-09-27 6:13 ` [stable] " Greg KH
2010-09-27 6:34 ` Kyle McMartin
2010-09-27 8:37 ` [stable] PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot [PATCH] James Dingwall
2010-09-28 18:29 ` Greg KH
2010-09-27 18:08 ` [stable] PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot Jeremy Fitzhardinge
2010-09-28 18:29 ` Greg KH
2010-09-29 15:48 ` Jeremy Fitzhardinge
2010-09-30 0:06 ` Greg KH
2010-10-01 16:46 ` Jeremy Fitzhardinge
2010-10-01 18:26 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-09-23 10:04 James Dingwall
2010-09-21 19:05 Paweł Zuzelski
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=20100923175350.GA4737@davabel.xatka.net \
--to=pawelz@pld-linux.org \
--cc=james.dingwall@amdocs.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®