Interrupt issue with 2.4.19 vs 2.4.18.

Interrupt issue with 2.4.19 vs 2.4.18.

Post by Reid Sutherlan » Sun, 18 Aug 2002 04:30:07



Hi everyone,

I have a problem with the aic7xxx constantly retrying to initialize my
LVD SCSI drives.  I'm repeatedly getting a "Command already completed"
message.  It was mentioned to me that this might be an interrupt related
problem (thank you Justin!).

My board has a Intel 440GX chipset.  From my understanding these are a
* to deal with and are littered with bugs.  I've also read that by
enabling SMP or IO-APIC, it should solve this issue.  Well, neither does
it for me.

Does anyone know what could have changed between .18 and .19 that would
cause something like this to happen?

Any insight would be appreciated!

Thanks,

-reid

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://www.veryComputer.com/
Please read the FAQ at  http://www.veryComputer.com/

 
 
 

Interrupt issue with 2.4.19 vs 2.4.18.

Post by Reid Sutherlan » Tue, 20 Aug 2002 22:20:07


Hi,

I'm guessing since no one replied it's because either I did not provide
enough details or the the problem itself specific to my hardware which
no one has :)

In an effort to help out as much as I can, could someone shed some light
on how I can debug this further?  What kernel debugging options should
be enabled?  And how can I actually debug this since the system will not
  boot while the problem is happening?

Thanks in advance!

-reid

(please note that 2.4.18 does work _without_ a hitch, but 2.4.19 fails)


> Hi everyone,

> I have a problem with the aic7xxx constantly retrying to initialize my
> LVD SCSI drives.  I'm repeatedly getting a "Command already completed"
> message.  It was mentioned to me that this might be an interrupt related
> problem (thank you Justin!).

> My board has a Intel 440GX chipset.  From my understanding these are a
> * to deal with and are littered with bugs.  I've also read that by
> enabling SMP or IO-APIC, it should solve this issue.  Well, neither does
> it for me.

> Does anyone know what could have changed between .18 and .19 that would
> cause something like this to happen?

> Any insight would be appreciated!

> Thanks,

> -reid

> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

> More majordomo info at  http://www.veryComputer.com/
> Please read the FAQ at  http://www.veryComputer.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://www.veryComputer.com/
Please read the FAQ at  http://www.veryComputer.com/

 
 
 

Interrupt issue with 2.4.19 vs 2.4.18.

Post by Philipp Matthias Hah » Wed, 21 Aug 2002 01:00:18


Hello Reid!


> I have a problem with the aic7xxx constantly retrying to initialize my
> LVD SCSI drives.  I'm repeatedly getting a "Command already completed"
> message.  It was mentioned to me that this might be an interrupt related
> problem (thank you Justin!).

> My board has a Intel 440GX chipset.  From my understanding these are a
> * to deal with and are littered with bugs.  I've also read that by
> enabling SMP or IO-APIC, it should solve this issue.  Well, neither does
> it for me.

> Does anyone know what could have changed between .18 and .19 that would
> cause something like this to happen?

I had it the other way around: 2.4.18 worked only with "pci=noacpi",
2.4.19 works without the extra boot option. You might check for ACPI
related things and give the pci=... options a try.

(My 2.4.18 was actually 2.4.18+acpi+pciirq)

BYtE
Philipp
--
  / /  (_)__  __ ____  __ Philipp Hahn
 / /__/ / _ \/ // /\ \/ /

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://www.veryComputer.com/
Please read the FAQ at  http://www.veryComputer.com/

 
 
 

Interrupt issue with 2.4.19 vs 2.4.18.

Post by Alan Co » Wed, 21 Aug 2002 01:40:06


Quote:> My board has a Intel 440GX chipset.  From my understanding these are a
> * to deal with and are littered with bugs.  I've also read that by

Not bugs. Intel refusal to provide documentation on the IRQ routing for
them

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://www.veryComputer.com/
Please read the FAQ at  http://www.veryComputer.com/

 
 
 

Interrupt issue with 2.4.19 vs 2.4.18.

Post by Reid Sutherlan » Wed, 21 Aug 2002 02:10:05



>>My board has a Intel 440GX chipset.  From my understanding these are a
>>* to deal with and are littered with bugs.  I've also read that by

