Here is what I got on /var/log/messages
Jan 30 10:27:21 servmail kernel: Loading Adaptec I2O RAID: Version 2.4 Build 5
Jan 30 10:27:21 servmail kernel: Detecting Adaptec I2O RAID controllers...
Jan 30 10:27:39 servmail kernel: Linux I2O PCI support (c) 1999 Red Hat Software.
Jan 30 10:27:39 servmail kernel: I2O Core - (C) Copyright 1999 Red Hat Software
Jan 30 10:27:39 servmail kernel: i2o: Checking for PCI I2O controllers...
Jan 30 10:27:39 servmail kernel: i2o: I2O controller on bus 1 at 97.
Jan 30 10:27:39 servmail kernel: i2o: PCI I2O controller at 0xF8000000 size=67108864
Jan 30 10:27:39 servmail kernel: mtrr: Serverworks LE detected. Write-combining
disabled.
Jan 30 10:27:39 servmail kernel: mtrr: your processor doesn't support write-combining
Jan 30 10:27:39 servmail kernel: I2O: MTRR workaround for Intel i960 processor
Jan 30 10:27:39 servmail kernel: i2o/iop0: Installed at IRQ22
Jan 30 10:27:39 servmail kernel: i2o: 1 I2O controller found and installed.
Jan 30 10:27:39 servmail kernel: I2O: Event thread created as pid 787
Jan 30 10:27:39 servmail kernel: Activating I2O controllers...
Jan 30 10:27:39 servmail kernel: This may take a few minutes if there are many devices
Jan 30 10:28:09 servmail kernel: i2o/iop0: LCT has 17 entries.
Jan 30 10:29:25 servmail kernel: I2O configuration manager v 0.04.
Jan 30 10:29:25 servmail kernel: (C) Copyright 1999 Red Hat Software
Jan 30 10:29:36 servmail kernel: I2O Block Storage OSM v0.9
Jan 30 10:29:36 servmail kernel: (c) Copyright 1999-2001 Red Hat Software.
Jan 30 10:29:36 servmail kernel: i2o_block: registered device at major 80
Jan 30 10:29:36 servmail kernel: i2o_block: Checking for Boot device...
Jan 30 10:29:36 servmail kernel: i2o_block: Checking for I2O Block devices...
Jan 30 10:29:36 servmail kernel: i2ob: Installing tid 16 device at unit 0
Jan 30 10:29:36 servmail kernel: i2o/hda: Max segments 12, queue depth 128, byte limit 6144.
Jan 30 10:29:36 servmail kernel: i2o/hda: Type 176: 69808MB, 512 byte sectors.
Jan 30 10:29:36 servmail kernel: i2o/hda: Maximum sectors/read set to 256.
an 30 10:29:36 servmail kernel: i2o/hda: unknown partition table
Jan 30 10:33:23 servmail kernel: i2o_scsi.c: Version 0.0.1
Jan 30 10:33:23 servmail kernel: chain_pool: 2048 bytes @ f6b92800
Jan 30 10:33:23 servmail kernel: (512 byte buffers X 4 can_queue X 1 i2o controllers)
Jan 30 10:33:23 servmail kernel: scsi2 : i2o/iop0
Jan 30 10:33:23 servmail kernel: scsi3 : i2o/iop0
Jan 30 10:33:23 servmail kernel: scsi3 channel 0 : resetting for second half of retries.
Jan 30 10:33:23 servmail kernel: SCSI bus is being reset for host 3 channel 0.
Jan 30 10:33:23 servmail kernel: i2o_scsi: Attempting to reset the bus.
Jan 30 10:33:24 servmail kernel: SCSI host 3 channel 0 reset (pid 9075) timed out - trying harder
Jan 30 10:33:24 servmail kernel: SCSI bus is being reset for host 3 channel 0.
Jan 30 10:33:24 servmail kernel: i2o_scsi: Attempting to reset the bus.
Jan 30 10:36:36 servmail syslogd 1.4.1: restart.
and the server boot
And here is the Oops
CPU:1
EIP:0010:[<fcc40243>] not tained
EFLAGS: 00010046
EAX: 0000001d EBX: 03f686d0 ECX: f232a000 EDX: 00000001 ESI: c3f686d0
EDI: 00000000 EBP: f236ad60 ESP: c1b75ef4
DS: 0018 ES: 0018 SS: 0018
process swapper (pid:0, stackpage=c1b75000)
stack: 31d4cd00 f236ad60 00000020 00000016 f236ad013 0b000020 00000000
f8c33f79 fcc415f4 f236ad60 f1d4cd00 f1ddddf80 04000001 f8c3112c
f236ad60 c01086c4 00000016 f236ad60 c1b75f7c c032fde0 c0305ac0
00000016 c1b75f74 c01088b6
call trace: [<f8c33f79>] [<fcc415f4>] [<f8c3112c>] [<c01086c4>]
[<c01088b6>] [<c01053c0>] [<c01053c0>] [<c01053c0>]
[<c01053ec>] [<c0105452>] [<cd117298>] [<c01171a3>]
code: 8b 47 24 5d 68 c2 0e c4 fc e8 3f 63 4d c3 83 c4 08 fa f0 fe
<0> Kernel Panic: Aiee, killing interrupt handler!
in interrupt handler - not syncing
--
=================================================
Borges & Rinolfi Solu??es em Redes Corporativas
Security Officer
Profissional Certificado Conectiva Linux
http://www.techs.com.br/kidmumu - UIN 4553082 - LC 83522
=================================================
On Wed, 30 Jan 2002, Michel Angelo da Silva Pereira wrote:
>
> Here is what I got on /var/log/messages
>
> Jan 30 10:27:21 servmail kernel: Loading Adaptec I2O RAID: Version 2.4 Build 5
> Jan 30 10:27:21 servmail kernel: Detecting Adaptec I2O RAID controllers...
Could you send an lspci listing as well... Looks like the dpt i2o probe
didn't find a supported card.
> Jan 30 10:27:39 servmail kernel: Linux I2O PCI support (c) 1999 Red Hat Software.
> Jan 30 10:27:39 servmail kernel: I2O Core - (C) Copyright 1999 Red Hat Software
> And here is the Oops
>
> CPU:1
> EIP:0010:[<fcc40243>] not tained
> EFLAGS: 00010046
>
> EAX: 0000001d EBX: 03f686d0 ECX: f232a000 EDX: 00000001 ESI: c3f686d0
> EDI: 00000000 EBP: f236ad60 ESP: c1b75ef4
> DS: 0018 ES: 0018 SS: 0018
>
> process swapper (pid:0, stackpage=c1b75000)
>
> stack: 31d4cd00 f236ad60 00000020 00000016 f236ad013 0b000020 00000000
> f8c33f79 fcc415f4 f236ad60 f1d4cd00 f1ddddf80 04000001 f8c3112c
> f236ad60 c01086c4 00000016 f236ad60 c1b75f7c c032fde0 c0305ac0
> 00000016 c1b75f74 c01088b6
>
> call trace: [<f8c33f79>] [<fcc415f4>] [<f8c3112c>] [<c01086c4>]
> [<c01088b6>] [<c01053c0>] [<c01053c0>] [<c01053c0>]
> [<c01053ec>] [<c0105452>] [<cd117298>] [<c01171a3>]
>
> code: 8b 47 24 5d 68 c2 0e c4 fc e8 3f 63 4d c3 83 c4 08 fa f0 fe
Could you run this through ksymoops and send the decoded oops + trace, man
ksymoops has lots of information on how to best do this.
Regards,
Zwane Mwaikambo
> Jan 30 10:33:23 servmail kernel: i2o_scsi.c: Version 0.0.1
> Jan 30 10:33:23 servmail kernel: chain_pool: 2048 bytes @ f6b92800
> Jan 30 10:33:23 servmail kernel: (512 byte buffers X 4 can_queue X 1 =
> i2o controllers)
> Jan 30 10:33:23 servmail kernel: scsi2 : i2o/iop0
Ok the oops is not nice. The timeouts point to i2o_scsi and/or the serveraid
in i2o mode not liking one another (it has an official native mode driver
too btw which is the one you wanted)
Can you run the oops through ksymoops so I can see what the symbols are
and I'll take a look. I guess Im mixing a bus/host address somewhere on
the reset command (which just doesnt occur in normal i2o use)
Could you please try without the adaptec i2o driver compiled in and only
the generic i2o drivers. Also which kernel last worked for you?
Cheers,
Zwane Mwaikambo
Noone kernel works here, I?ve an Adaptec AIC7XXX onboard
and this card Offboard.
I?m going to compile without adaptec module.
Bye
On Wed, Jan 30, 2002 at 05:57:51PM +0200, Zwane Mwaikambo wrote:
> Could you please try without the adaptec i2o driver compiled in and only
> the generic i2o drivers. Also which kernel last worked for you?
>
> Cheers,
> Zwane Mwaikambo
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
=================================================
Borges & Rinolfi Solu??es em Redes Corporativas
Security Officer
Profissional Certificado Conectiva Linux
http://www.techs.com.br/kidmumu - UIN 4553082 - LC 83522
=================================================
> Could you please try without the adaptec i2o driver compiled in and only
> the generic i2o drivers. Also which kernel last worked for you?
The adaptec driver won't touch the IBM ServeRAID - that side is ok. The
generic i2o will see it as it claims to be an I2O device but the right
driver is the IBM ips driver
Alan
On Wed, 30 Jan 2002, Alan Cox wrote:
> The adaptec driver won't touch the IBM ServeRAID - that side is ok. The
> generic i2o will see it as it claims to be an I2O device but the right
> driver is the IBM ips driver
Hmmm i guessed IBM ServeRAID, but then wasn't 100% sure. Thats
interesting, because in order to get my IBM ServeRAID 4L card to work
under 2.2.18 i had to use both the ips driver _and_ generic i2o code too.
Thanks,
Zwane Mwaikambo
> On Wed, 30 Jan 2002, Alan Cox wrote:
>
> > Ok the oops is not nice. The timeouts point to i2o_scsi and/or the serveraid
> > in i2o mode not liking one another (it has an official native mode driver
> > too btw which is the one you wanted)
>
> Is that the one supplied on Intel's site? Or is there a kernel supported
> one?
ServeRAID is IBM - its kernel supported and also on IBM's site.
On Wed, 30 Jan 2002, Alan Cox wrote:
> Ok the oops is not nice. The timeouts point to i2o_scsi and/or the serveraid
> in i2o mode not liking one another (it has an official native mode driver
> too btw which is the one you wanted)
Is that the one supplied on Intel's site? Or is there a kernel supported
one?
Thanks,
Zwane Mwaikambo