All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Sjoerd Simons <sjoerd@luon.net>, linux-parisc@vger.kernel.org
Subject: Re: kernel fault when booting with dual link network card
Date: Sun, 29 Jun 2008 10:22:21 -0600	[thread overview]
Message-ID: <20080629162220.GL14894@parisc-linux.org> (raw)
In-Reply-To: <1214755234.3405.5.camel@localhost.localdomain>

On Sun, Jun 29, 2008 at 11:00:34AM -0500, James Bottomley wrote:
> On Sun, 2008-06-29 at 16:17 +0100, Sjoerd Simons wrote:
> > Hi,
> > 
> >   Kernel 2.6.24 causes the machine to fault when a dual-link network card is
> >   installed right after loading the tulip module. Output of SER PIM attached.
> 
> I'm afraid just the hex dump isn't really any use.  To be possibly
> useful, we need at least the symbolic addresses of IAOQ and %r2.
> That's:
> 
> %r2: 0x10245748
> IAOQ[0]: 0x10252bdc
> IAOQ[1]: 0x10252be0
> 
> the I/O module error seems to indicate an incorrect GSC DMA read.

I don't think it's going to tell us anything useful.  I believe that
we've not set up the cardmode Dino correctly to respond to iomem space
and as a result the first access to iomem space will fault.

Of course, this is a machine with CCIO, so it could be something going
wrong with the CCIO programming too.  But I think it's Dino.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2008-06-29 16:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-29 15:17 kernel fault when booting with dual link network card Sjoerd Simons
2008-06-29 16:00 ` James Bottomley
2008-06-29 16:22   ` Matthew Wilcox [this message]
2008-06-29 17:54     ` Joel Soete
2008-06-29 17:57       ` Sjoerd Simons
2008-06-29 18:11         ` Joel Soete
2008-06-29 18:38           ` Sjoerd Simons
2008-06-29 21:11     ` Grant Grundler
2008-06-29 21:05 ` Grant Grundler

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=20080629162220.GL14894@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-parisc@vger.kernel.org \
    --cc=sjoerd@luon.net \
    /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.