From: "David C. Rankin" <drankinatty@suddenlinkmail.com>
To: kernel <linux-kernel@vger.kernel.org>
Subject: Re: Upgrade to recent 2.6.35 & 2.6.36 kernel causing boot failure with nv dmraid
Date: Fri, 05 Nov 2010 04:59:24 -0500 [thread overview]
Message-ID: <4CD3D57C.2000002@suddenlinkmail.com> (raw)
In-Reply-To: <4CD24A64.3080503@suddenlinkmail.com>
On 11/04/2010 12:53 AM, David C. Rankin wrote:
<big snip>
> something got broke with the way the kernel inits the dmraid arrays resulting in
> grub thinking it is reading beyond some partition boundary or a corrupt
> partition table. Neither are correct, because simply booting an older kernel
> works fine.
Anybody have even a guess on this one? I guarantee you, your guess will be much
appreciated. (see the original post for details) Thanks.
Also, if this post isn't appropriate for the list, I apologize. I was referred
here by the Arch Linux devs to see if I could find out what may be causing the
boot failures.
As always, any help is much appreciated.
--
David C. Rankin, J.D.,P.E.
next prev parent reply other threads:[~2010-11-05 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 5:53 Upgrade to recent 2.6.35 & 2.6.36 kernel causing boot failure with nv dmraid David C. Rankin
2010-11-04 6:12 ` David C. Rankin
2010-11-05 9:59 ` David C. Rankin [this message]
2010-11-09 17:48 ` David C. Rankin
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=4CD3D57C.2000002@suddenlinkmail.com \
--to=drankinatty@suddenlinkmail.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 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.