> Not bugs. Intel refusal to provide documentation on the IRQ routing for
> them

Ahh just lovely.  Any known hack/workaround?

(pci=noacpi doesn't work)

-reid

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://www.veryComputer.com/
Please read the FAQ at  http://www.veryComputer.com/

 
 
 

Interrupt issue with 2.4.19 vs 2.4.18.

Post by Reid Sutherlan » Thu, 22 Aug 2002 04:20:07


This issue has been fixed in 2.4.20-pre1.  I don't know exactly what
patch fixed it, but I suspect it could be Alan's massive patch.

o fix aic7xxx build when PCI=n

It's really hard for me to tell where it was fixed, all I know is it
working now!

So if you had the problem attached to this email, it looks like it's
sovled in 2.4.20pre1.  Or you can revert to 2.4.18.

Hope this helps someone.

-reid

Reid Sutherland wrote:
> Hi everyone,

> I have a problem with the aic7xxx constantly retrying to initialize my
> LVD SCSI drives.  I'm repeatedly getting a "Command already completed"
> message.  It was mentioned to me that this might be an interrupt related
> problem (thank you Justin!).

> My board has a Intel 440GX chipset.  From my understanding these are a
> bitch to deal with and are littered with bugs.  I've also read that by
> enabling SMP or IO-APIC, it should solve this issue.  Well, neither does
> it for me.

> Does anyone know what could have changed between .18 and .19 that would
> cause something like this to happen?

> Any insight would be appreciated!

> Thanks,

> -reid

> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

[ 2.4.19-aic7xxx.output.txt 25K ]
Linux version 2.4.19 (root@victim) (gcc version 2.95.4 20011002 (Debian prerelease)) #4 Fri Aug 16 10:21:41 EDT 2002

BIOS-provided physical RAM map:

 BIOS-e820: 0000000000000000 - 000000000009f800 (usable)

 BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)

 BIOS-e820: 00000000000e8000 - 0000000000100000 (reserved)

 BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)

 BIOS-e820: 000000000fff0000 - 000000000ffffc00 (ACPI data)

 BIOS-e820: 000000000ffffc00 - 0000000010000000 (ACPI NVS)

 BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)

 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)

 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)

255MB LOWMEM available.

found SMP MP-table at 000f6b40

hm, page 000f6000 reserved twice.

hm, page 000f7000 reserved twice.

hm, page 0009f000 reserved twice.

hm, page 000a0000 reserved twice.

On node 0 totalpages: 65520

zone(0): 4096 pages.

zone(1): 61424 pages.

zone(2): 0 pages.

Intel MultiProcessor Specification v1.4

    Virtual Wire compatibility mode.

OEM ID: INTEL    Product ID: Lancewood    APIC at: 0xFEE00000

Processor #1 Pentium(tm) Pro APIC version 17

I/O APIC #0 Version 17 at 0xFEC00000.

Processors: 1

Kernel command line: BOOT_IMAGE=Linux ro root=802 console=ttyS0,tty
0

Initializing CPU#0

Detected 596.923 MHz processor.

Console: colour VGA+ 80x25

Calibrating delay loop... 1189.47 BogoMIPS

Memory: 256488k/262080k available (1090k kernel code, 5204k reserved, 318k data, 224k init, 0k highmem)

Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)

Inode cache hash table entries: 16384 (order: 5, 131072 bytes)

Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)

Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)

Page-cache hash table entries: 65536 (order: 6, 262144 bytes)

CPU: L1 I cache: 16K, L1 D cache: 16K

CPU: L2 cache: 256K

CPU serial number disabled.

Intel machine check architecture supported.

Intel machine check reporting enabled on CPU#0.

CPU: Intel Pentium III (Coppermine) stepping 01

Enabling fast FPU save and restore... done.

Enabling unmasked SIMD FPU exception support... done.

Checking 'hlt' instruction... OK.

POSIX conformance testing by UNIFIX

enabled ExtINT on CPU#0

ESR value before enabling vector: 00000000

ESR value after enabling vector: 00000000

Using local APIC timer interrupts.

calibrating APIC timer ...

..... CPU clock speed is 596.9264 MHz.

..... host bus clock speed is 99.4876 MHz.

