public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Lidel <Markus.Lidel@shadowconnect.com>
To: joshuam@gravityedge.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: Repeatable Kernel Panic on Adaptec 2015S I20 device on bootup
Date: Mon, 25 Jul 2005 23:17:19 +0200	[thread overview]
Message-ID: <42E556DF.2010406@shadowconnect.com> (raw)
In-Reply-To: <1671.206.173.47.7.1122320965.squirrel@mail.gravityedge.com>

Hello,

joshuam@gravityedge.com wrote:
> 1. Repeatable Kernel Panic on Adaptec 2015S I20 device on bootup
> 2. I can get this to panic on every bootup, I have included the Kernel
> boot output below.
> 3. Linux SCSI panic Adaptec 2015 bootup
> 4. Kernel version: 2.6.12.3
> 5. Kernel Output/Oops
> Linux version 2.6.12.3 (root@graviton.krk0) (gcc version 3.3.5 (Debian
> 1:3.3.5-
> )) #2 SMP Fri Jul 22 14:52:48 PDT 2005
> [...]
> Loading Adaptec I2O RAID: Version 2.4 Build 5go
> Detecting Adaptec I2O RAID controllers...
> Adaptec I2O RAID controller 0 irq=30
>      BAR0 e0900000 -
>      BAR1 e0a80000 - size= 1000000
> dpti: If you have a lot of devices this could take a few minutes.
> dpti0: Reading the hardware resource table.

here the dpt_i2o driver is loaded...

> TID 008  Vendor: ADAPTEC      Device: AIC-7902     Rev: 00000001
> TID 009  Vendor: ADAPTEC      Device: AIC-7902     Rev: 00000001
> TID 513  Vendor: SUPER   G    Device: GEM318       Rev: 0   0
> scsi0 : Vendor: Adaptec  Model: 2015S            FW:3B0A
>   Vendor: SUPER     Model: GEM318            Rev: 0
>   Type:   Processor                          ANSI SCSI revision: 02
> megaraid cmm: 2.20.2.5 (Release Date: Fri Jan 21 00:01:03 EST 2005)
> megaraid: 2.20.4.5 (Release Date: Thu Feb 03 12:27:22 EST 2005)
> 3ware Storage Controller device driver for Linux v1.26.02.001.
> 3ware 9000 Storage Controller device driver for Linux v2.26.02.002.
> Attached scsi generic sg0 at scsi0, channel 0, id 6, lun 0,  type 3
> I2O subsystem v$Rev$

and here the I2O subsystem...

> i2o: max drivers = 8
> i2o: Checking for PCI I2O controllers...
> i2o: I2O controller found on bus 3 at 24.
> iop0: PCI I2O controller
>      BAR0 at 0xF8300000 size=1048576
>      BAR1 at 0xFB000000 size=16777216
> iop0: using write combining MTRR
> iop0: Installed at IRQ 30
> iop0: Activating I2O controller...
> iop0: This may take a few minutes if there are many devices
> Unable to handle kernel paging request at virtual address 8000002c
 > [...]

The problem is caused, because two different drivers for the same device 
are loaded at the same time. You have to remove either the I2O subsystem 
or the dpt_i2o driver, both at the same time won't work...



Best regards,


Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)

Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany

Phone:  +49 82 82/99 51-0
Fax:    +49 82 82/99 51-11

E-Mail: Markus.Lidel@shadowconnect.com
URL:    http://www.shadowconnect.com

      reply	other threads:[~2005-07-25 21:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25 19:49 Repeatable Kernel Panic on Adaptec 2015S I20 device on bootup joshuam
2005-07-25 21:17 ` Markus Lidel [this message]

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=42E556DF.2010406@shadowconnect.com \
    --to=markus.lidel@shadowconnect.com \
    --cc=joshuam@gravityedge.com \
    --cc=linux-scsi@vger.kernel.org \
    /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