9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve Simon <nospam@nospam.org>
To: 9fans@cse.psu.edu
Subject: [9fans] adaptec 1542 -> kernel panic on boot
Date: Thu,  2 Jan 2003 10:16:01 +0000	[thread overview]
Message-ID: <VHiQ9.690$hu4.112076@newsfep1-win.server.ntli.net> (raw)

Hi,

I tried to add an Adaptec 1542B to a pc I hope to
use as a cpu server (for DAT and CDROM support)
and I get a panic (This is a dual Pentium Pro machine,
though I still have *nomp=1).

I am booting at present using just the current
installation floppy - but I guess it must have an
aha1542 driver as its doing somthing!

Without the scsi0=aha1542 port=0x330 in plan9.ini
the machine boots fine.

The error I get is:
panic: what ? up is zero pc 0x801a413d
ktrace /kernel/path 80106720 800005c50

I cannot see this error in ther kernel though there is
somthing similar in trap.c - maybe the error message
is getting overwritten by somthing else?

The card set for its default configuration (apart from
the BIOS and floppy being disabled).

Looking at the source (below) I wonder if the interrupt structure
has changed a bit since this code was written and the kernel
is more strict about stray interrupts than it used to be?

This is purely a guess. anyone any other / more concrete ideas?

-Steve

sdmylex.c:
/*
  * Get the id, DMA and IRQ info from the board. This will
  * cause an interrupt which will hopefully not cause any
  * trouble because the interrupt number isn't known yet.
  * This is necessary as the DMA won't be set up if the
  * board has the BIOS disabled.
  *
  * If the IRQ is already known, this must be a 32-bit PCI
  * or EISA card, in which case the returned DMA and IRQ can
  * be ignored.
  */


                 reply	other threads:[~2003-01-02 10:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='VHiQ9.690$hu4.112076@newsfep1-win.server.ntli.net' \
    --to=nospam@nospam.org \
    --cc=9fans@cse.psu.edu \
    /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).