From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <001e01c2b0eb$f756a8d0$78b5fc3e@swlocal>
From: "Steve Simon" <steve.simon@ntlworld.com>
To: <9fans@cse.psu.edu>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_001B_01C2B0EB.F6438B20"
Subject: [9fans] aha1542 -> kernel panic
Date: Tue, 31 Dec 2002 16:45:01 +0000
Topicbox-Message-UUID: 3a389538-eacb-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.

------=_NextPart_000_001B_01C2B0EB.F6438B20
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hi,

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

I have an ata disk but this is for swap.

I am booting 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
   <stack dump...>

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 is setup for its default configuration from the adaptec manual
(apart from the BIOS and floppy being disabled, and the DMA
speed of 8MB/s) IE port=0x330 dma=5 irq=11.

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?

ioalloc and irqalloc attached - BTW I get an error when I cat'ed
these devices: qlock 80186a14 nlocks 1. Dont know if this is relevant.
also the ports reported in /dev/sdstat don't tally with those in
/dev/ioalloc...

-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.
  */





------=_NextPart_000_001B_01C2B0EB.F6438B20
Content-Type: application/octet-stream;
	name="ioalloc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="ioalloc"

       0        f dma         =0A=
      20       21 i8259.0     =0A=
      40       43 i8253       =0A=
      60       60 kbd         =0A=
      61       61 i8253.cntr2c=0A=
      64       64 kbd         =0A=
      70       71 rtc/nvr     =0A=
      80       8f dma         =0A=
      a0       a1 i8259.1     =0A=
      d0       df dma         =0A=
     1f0      1f7 atacmd      =0A=
     2b0      2df vga         =0A=
     300      30f tcm509isa   =0A=
     3c0      3da vga         =0A=
     3f0      3f5 floppy      =0A=
     3f6      3f6 atactl      =0A=
     3f7      3f7 floppy      =0A=

------=_NextPart_000_001B_01C2B0EB.F6438B20
Content-Type: application/octet-stream;
	name="irqalloc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="irqalloc"

          3           0 debugpt=0A=
          7           0 mathemu=0A=
          9           0 mathover=0A=
         14           0 fault386=0A=
         16           0 matherror=0A=
         32           0 clock=0A=
         33           1 kbd=0A=
         35           3 COM2=0A=
         38           6 floppy=0A=
         42          10 ether0=0A=
         46          14 sdC (ata)=0A=

------=_NextPart_000_001B_01C2B0EB.F6438B20
Content-Type: application/octet-stream;
	name="sdatat"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="sdatat"

sdC ata port 1F0 ctl 3F4 irq 14=0A=

------=_NextPart_000_001B_01C2B0EB.F6438B20--