9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve.simon@ntlworld.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] aha1542 -> kernel panic
Date: Tue, 31 Dec 2002 16:45:01 +0000	[thread overview]
Message-ID: <001e01c2b0eb$f756a8d0$78b5fc3e@swlocal> (raw)

[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]

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





[-- Attachment #2: ioalloc --]
[-- Type: application/octet-stream, Size: 544 bytes --]

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

[-- Attachment #3: irqalloc --]
[-- Type: application/octet-stream, Size: 358 bytes --]

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

[-- Attachment #4: sdatat --]
[-- Type: application/octet-stream, Size: 33 bytes --]

sdC ata port 1F0 ctl 3F4 irq 14

             reply	other threads:[~2002-12-31 16:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-31 16:45 Steve Simon [this message]
2002-12-31 16:57 ` Russ Cox
2002-12-31 16:58 ` jmk
2003-01-01 11:15 ` Richard Miller
2003-01-01 14:25   ` David Presotto

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='001e01c2b0eb$f756a8d0$78b5fc3e@swlocal' \
    --to=steve.simon@ntlworld.com \
    --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).