From: Lawrence MacIntyre <lpz@ornl.gov>
To: linux-scsi@vger.kernel.org
Subject: Adaptec 200S on kernel > 2.4.21 won't boot
Date: Tue, 25 Nov 2003 17:21:08 -0500 [thread overview]
Message-ID: <1069798868.2790.218.camel@nautique> (raw)
[-- Attachment #1: Type: text/plain, Size: 3546 bytes --]
Hi:
I have a dual Xeon with an Adaptec 200S zero-channel raid controller
running the 2.4.21 kernel. I want to try a patch that requires
2.4.23-rc-1. However, when I build the kernel, it won't boot. I simply
took the .config from the 2.4.21 kernel and ran make oldconfig. I have
tried this with 2.4.22 unpatched and patched to 2.4.23-rc1. When the
2.4.21 machine boots, I get these messages:
SvrWks CSB5: IDE controller at PCI slot 00:0f.1
SvrWks CSB5: chipset revision 147
SvrWks CSB5: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
hda: CDU5211, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: attached ide-cdrom driver.
hda: ATAPI 52X CD-ROM drive, 120kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
SCSI subsystem driver Revision: 1.00
Loading Adaptec I2O RAID: Version 2.4 Build 5
Detecting Adaptec I2O RAID controllers...
Adaptec I2O RAID controller 0 irq=18
BAR0 f881b000 - size= 100000
BAR1 f891c000 - size= 1000000
dpti: If you have a lot of devices this could take a few minutes.
dpti0: Reading the hardware resource table.
TID 008 Vendor: ADAPTEC Device: AIC-7899 Rev: 00000001
TID 009 Vendor: ADAPTEC Device: AIC-7899 Rev: 00000001
TID 517 Vendor: ADAPTEC R Device: RAID-1 Rev: 380ED
scsi0 : Vendor: Adaptec Model: 2000S FW:380E
Vendor: ADAPTEC Model: RAID-1 Rev: 380E
Type: Direct-Access ANSI SCSI revision: 02
Red Hat/Adaptec aacraid driver, Jul 15 2003
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 71686144 512-byte hdwr sectors (36703 MB)
Partition check:
sda: sda1 sda2 sda3
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
host/uhci.c: USB Universal Host Controller Interface driver v1.1
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
I2O Core - (C) Copyright 1999 Red Hat Software
I2O: Event thread created as pid 13
Linux I2O PCI support (c) 1999 Red Hat Software.
i2o: Checking for PCI I2O controllers...
I2O configuration manager v 0.04.
(C) Copyright 1999 Red Hat Software
I2O Block Storage OSM v0.9
(c) Copyright 1999-2001 Red Hat Software.
i2o_block: Checking for Boot device...
i2o_block: Checking for I2O Block devices...
I2O LAN OSM (C) 1999 University of Helsinki.
i2o_scsi.c: Version 0.0.1
chain_pool: 0 bytes @ f7c46f40
(512 byte buffers X 4 can_queue X 0 i2o controllers)
However, when the non-working kernels boot, this happens before the
loading Adaptec I2O Raid message (this message never appears).
kmod: failed to exec /sbin/modprobe -s -k block-major-8 errno=2
VFS: Cannot open root device "sda2" or 08:02
Please append a correct "root=" boot option
kernel panic: VFS: Unable to mount root fs on 08:02
The following options are enabled:
Adaptec AACRAID support
Adaptec AIC79xx support
Adaptec I2O Raid support
I2O support
I2O PCI support
I2O Block support
I2O LAN support
I2O SCSI support
I2O /proc support
I have tried this with the support in the kernel and as modules. The
same thing happens each time. Is there something I have done wrong or
is this broken?
--
Lawrence MacIntyre 865.574.8696 lpz@ornl.gov
Oak Ridge National Laboratory
High Performance Information Infrastructure Technology Group
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-11-25 22:21 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=1069798868.2790.218.camel@nautique \
--to=lpz@ornl.gov \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.