cpu: 0, clocks: 994876, slice: 497438

CPU0<T0:994864,T1:497424,D:2,S:497438,C:994876>

mtrr: v1.40 (20010327) Richard Gooch (rgo...@atnf.csiro.au)

mtrr: detected mtrr type: Intel

PCI: PCI BIOS revision 2.10 entry at 0xfdab0, last bus=2

PCI: Using configuration type 1

PCI: Probing PCI hardware

Unknown bridge resource 0: assuming transparent

Unknown bridge resource 1: assuming transparent

Unknown bridge resource 2: assuming transparent

Unknown bridge resource 0: assuming transparent

Unknown bridge resource 1: assuming transparent

Unknown bridge resource 2: assuming transparent

PCI: Discovered primary peer bus ff [IRQ]

PCI: Using IRQ router PIIX [8086/7110] at 00:12.0

isapnp: Scanning for PnP cards...

isapnp: No Plug & Play device found

Linux NET4.0 for Linux 2.4

Based upon Swansea University Computer Society NET3.039

Initializing RT netlink socket

apm: BIOS not found.

Starting kswapd

VFS: Diskquotas version dquot_6.4.0 initialized

Journalled Block Device driver loaded

ACPI: Core Subsystem version [20011018]

ACPI: Subsystem enabled

pty: 256 Unix98 ptys configured

Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled

ttyS00 at 0x03f8 (irq = 4) is a 16550A

ttyS01 at 0x02f8 (irq = 3) is a 16550A

eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html

eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <s...@saw.sw.com.sg> and others

PCI: Assigned IRQ 11 for device 00:09.0

PCI: Sharing IRQ 11 with 00:0c.0

PCI: Sharing IRQ 11 with 00:0c.1

eth0: Intel Corp. 82557/8/9 [Ethernet Pro 100], 00:D0:B7:85:C0:4B, IRQ 11.

  Board assembly 729757-006, Physical connectors present: RJ45

  Primary interface chip i82555 PHY #1.

  General self-test: passed.

  Serial sub-system self-test: passed.

  Internal registers self-test: passed.

  ROM checksum self-test: passed (0x04f4518b).

PCI: Assigned IRQ 10 for device 00:0e.0

PCI: Sharing IRQ 10 with 00:12.2

eth1: Intel Corp. 82557/8/9 [Ethernet Pro 100] (#2), 00:D0:B7:65:CD:AF, IRQ 10.

  Board assembly 000000-000, Physical connectors present: RJ45

  Primary interface chip i82555 PHY #1.

  General self-test: passed.

  Serial sub-system self-test: passed.

  Internal registers self-test: passed.

  ROM checksum self-test: passed (0x04f4518b).

SCSI subsystem driver Revision: 1.00

PCI: Found IRQ 11 for device 00:0c.0

PCI: Sharing IRQ 11 with 00:09.0

PCI: Sharing IRQ 11 with 00:0c.1

PCI: Found IRQ 11 for device 00:0c.1

PCI: Sharing IRQ 11 with 00:09.0

PCI: Sharing IRQ 11 with 00:0c.0

scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8

        <Adaptec aic7896/97 Ultra2 SCSI adapter>

        aic7896/97: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs

scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8

        <Adaptec aic7896/97 Ultra2 SCSI adapter>

        aic7896/97: Ultra2 Wide Channel B, SCSI Id=7, 32/253 SCBs

scsi0:0:0:0: Attempting to queue an ABORT message

scsi0: Dumping Card State while idle, at SEQADDR 0x8

ACCUM = 0x0, SINDEX = 0x3, DINDEX = 0xe4, ARG_2 = 0x0

HCNT = 0x0 SCBPTR = 0x0

SCSISEQ = 0x12, SBLKCTL = 0xa

 DFCNTRL = 0x0, DFSTATUS = 0x89

LASTPHASE = 0x1, SCSISIGI = 0x0, SXFRCTL0 = 0x80

SSTAT0 = 0x0, SSTAT1 = 0xa

STACK == 0x3, 0x107, 0x15f, 0x0

SCB count = 4

Kernel NEXTQSCB = 2

Card NEXTQSCB = 2

QINFIFO entries:

Waiting Queue entries:

Disconnected Queue entries:

QOUTFIFO entries:

Sequencer Free SCB List: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Sequencer SCB Info: 0(c 0x40, s 0x7, l 0, t 0xff) 1(c 0x0, s 0xff, l 255, t 0xff) 2(c 0x0, s 0xff, l 255, t 0xff) 3(c 0x0, s 0xff, l 255, t 0xff) 4(c 0x0, s 0xff, l 255, t 0xff) 5(c 0x0, s 0xff, l 255, t 0xff) 6(c 0x0, s 0xff, l 255, t 0xff) 7(c 0x0, s 0xff, l 255, t 0xff) 8(c 0x0, s 0xff, l 255, t 0xff) 9(c 0x0, s 0xff, l 255, t 0xff) 10(c 0x0, s 0xff, l 255, t 0xff) 11(c 0x0, s 0xff, l 255, t 0xff) 12(c 0x0, s 0xff, l 255, t 0xff) 13(c 0x0, s 0xff, l 255, t 0xff) 14(c 0x0, s 0xff, l 255, t 0xff) 15(c 0x0, s 0xff, l 255, t 0xff) 16(c 0x0, s 0xff, l 255, t 0xff) 17(c 0x0, s 0xff, l 255, t 0xff) 18(c 0x0, s 0xff, l 255, t 0xff) 19(c 0x0, s 0xff, l 255, t 0xff) 20(c 0x0, s 0xff, l 255, t 0xff) 21(c 0x0, s 0xff, l 255, t 0xff) 22(c 0x0, s 0xff, l 255, t 0xff) 23(c 0x0, s 0xff, l 255, t 0xff) 24(c 0x0, s 0xff, l 255, t 0xff) 25(c 0x0, s 0xff, l 255, t 0xff) 26(c 0x0, s 0xff, l 255, t 0xff) 27(c 0x0, s 0xff, l 255, t 0xff) 28(c 0x0, s 0xff, l 255, t 0xff) 29(c 0x0, s 0xff, l 255, t 0xff) 30(c 0x0, s 0xff, l 255, t 0xff) 31(c 0x0, s 0xff, l 255, t 0xff)

Pending list:

Kernel Free SCB list: 3 1 0

DevQ(0:0:0): 0 waiting

scsi0:0:0:0: Command already completed

aic7xxx_abort returns 0x2002

scsi0:0:0:0: Attempting to queue an ABORT message

scsi0: Dumping Card State in Message-out phase, at SEQADDR 0xe7

ACCUM = 0xa0, SINDEX = 0x61, DINDEX = 0xe4, ARG_2 = 0x0

HCNT = 0x0 SCBPTR = 0x0

SCSISEQ = 0x12, SBLKCTL = 0xa

 DFCNTRL = 0x0, DFSTATUS = 0x89

LASTPHASE = 0xa0, SCSISIGI = 0xb6, SXFRCTL0 = 0x88

SSTAT0 = 0x2, SSTAT1 = 0x3

STACK == 0xe6, 0x175, 0x15f, 0x0

SCB count = 4

Kernel NEXTQSCB = 3

Card NEXTQSCB = 3

QINFIFO entries:

Waiting Queue entries:

Disconnected Queue entries:

QOUTFIFO entries:

Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Sequencer SCB Info: 0(c 0x40, s 0x7, l 0, t 0x2) 1(c 0x0, s 0xff, l 255, t 0xff) 2(c 0x0, s 0xff, l 255, t 0xff) 3(c 0x0, s 0xff, l 255, t 0xff) 4(c 0x0, s 0xff, l 255, t 0xff) 5(c 0x0, s 0xff, l 255, t 0xff) 6(c 0x0, s 0xff, l 255, t 0xff) 7(c 0x0, s 0xff, l 255, t 0xff) 8(c 0x0, s 0xff, l 255, t 0xff) 9(c 0x0, s 0xff, l 255, t 0xff) 10(c 0x0, s 0xff, l 255, t 0xff) 11(c 0x0, s 0xff, l 255, t 0xff) 12(c 0x0, s 0xff, l 255, t 0xff) 13(c 0x0, s 0xff, l 255, t 0xff) 14(c 0x0, s 0xff, l 255, t 0xff) 15(c 0x0, s 0xff, l 255, t 0xff) 16(c 0x0, s 0xff, l 255, t 0xff) 17(c 0x0, s 0xff, l 255, t 0xff) 18(c 0x0, s 0xff, l 255, t 0xff) 19(c 0x0, s 0xff, l 255, t 0xff) 20(c 0x0, s 0xff, l 255, t 0xff) 21(c 0x0, s 0xff, l 255, t 0xff) 22(c 0x0, s 0xff, l 255, t 0xff) 23(c 0x0, s 0xff, l 255, t 0xff) 24(c 0x0, s 0xff, l 255, t 0xff) 25(c 0x0, s 0xff, l 255, t 0xff) 26(c 0x0, s 0xff, l 255, t 0xff) 27(c 0x0, s 0xff, l 255, t 0xff) 28(c 0x0, s 0xff, l 255, t 0xff) 29(c 0x0, s 0xff, l 255, t 0xff) 30(c 0x0, s 0xff, l 255, t 0xff) 31(c 0x0, s 0xff, l 255, t 0xff)

Pending list: 2(c 0x40, s 0x7, l 0)

Kernel Free SCB list: 1 0

Untagged Q(0): 2

DevQ(0:0:0): 0 waiting

scsi0:0:0:0: Device is active, asserting ATN

Recovery code sleeping

Recovery code awake

Timer Expired

aic7xxx_abort returns 0x2003

scsi0:0:0:0: Attempting to queue a TARGET RESET message

aic7xxx_dev_reset returns 0x2003

Recovery SCB completes

scsi0:0:0:0: Attempting to queue an ABORT message

ahc_intr: HOST_MSG_LOOP bad phase 0x0

scsi0: Dumping Card State while idle, at SEQADDR 0x46

ACCUM = 0xa0, SINDEX = 0x61, DINDEX = 0xe4, ARG_2 = 0x0

HCNT = 0x0 SCBPTR = 0x0

SCSISEQ = 0x12, SBLKCTL = 0xa

 DFCNTRL = 0x0, DFSTATUS = 0x89

LASTPHASE = 0x1, SCSISIGI = 0x0, SXFRCTL0 = 0x88

SSTAT0 = 0x0, SSTAT1 = 0x0

STACK == 0x15f, 0x0, 0xe5, 0x3

SCB count = 4

Kernel NEXTQSCB = 2

Card NEXTQSCB = 3

QINFIFO entries: 3

Waiting Queue entries:

Disconnected Queue entries:

QOUTFIFO entries:

Sequencer Free SCB List: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 ...

read more »

 
 
 

1. issues with 2.4.19 that didn't exist in 2.4.18...

I got this new in 2.4.19, and my busmaster IDE doesn't work:

---------------
pty: 256 Unix98 ptys configured
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
ICH3M: IDE controller on PCI bus 00 dev f9
PCI: Device 00:1f.1 not available because of resource collisions
ICH3M: (ide_setup_pci_device:) Could not enable device.
--------------

lspci
[...]
00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 41)
00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 01)
00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 01)
00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus (rev 01)
00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem (rev 01)
[...]

Yep, that's my IDE controller allright.

The machine kept on crashing on me too before I could get this to even
boot.  2.4.18 works fine and bmide works...

Likely I have a broken bios or something, but something changed?

Thanks,

-bc

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Startup file for Bind on solaris 8

3. Compilation problem: SiS 630 dri driver (2.4.18 and 2.4.19-rc3)

4. pdc202xx.c, adds another quirk drive to the list

5. Kernel Panic 2.4.18 - 2.4.19-rc3 when using iptables

6. Problem : fgrep -l pattern filename , but recursivley ?

7. kernel 2.4.18 + 2.4.19-pre10 patch

8. Unable to Compile gdk-pixbuf-0.4.tar.gz

9. Announce: kdb v2.3 i386 updates for kernels 2.4.18 and 2.4.19

10. PCI Resources: 2.4.19 fails 82801CAM IDE, but 2.4.18 goes anyway?

11. broken compile fixes for 2.4.18 or 2.4.19-pre1

12. Slow system after switching from 2.4.18 to 2.4.19

13. USB lockup in 2.4.18-pre8 <-- typo 2.4.19-pre8