All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Bradetich <rbradetich@uswest.net>
To: Erik Paulson <epaulson@upl.cs.wisc.edu>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] C100 and ccio-dma
Date: Thu, 21 Sep 2000 20:44:10 -0600	[thread overview]
Message-ID: <39CAC77A.8761CD51@uswest.net> (raw)
In-Reply-To: 20000921201241.C28365@data.upl.cs.wisc.edu

Erik,

I also have that problem on the C200+, but it isn't a ccio-dma.c problem
(atleast I don't think it is) ... I believe it is a sym53cxx driver problem.  I
have already started tracking this down, and hopefully will have time to
find and squash the bug this weekend.

hope this helps!

Ryan

Erik Paulson wrote:

> Hi,
>         Using the CVS kernel on a C100 I'm seeing it die with an out-of-mapping
> resources error from ccio-dma.c. It looks like there's been some active
> development there about a week ago, but it's not helping my machine. The
> quickest way for me to bring it about is to try and use mke2fs, but just
> mounting the CD and running a few commands will oftentimes do the trick.
>
> How can I help debug this? There's really no useful information provided by
> the printk now - is there some sort of debugging info I could be collecting,
> or would a backtrace help?
>
> Thanks
>
> -Erik
>
> ---------------------------------------------------------------------------
> To unsubscribe: send e-mail to parisc-linux-request@thepuffingroup.com with
> `unsubscribe' as the subject.

  reply	other threads:[~2000-09-22  2:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-22  1:12 [parisc-linux] C100 and ccio-dma Erik Paulson
2000-09-22  2:44 ` Ryan Bradetich [this message]
2000-09-22 21:31   ` Grant Grundler
2000-09-22 22:49     ` Grant Grundler
2000-09-23  5:30 ` Ryan Bradetich
2000-09-25  2:40   ` Ryan Bradetich

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=39CAC77A.8761CD51@uswest.net \
    --to=rbradetich@uswest.net \
    --cc=epaulson@upl.cs.wisc.edu \
    --cc=parisc-linux@thepuffingroup.com \
    /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.