From: Grant Grundler <grundler@cup.hp.com>
To: yuqian <yuqian@huawei.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] bug report on Sym53C895a or config error?
Date: Thu, 05 Oct 2000 09:40:46 -0700 [thread overview]
Message-ID: <200010051640.JAA04424@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "05 Oct 2000 12:13:46 PDT." <20001005121346.23782.qmail@mailserv2.iuinc.com>
yuqian wrote:
> For xc not available yet, I download Image-testcpu(2000-10-02)
> as my net-boot kernel, my HP box is HP B2000 (9000/785) with
> NCR53C8x SCSI card.
The B2000 isn't really supported yet. The piece that's missing
support is the SuckyIO (superio from NCR) chip. SuckyIO provides
USB, IDE, Floppy, Serial port, etc.
I'm using an add-on serial card as my "console" in a C3000.
The built-in Serial port 1 provides output until linux switches
from PDC console to serial console.
Once SuckyIO support is in place, the add-on serial card won't
be needed.
...
> BTW: Is xc not available for HP-UX 10.20 yet?
No one has taken ownership of HPUX XC builds since building
on i686-linux is pretty fast. Did I hear you volunteer? :^)
You can try building an HPUX XC with the following script
after downloading the appropriate sources (either from CVS
or nightly snapshots via ftp):
http://puffin.external.hp.com/cgi-bin/cvsview/build-tools/recipe.hpux
> (When I type 'configure --target hppa-linux' for glibc, it told me this
> is not supported yet.)
You don't need xc-glibc to build kernels - only userspace apps.
The XC resulting from recipe.hpux is only suitable for building
parisc-linux kernels.
> And: How can I get more information (like instruction, registers value ...)
> for bug report?
Add calls to show_reg() in the code path that crashes.
We should get register dumps with most dumps and I thought with
panics as well.
> Kernel panic: sba_iommu.c:sba_alloc_range() I/O MMU is out of mapping resources
The problem here is the same one Ryan Bradetich (and others) ran into.
Basically the I/O Pdir mapping resource is poorly utilized (though
not as bad as it originally was). Much of the I/O Pdir is "wasted"
due to the way it's managed.
I'll add some more debug code in this particular panic path.
BTW, can someone look at why the panic didn't halt the machine and
provide a register dump?
thanks,
grant
Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253
next prev parent reply other threads:[~2000-10-05 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-05 12:13 [parisc-linux] bug report on Sym53C895a or config error? yuqian
2000-10-05 16:40 ` Grant Grundler [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-06 1:45 yuqian
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=200010051640.JAA04424@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=yuqian@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox