From: Ethan Weinstein <e-d0uble@stinkfoot.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: aic7xxx panics (long)
Date: Thu, 03 Jul 2003 21:01:30 -0400 [thread overview]
Message-ID: <3F04D1EA.6060906@stinkfoot.org> (raw)
In-Reply-To: <1057148769.32104.422.camel@gaston>
Ben,
Same oops with your dev tree (2.4.22-pre2-ben0). I'll post it as I did
the last one if you'd like, but it looks nearly identical. What to try
next?
Ethan
Benjamin Herrenschmidt wrote:
>
> Ok, it's real strange now. It seems you get that machine check on
> the first access to the second controller while the first works fine,
> though both appear to be configured properly on the PCI bus. It
> looks like the second controller isn't responding on the MMIO
> addresses... Can you try my devel tree with the updated driver ?
> (just in case it changes anything....) I see no reason for this
> problem right now though...
>
> Ben.
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-04 1:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 6:27 aic7xxx panics Ethan Weinstein
2003-06-30 7:11 ` Benjamin Herrenschmidt
2003-07-01 1:48 ` aic7xxx panics (long) Ethan Weinstein
2003-07-01 9:59 ` Benjamin Herrenschmidt
2003-07-02 3:37 ` Ethan Weinstein
2003-07-02 7:59 ` Ethan Benson
2003-07-02 8:39 ` Michel Dänzer
2003-07-02 9:24 ` Benjamin Herrenschmidt
2003-07-02 9:48 ` Ethan Benson
2003-07-02 12:26 ` Benjamin Herrenschmidt
2003-07-04 1:01 ` Ethan Weinstein [this message]
2003-07-07 15:04 ` Benjamin Herrenschmidt
2003-07-07 16:51 ` Ethan Weinstein
2003-07-15 14:15 ` Ethan Weinstein
2003-07-15 14:17 ` Benjamin Herrenschmidt
2003-07-15 14:26 ` Ethan Weinstein
2003-07-15 14:30 ` Benjamin Herrenschmidt
2003-07-19 22:22 ` Ethan Weinstein
2003-07-21 23:42 ` Benjamin Herrenschmidt
2003-07-22 1:11 ` Ethan Weinstein
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=3F04D1EA.6060906@stinkfoot.org \
--to=e-d0uble@stinkfoot.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).