From owner-freebsd-scsi Wed Nov 29 14:24: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front4.grolier.fr (front4.grolier.fr [194.158.96.54]) by hub.freebsd.org (Postfix) with ESMTP id C375337B401 for ; Wed, 29 Nov 2000 14:23:56 -0800 (PST) Received: from nas1-13.cgy.club-internet.fr (nas1-13.cgy.club-internet.fr [195.36.197.13]) by front4.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA13203; Wed, 29 Nov 2000 23:23:45 +0100 (MET) Date: Wed, 29 Nov 2000 22:23:52 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Kevin Day Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sym driver in 4.1.1+ on Proliant In-Reply-To: <200011291950.NAA54487@temphost.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 29 Nov 2000, Kevin Day wrote: > I've got several Compaq Proliant ML530's with the internal '896 SCSI > controller. Everything works great on 4.1-RELEASE. Going to 4.1.1 or 4.2 > causes sym0 to say "Cannot allocate IRQ resource", followed by a kernel t= rap > inside the sym driver. Has anyone experienced this, or know what I can tr= y? It has been no change in this area of the driver between 4.1 and 4.1.1. The driver normally allocates IRQs as shared resources as PCI requires interrupt lines to be shareable. The IRQ for `sym0' appears to be #11 on the boot messages below. I you didn't change any piece of hardware neither changed the IRQ (PNP?) settings from your motherboard setup, sym0 should still be assigned IRQ 11 on your machine. Anyway, it would be interesting to know if the IRQ now assigned to `sym0' (whatever it is still IRQ11 or not) is shared by `sym0' and another device that has kernel support in your kernel config (GENERIC?) for 4.1.1 but haven't support in your kernel config for 4.1. If, for example, IRQ 11 was allocated by another driver as non shareable and `sym' tries to allocate it as shareable, allocation of this resource by `sym' will fail with exactly the message your report. G=E9rard. > -- Kevin >=20 >=20 > Here's a dmesg from 4.1 where things do work: > (the same issue occurs on a server with no PCI cards in it, except for an= fxp0) >=20 >=20 > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.1-RELEASE #0: Thu Jul 27 04:44:16 GMT 2000 > root@usw4.freebsd.org:/usr/src/sys/compile/GENERIC > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (863.93-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0x683 Stepping =3D 3 > Features=3D0x383f9ff > real memory =3D 402636800 (393200K bytes) > avail memory =3D 387260416 (378184K bytes) > Pentium Pro MTRR support enabled > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pci0: (vendor=3D0x0e11, dev=3D0xa0f0) at 3.0 > pci0: at 5.0 > fxp0: port 0x2400-0x243f mem 0xc6800000= -0xc68fffff,0xc69fd000-0xc69fdfff irq 5 at device 8.0 on pci0 > fxp0: Ethernet address 00:50:8b:ae:c5:38 > isab0: at device 15.0 o= n pci0 > isa0: on isab0 > atapci0: port 0x2440-0x244f at device 15.1 o= n pci0 > ata0: at 0x1f0 irq 14 on atapci0 > pcib2: on motherboard > pci2: on pcib2 > pci2: (vendor=3D0x1148, dev=3D0x4300) at 6.0 irq 10 > pcib255: on motherboard > pci255: on pcib255 > pcib5: on motherboard > pci5: on pcib5 > sym0: <896> port 0x4000-0x40ff mem 0xc6bfc000-0xc6bfdfff,0xc6bffc00-0xc6b= fffff irq 11 at device 4.0 on pci5 > sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking > sym1: <896> port 0x4400-0x44ff mem 0xc6bf8000-0xc6bf9fff,0xc6bfbc00-0xc6b= fbfff irq 15 at device 4.1 on pci5 > sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking > pcib1: at device 7.0 on pci5 > pci6: on pcib1 > sf0: port 0x5000-0x50ff mem 0xc6d80000-0= xc6dfffff irq 5 at device 4.0 on pci6 > sf0: Ethernet address: 00:00:d1:ed:c0:e5 > miibus0: on sf0 > ukphy0: on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sf1: port 0x5400-0x54ff mem 0xc6d00000-0= xc6d7ffff irq 5 at device 5.0 on pci6 > sf1: Ethernet address: 00:00:d1:ed:c0:e6 > miibus1: on sf1 > ukphy1: on miibus1 > ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sf2: port 0x5800-0x58ff mem 0xc6c80000-0= xc6cfffff irq 5 at device 6.0 on pci6 > sf2: Ethernet address: 00:00:d1:ed:c0:e7 > miibus2: on sf2 > ukphy2: on miibus2 > ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sf3: port 0x5c00-0x5cff mem 0xc6c00000-0= xc6c7ffff irq 5 at device 7.0 on pci6 > sf3: Ethernet address: 00:00:d1:ed:c0:e8 > miibus3: on sf3 > ukphy3: on miibus3 > ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > pcib3: at device 9.0 on pci5 > pci7: on pcib3 > sf4: port 0x6000-0x60ff mem 0xc6f80000-0= xc6ffffff irq 5 at device 4.0 on pci7 > sf4: Ethernet address: 00:00:d1:ed:c0:7d > miibus4: on sf4 > ukphy4: on miibus4 > ukphy4: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sf5: port 0x6400-0x64ff mem 0xc6f00000-0= xc6f7ffff irq 5 at device 5.0 on pci7 > sf5: Ethernet address: 00:00:d1:ed:c0:7e > miibus5: on sf5 > ukphy5: on miibus5 > ukphy5: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sf6: port 0x6800-0x68ff mem 0xc6e80000-0= xc6efffff irq 5 at device 6.0 on pci7 > sf6: Ethernet address: 00:00:d1:ed:c0:7f > miibus6: on sf6 > ukphy6: on miibus6 > ukphy6: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sf7: port 0x6c00-0x6cff mem 0xc6e00000-0= xc6e7ffff irq 5 at device 7.0 on pci7 > sf7: Ethernet address: 00:00:d1:ed:c0:80 > miibus7: on sf7 > ukphy7: on miibus7 > ukphy7: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > eisa0: on motherboard > mainboard0: on eisa0 slot 0 > eisa0: unknown card @@@0000 (0x00000000) at slot 5 > eisa0: unknown card @@@0000 (0x00000000) at slot 6 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: cannot reserve I/O port range > ata0-slave: identify retries exceeded > acd0: CDROM at ata0-master using PIO4 > Waiting 15 seconds for SCSI devices to settle > Mounting root from ufs:da0s1a > da1 at sym0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device=20 > da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing = Enabled > da1: 17365MB (35565080 512 byte sectors: 255H 63S/T 2213C) > da2 at sym0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-2 device=20 > da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing = Enabled > da2: 17365MB (35565080 512 byte sectors: 255H 63S/T 2213C) > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device=20 > da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing = Enabled > da0: 17365MB (35565080 512 byte sectors: 255H 63S/T 2213C) > vinum: loaded > vinum: reading configuration from /dev/da2s1b > vinum: updating configuration from /dev/da1s1b >=20 >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message