From: "Richard Mortimer" <richm@oldelvet.org.uk>
To: sparclinux@vger.kernel.org
Subject: RE: IRQ routing(?) problem on Enterprise 450 with Areca SATA RAID controller
Date: Tue, 23 Jan 2007 14:18:07 +0000 [thread overview]
Message-ID: <004001c73ef9$548bb7d0$c505a8c0@Jive> (raw)
In-Reply-To: <20070102140325.GB11095@wopr.homeunix.org>
Hi,
> -----Original Message-----
> From: sparclinux-owner@vger.kernel.org
> [mailto:sparclinux-owner@vger.kernel.org] On Behalf Of David Johnson
> Sent: 23 January 2007 13:54
> To: sparclinux@vger.kernel.org
> Subject: Re: IRQ routing(?) problem on Enterprise 450 with
> Areca SATA RAID controller
>
> On Thursday 18 January 2007 20:40, you wrote:
> I suspect the breakage is in 2.6.18-rc1, but there seems to
> be a critical bug
> in this kernel which prevents it from even booting on E450
> (it gets as far
> as 'Booting the kernel' and just sits there, giving no errors
> or other
> output) so I can't test this. As a result, I am unable to
> bisect the tree to
> find the patch that introduced the bug...
>
Is there any chance that you could boot with the -p flag. That
directs early kernel startup output via Openboot and will likely
give an indication as to what the problem is.
Note I did find some issues with 2.6.18 relating to the changes to
reading information from OBP. You may be seeing something similar.
Richard
prev parent reply other threads:[~2007-01-23 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 14:03 IRQ routing(?) problem on Enterprise 450 with Areca SATA RAID controller Eki
2007-01-18 20:40 ` Eki
2007-01-18 21:21 ` IRQ routing(?) problem on Enterprise 450 with Areca SATA RAID Daniel Smolik
2007-01-22 10:09 ` IRQ routing(?) problem on Enterprise 450 with Areca SATA RAID controller David Johnson
2007-01-23 13:54 ` David Johnson
2007-01-23 14:18 ` Richard Mortimer [this message]
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='004001c73ef9$548bb7d0$c505a8c0@Jive' \
--to=richm@oldelvet.org.uk \
--cc=sparclinux@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.