All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Grant Grundler <grundler@parisc-linux.org>,
	PA-RISC Linux Port <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] 2.6.5-rc2-pa2 boot panic on c110 :(
Date: Fri, 09 Apr 2004 20:47:27 +0000	[thread overview]
Message-ID: <40770BDF.10209@tiscali.be> (raw)
In-Reply-To: <20040323045151.GA6190@colo.lackof.org>

Hi James,

I come back to you with your ccio-dma patch because I don't undertand this part:
[snip]
#ifdef CONFIG_PROC_FS
/*
  * CCIO_SEARCH_TIME can help measure how fast the bitmap search is.
  * impacts performance though - ditch it if you don't use it.
  */
#define CCIO_SEARCH_TIME
#undef CCIO_MAP_STATS
#else
#undef CCIO_SEARCH_TIME
#undef CCIO_MAP_STATS
#endif

CCIO_MAP_STATS is always undef?

Could it be the panic reason of my c110 (_apparently_ since this patch)?

Thanks in advance for your attention,
	Joel


Grant Grundler wrote:
> On Sun, Mar 21, 2004 at 12:57:16PM -0700, Grant Grundler wrote:
> 
>>>Kernel Fault: Code=26 regs=10594380 (Addr=00000000)
>>
>>null ptr deref.
>>
>>...
>>
>>> IAOQ[0]: lasi700_probe+0x18c/0x1cc
>>> IAOQ[1]: lasi700_probe+0x190/0x1cc
>>> RP(r2): lasi700_probe+0x58/0x1cc
>>
>>IOAQ[0] is the offending instruction.
> 
> 
> James Bottomley observed a problem with hppa_dma_ops
> not being set properly for his U2/Uturn box.
> This is likely the same problem.
> See ccio driver isn't claiming the chip when it should.
> 
> grant
> 

  parent reply	other threads:[~2004-04-09 20:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-21 13:17 [parisc-linux] 2.6.5-rc2-pa2 boot panic on c110 :( Joel Soete
2004-03-21 19:57 ` Grant Grundler
2004-03-22  7:07   ` Joel Soete
2004-03-23  4:51   ` Grant Grundler
2004-03-27 22:43     ` Joel Soete
2004-04-09 20:47     ` Joel Soete [this message]
2004-04-09 21:15       ` Grant Grundler
2004-04-10  8:32         ` Joel Soete
2004-04-10 18:14           ` Grant Grundler
2004-04-10 21:19             ` Joel Soete
2004-04-14  0:22               ` Ryan Bradetich
  -- strict thread matches above, loose matches on Subject: below --
2004-04-14  6:45 Joel Soete
2004-04-14 12:01 ` Joel Soete
2004-04-14 14:36 ` Ryan Bradetich
2004-04-14 14:49   ` James Bottomley
2004-04-14 16:26     ` Joel Soete
2004-04-14 16:08   ` Joel Soete
2004-04-14 19:32 Andy Walker
2004-04-14 20:52 ` Joel Soete
2004-04-15  7:05   ` Joel Soete
2004-04-16 11:19     ` Andy Walker
2004-04-17 18:10       ` Joel Soete
2004-04-17 20:49         ` Andy Walker
2004-04-17 21:32           ` Joel Soete

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=40770BDF.10209@tiscali.be \
    --to=soete.joel@tiscali.be \
    --cc=James.Bottomley@steeleye.com \
    --cc=grundler@parisc-linux.org \
    --cc=parisc-linux@lists.parisc-linux.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.