[2.5.54] Oops IDE-SCSI and failure AIC7xxx

[2.5.54] Oops IDE-SCSI and failure AIC7xxx

[Paul Rolland]

Hello,

Here is the copy of a boot sequence using kernel 2.5.54 :
aic7xxx: PCI Device 0:8:0 failed memory mapped test.  Using PIO.
scsi0: PCI error Interrupt at seqaddr = 0x3
scsi0: Signaled a Target Abort
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.25
        <Adaptec 2940 Ultra2 SCSI adapter>
        aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs

(scsi0:A:0): 40.000MB/s transfers (20.000MHz, offset 127, 16bit)
  Vendor: FUJITSU   Model: MAN3367MP         Rev: 5507
  Type:   Direct-Access                      ANSI SCSI revision: 03
scsi0:A:0:0: Tagged Queuing enabled.  Depth 64
scsi1 : SCSI host adapter emulation for IDE ATAPI devices
  Vendor: TDK       Model: CDRW4800B         Rev: S7S3
  Type:   CD-ROM                             ANSI SCSI revision: 02
ide-scsi: abort called for 21
Unable to handle kernel NULL pointer dereference at virtual address
00000030
 printing eip:
c030802c
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0060:[<c030802c>]    Not tainted
EFLAGS: 00010082
Unable to handle kernel paging request at virtual address ffffff8d
 printing eip:
c012ecc7
*pde = 00001067
*pte = 00000000
Oops: 0002
CPU:    0
EIP:    0060:[<c012ecc7>]    Not tainted
EFLAGS: 00010006

Out of this, two problems :
 - AIC7xxx fails to use DMA, with :
aic7xxx: PCI Device 0:8:0 failed memory mapped test.  Using PIO.
scsi0: PCI error Interrupt at seqaddr = 0x3
scsi0: Signaled a Target Abort

 - IDE scsi oops at boot.
7 [12:01] rol@donald:~> ksymoops -v /usr/src/linux/vmlinux -m
/boot/System.map-2.5.54 -K < oops-idescsi2
ksymoops 2.4.8 on i686 2.4.20.  Options used
     -v /usr/src/linux/vmlinux (specified)
     -K (specified)
     -l /proc/modules (default)
     -o /lib/modules/2.4.20/ (default)
     -m /boot/System.map-2.5.54 (specified)

No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Unable to handle kernel NULL pointer dereference at virtual address
00000030
c030802c
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0060:[<c030802c>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010082
Warning (Oops_read): Code line not seen, dumping what data is available


>>EIP; c030802c <idescsi_abort+74/108>   <=====


1 warning issued.  Results may not be reliable.

Regards,
Paul Rolland, rol@as2917.net

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[Justin T. Gibbs]

> Out of this, two problems :
>  - AIC7xxx fails to use DMA, with :
> aic7xxx: PCI Device 0:8:0 failed memory mapped test.  Using PIO.
> scsi0: PCI error Interrupt at seqaddr = 0x3
> scsi0: Signaled a Target Abort

This is because your system is violating the PCI spec.  There is
now an explicit test for this during driver initialization so that
the driver doesn't unexpectedly fail later.  I can change the driver
so that it doesn't print out the diagnostic if it would make you
feel better. 8-)

Just out of curiosity, what MB/Chipset are you using?

--
Justin

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[Paul Rolland]

Hello,

> > Out of this, two problems :
> >  - AIC7xxx fails to use DMA, with :
> > aic7xxx: PCI Device 0:8:0 failed memory mapped test.  Using PIO.
> > scsi0: PCI error Interrupt at seqaddr = 0x3
> > scsi0: Signaled a Target Abort
> 
> This is because your system is violating the PCI spec.  There 
Waouh.... It is a quite new MB... I wasn't expecting it to be
so bad...

> is now an explicit test for this during driver initialization 
> so that the driver doesn't unexpectedly fail later.  I can 
Thanks for taking care of people with bad hardware...

> change the driver so that it doesn't print out the diagnostic 
> if it would make you feel better. 8-)
No, just keep it like that... It is a dev kernel !
 
> Just out of curiosity, what MB/Chipset are you using?
This is an ASUS P4S8X MB.
Not sure about the kind of chipset you are looking for, so here
are some details (but full spec are avail at asus web site).

[root@donald rol]# lspci -vvv
00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device
0648 (rev 02)
        Subsystem: Asustek Computer, Inc.: Unknown device 8086
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort+ <MAbort+ >SERR- <PERR-
        Latency: 32
        Region 0: Memory at d0000000 (32-bit, non-prefetchable)
[size=256M]
        Capabilities: [c0] AGP version 2.0
         Status: RQ=31 SBA+ 64bit- FW+ Rate=x1,x2,x4
         Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>

00:01.0 PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP
(prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 0000d000-0000dfff
        Memory behind bridge: cf800000-cfffffff
        Prefetchable memory behind bridge: eff00000-febfffff
        BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-

00:02.0 ISA bridge: Silicon Integrated Systems [SiS]: Unknown device
0963 (rev 04)
        Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 0

00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
(prog-if 80 [Master])
        Subsystem: Asustek Computer, Inc.: Unknown device 8087
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 128
        Interrupt: pin ? routed to IRQ 11
        Region 4: I/O ports at a400 [size=16]

00:03.0 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 0f)
(prog-if 10 [OHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 8087
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR+
        Latency: 32 (20000ns max), cache line size 08
        Interrupt: pin A routed to IRQ 9
        Region 0: Memory at ce800000 (32-bit, non-prefetchable)
[size=4K]

00:03.1 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 0f)
(prog-if 10 [OHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 8087
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (20000ns max), cache line size 08
        Interrupt: pin B routed to IRQ 9
        Region 0: Memory at ce000000 (32-bit, non-prefetchable)
[size=4K]

00:03.2 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 0f)
(prog-if 10 [OHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 8087
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (20000ns max), cache line size 08
        Interrupt: pin C routed to IRQ 9
        Region 0: Memory at cd800000 (32-bit, non-prefetchable)
[size=4K]

00:03.3 USB Controller: Silicon Integrated Systems [SiS]: Unknown device
7002 (prog-if 20 [EHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 8087
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (20000ns max), cache line size 08
        Interrupt: pin D routed to IRQ 9
        Region 0: Memory at cd000000 (32-bit, non-prefetchable)
[size=4K]
        Capabilities: [50] Power Management version 2
         Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
         Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:08.0 SCSI storage controller: Adaptec AHA-2940U2/U2W
        Subsystem: Adaptec AHA-2940U2W SCSI Controller
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (9750ns min, 6250ns max), cache line size 08
        Interrupt: pin A routed to IRQ 10
        BIST result: 00
        Region 0: I/O ports at 8400 [size=256]
        Region 1: Memory at cc000000 (64-bit, non-prefetchable)
[disabled] [size=4K]
        Expansion ROM at <unassigned> [disabled] [size=128K]
        Capabilities: [dc] Power Management version 1
         Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
         Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:09.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev
07)
        Subsystem: Creative Labs: Unknown device 8064
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (500ns min, 5000ns max)
        Interrupt: pin A routed to IRQ 5
        Region 0: I/O ports at 8000 [size=32]
        Capabilities: [dc] Power Management version 1
         Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
         Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:09.1 Input device controller: Creative Labs SB Live! MIDI/Game Port
(rev 07)
        Subsystem: Creative Labs Gameport Joystick
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32
        Region 0: I/O ports at 7800 [size=8]
        Capabilities: [dc] Power Management version 1
         Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
         Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0a.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX
[Boomerang]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (750ns min, 2000ns max)
        Interrupt: pin A routed to IRQ 7
        Region 0: I/O ports at 7400 [size=64]
        Expansion ROM at <unassigned> [disabled] [size=64K]

01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV200 QW
[Radeon 7500] (prog-if 00 [VGA])
        Subsystem: Giga-byte Technology: Unknown device 4000
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping+ SERR- FastB2B-
        Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (2000ns min), cache line size 08
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
        Region 1: I/O ports at d800 [size=256]
        Region 2: Memory at cf800000 (32-bit, non-prefetchable)
[size=64K]
        Expansion ROM at effe0000 [disabled] [size=128K]
        Capabilities: [58] AGP version 2.0
         Status: RQ=47 SBA+ 64bit- FW- Rate=x1,x2,x4
         Command: RQ=0 SBA+ AGP- 64bit- FW- Rate=<none>
        Capabilities: [50] Power Management version 2
         Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
         Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Does this help in any way ?

Regards,
Paul, rol@as2917.net

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[Justin T. Gibbs]

> Hello,
> 
>> > Out of this, two problems :
>> >  - AIC7xxx fails to use DMA, with :
>> > aic7xxx: PCI Device 0:8:0 failed memory mapped test.  Using PIO.
>> > scsi0: PCI error Interrupt at seqaddr = 0x3
>> > scsi0: Signaled a Target Abort
>> 
>> This is because your system is violating the PCI spec.  There 
> Waouh.... It is a quite new MB... I wasn't expecting it to be
> so bad...

There may be options in your BIOS to disable this "feature".  Look
for things like "PCI byte-merging" and/or "PCI read prefetch".  I
haven't had access to one of the new SIS based P4 systems yet, so
I don't know how they are setup or exactly how they are violating
the PCI spec.  The test will fail either if byte-merging or read
prefetch occurs and perhaps if there is an MTTR covering the memory
mapped region of the chip that is set to write combining mode (I
don't think that the mb() we issue after every memory write helps
in this last case).

--
Justin

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[Paul Rolland]

Hello,

> There may be options in your BIOS to disable this "feature".  
> Look for things like "PCI byte-merging" and/or "PCI read 
> prefetch".  I haven't had access to one of the new SIS based 
> P4 systems yet, so I don't know how they are setup or exactly 
> how they are violating the PCI spec.  The test will fail 
> either if byte-merging or read prefetch occurs and perhaps if 
> there is an MTTR covering the memory mapped region of the 
> chip that is set to write combining mode (I don't think that 
> the mb() we issue after every memory write helps in this last case).

I've been looking at the PCI option in the BIOS...

1st part is mapping IRQ to PCI slots...
Then, you have :
PCI/VGA Palette Snoop         Disabled
PCI Latency Timer             32
Primary VGA BIOS              PCI VGA Card
USB Function                  Enabled
USB2.0 Function               Enabled
Onboard LAN Boot ROM          Disabled

Maybe related, the memory config :
SDRAM Configuration           By SPD
Chipset clock mode            Synchronous
SDRam Command Lead-off time   Auto
Graphics Aperture Size        256 MB
AGP Capability                4x Mode
AGP Fast Write Capability     Enabled
Video Memory Cache Mode       UC
Memory hole at 15M-16M        Disabled
PCI 2.1 Support               Enabled
Onboard PCI IDE Enable        Both
IDE Bus Master Support        Enabled

Could it be PCI 2.1 Support ? Don't think because I've restarted
with it disabled, and I still have the same problem...

Regards,
Paul

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[Justin T. Gibbs]

> I've been looking at the PCI option in the BIOS...

...

> Could it be PCI 2.1 Support ? Don't think because I've restarted
> with it disabled, and I still have the same problem...

No.  That shouldn't make a difference.

--
Justin

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[J.A. Magallon]

On 2003.01.05 Justin T. Gibbs wrote:
> > I've been looking at the PCI option in the BIOS...
> 
> ...
> 
> > Could it be PCI 2.1 Support ? Don't think because I've restarted
> > with it disabled, and I still have the same problem...
> 
> No.  That shouldn't make a difference.
> 

I also get this on a SuperMicro P6DGU:

SCSI subsystem driver Revision: 1.00
aic7xxx: PCI Device 0:14:0 failed memory mapped test.  Using PIO.
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.25
        <Adaptec aic7890/91 Ultra2 SCSI adapter>
        aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs

scsi0: PCI error Interrupt at seqaddr = 0x2
scsi0: Signaled a Target Abort
(scsi0:A:0): 80.000MB/s transfers (40.000MHz, offset 63, 16bit)
(scsi0:A:1): 80.000MB/s transfers (40.000MHz, offset 63, 16bit)
  Vendor: IBM       Model: DDYS-T09170N      Rev: S96H
  Type:   Direct-Access                      ANSI SCSI revision: 03
  Vendor: IBM       Model: IC35L018UWD210-0  Rev: S5BS
  Type:   Direct-Access                      ANSI SCSI revision: 03

werewolf:~/in# lspci -v
00:00.0 Host bridge: Intel Corp. 440GX - 82443GX Host bridge
        Flags: bus master, medium devsel, latency 64
        Memory at f0000000 (32-bit, prefetchable) [size=128M]
        Capabilities: [a0] AGP version 1.0

00:01.0 PCI bridge: Intel Corp. 440GX - 82443GX AGP bridge (prog-if 00 [Normal decode])
        Flags: bus master, 66Mhz, medium devsel, latency 64
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
        I/O behind bridge: 0000d000-0000dfff
        Memory behind bridge: fca00000-feafffff
        Prefetchable memory behind bridge: dc800000-ec8fffff
...
00:0e.0 SCSI storage controller: Adaptec AHA-2940U2/U2W / 7890/7891 (rev 01)
        Subsystem: Adaptec 2940U2W SCSI Controller
        Flags: bus master, medium devsel, latency 64, IRQ 10
        BIST result: 00
        I/O ports at e800 [size=256]
        Memory at febff000 (64-bit, non-prefetchable) [disabled] [size=4K]
        Expansion ROM at febc0000 [disabled] [size=128K]
        Capabilities: [dc] Power Management version 1

???

-- 
J.A. Magallon <jamagallon@able.es>      \                 Software is like sex:
werewolf.able.es                         \           It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.21-pre2-jam2 (gcc 3.2.1 (Mandrake Linux 9.1 3.2.1-2mdk))

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[David Lang]

I get the same 'failed memory mapped' error (and the inability to run 2.5
kernels) on my SIS K6 board which has been running without a problem with
2.2 and 2.4 kernels.
this is /proc/pci from 2.4.18

PCI devices found:
  Bus  0, device   0, function  0:
    Host bridge: Silicon Integrated Systems [SiS] 530 Host (rev 2).
      Master Capable.  Latency=32.
      Non-prefetchable 32 bit memory at 0xe8000000 [0xebffffff].
  Bus  0, device   0, function  1:
    IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 208).
      Master Capable.  Latency=128.
      I/O at 0xffa0 [0xffaf].
  Bus  0, device   1, function  0:
    ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 177).
  Bus  0, device   1, function  1:
    Class ff00: Silicon Integrated Systems [SiS] ACPI (rev 0).
  Bus  0, device   2, function  0:
    PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP (rev 0).
      Master Capable.  No bursts.  Min Gnt=12.
  Bus  0, device  10, function  0:
    SCSI storage controller: Adaptec AHA-294x / AIC-7871 (rev 3).
      IRQ 9.
      Master Capable.  Latency=32.  Min Gnt=8.Max Lat=8.
      I/O at 0xda00 [0xdaff].
      Non-prefetchable 32 bit memory at 0xeffef000 [0xeffeffff].
  Bus  0, device  11, function  0:
    Ethernet controller: 3Com Corporation 3c595 100BaseTX [Vortex] (rev
0).
      IRQ 11.
      Master Capable.  Latency=248.  Min Gnt=3.Max Lat=8.
      I/O at 0xdc00 [0xdc1f].
  Bus  0, device  12, function  0:
    Multimedia audio controller: C-Media Electronics Inc CM8338A (rev 16).
      IRQ 10.
      Master Capable.  Latency=32.  Min Gnt=2.Max Lat=24.
      I/O at 0xde00 [0xdeff].
  Bus  1, device   0, function  0:
    VGA compatible controller: Silicon Integrated Systems [SiS] 6306
3D-AGP (rev 162).
      Master Capable.  Latency=32.  Min Gnt=2.
      Prefetchable 32 bit memory at 0xff000000 [0xff7fffff].
      Non-prefetchable 32 bit memory at 0xe7ef0000 [0xe7efffff].
      I/O at 0xcc00 [0xcc7f].

David Lang

On Sun, 5 Jan 2003, Justin T. Gibbs wrote:

> Date: Sun, 05 Jan 2003 08:50:06 -0700
> From: Justin T. Gibbs <gibbs@scsiguy.com>
> To: Paul Rolland <rol@witbe.net>, linux-kernel@vger.kernel.org
> Subject: Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx
>
> > Out of this, two problems :
> >  - AIC7xxx fails to use DMA, with :
> > aic7xxx: PCI Device 0:8:0 failed memory mapped test.  Using PIO.
> > scsi0: PCI error Interrupt at seqaddr = 0x3
> > scsi0: Signaled a Target Abort
>
> This is because your system is violating the PCI spec.  There is
> now an explicit test for this during driver initialization so that
> the driver doesn't unexpectedly fail later.  I can change the driver
> so that it doesn't print out the diagnostic if it would make you
> feel better. 8-)
>
> Just out of curiosity, what MB/Chipset are you using?
>
> --
> Justin
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[Justin T. Gibbs]

> I get the same 'failed memory mapped' error (and the inability to run 2.5
> kernels)

The messages and the inability to run 2.5 kernels are not related.  The
diagnostic prints and the driver falls back to using the "safe" PIO method.

--
Justin

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[David Lang]

Ok, but it's the only error message I get and the AIX7xxx driver then
fails to initialize.

David Lang

On Sun, 5 Jan 2003, Justin T. Gibbs wrote:

> Date: Sun, 05 Jan 2003 20:08:10 -0700
> From: Justin T. Gibbs <gibbs@scsiguy.com>
> To: David Lang <david.lang@digitalinsight.com>
> Cc: Paul Rolland <rol@witbe.net>, linux-kernel@vger.kernel.org
> Subject: Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx
>
> > I get the same 'failed memory mapped' error (and the inability to run 2.5
> > kernels)
>
> The messages and the inability to run 2.5 kernels are not related.  The
> diagnostic prints and the driver falls back to using the "safe" PIO method.
>
> --
> Justin
>

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[Justin T. Gibbs]

> Ok, but it's the only error message I get and the AIX7xxx driver then
> fails to initialize.

Can you be just a bit more specific?  Actual driver messages are
usually a big help.

--
Justin

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[David Lang]

other then the memmap error (in my case device 0:10:0 I get the first
three lines of the driver init and then nothing. the machine
completely locks up (driver version on .54 is 6.2.25 but I've
had this same problem since .50)

here is what I get on 2.4.18, the only difference on the first three lines
between this and 2.5.54 is the driver version number

scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.4
        <Adaptec 2940 SCSI adapter>
        aic7870: Single Channel A, SCSI Id=7, 16/253 SCBs

  Vendor: SEAGATE   Model: ST32430N          Rev: 0510
  Type:   Direct-Access                      ANSI SCSI revision: 02
(scsi0:A:0): 8.064MB/s transfers (8.064MHz, offset 15)
  Vendor: RICOH     Model: CD-R/RW MP7040S   Rev: 1.10
  Type:   CD-ROM                             ANSI SCSI revision: 02
scsi0:A:0:0: Tagged Queuing enabled.  Depth 15
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 4197405 512-byte hdwr sectors (2149 MB)
 /dev/scsi/host0/bus0/target0/lun0: p1 p2
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
sr0: scsi3-mmc drive: 20x/20x writer cd/rw xa/form2 cdda tray

David Lang


On Sun, 5 Jan 2003, Justin T. Gibbs wrote:

> Date: Sun, 05 Jan 2003 20:29:07 -0700
> From: Justin T. Gibbs <gibbs@scsiguy.com>
> To: David Lang <david.lang@digitalinsight.com>
> Cc: Paul Rolland <rol@witbe.net>, linux-kernel@vger.kernel.org
> Subject: Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx
>
> > Ok, but it's the only error message I get and the AIX7xxx driver then
> > fails to initialize.
>
> Can you be just a bit more specific?  Actual driver messages are
> usually a big help.
>
> --
> Justin
>

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[Justin T. Gibbs]

> other then the memmap error (in my case device 0:10:0 I get the first
> three lines of the driver init and then nothing. the machine
> completely locks up (driver version on .54 is 6.2.25 but I've
> had this same problem since .50)

Some things to try:

o  Turn on the nmi_watchdog.  See the help file in the kernel Documentation
   director on how to enable it for your system.

o  Compile in the debugging code for the aic7xxx driver and turn on some
   debugging options.  Use your favorite kernel configuration utility to
   enable the debug code and use an aic7xxx command line like:

	aic7xxx=verbose.debug:0x12ff

--
Justin

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[David Lang]

On Sun, 5 Jan 2003, Justin T. Gibbs wrote:

> Date: Sun, 05 Jan 2003 22:00:17 -0700
> From: Justin T. Gibbs <gibbs@scsiguy.com>
> To: David Lang <david.lang@digitalinsight.com>
> Cc: Paul Rolland <rol@witbe.net>, linux-kernel@vger.kernel.org
> Subject: Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx
>
> > other then the memmap error (in my case device 0:10:0 I get the first
> > three lines of the driver init and then nothing. the machine
> > completely locks up (driver version on .54 is 6.2.25 but I've
> > had this same problem since .50)
>
> Some things to try:
>
> o  Turn on the nmi_watchdog.  See the help file in the kernel Documentation
>    director on how to enable it for your system.

I will try this later

> o  Compile in the debugging code for the aic7xxx driver and turn on some
>    debugging options.  Use your favorite kernel configuration utility to
>    enable the debug code and use an aic7xxx command line like:
>
> 	aic7xxx=verbose.debug:0x12ff

I added this to lilo and it gets a series of messages that quickly scroll
off the screen

it starts with slave alloc 0
then starts the DV process and goes from state 0 to state 1, gives a
couple errors that I couldn't get and then goes into a loop

the looping messages are

sending INQ
timeout while doing DV command 12
command completed status=0x90000
entering ahc_linux_dv_transition, state=1, status=0x14005, cmd->result=0x90000
going from state 1 to state 1

thanks for your help, I was beginning to wonder since nobody had responded
to my previous messages.

David Lang

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

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[Justin T. Gibbs]

>> o  Compile in the debugging code for the aic7xxx driver and turn on some
>>    debugging options.  Use your favorite kernel configuration utility to
>>    enable the debug code and use an aic7xxx command line like:
>> 
>> 	aic7xxx=verbose.debug:0x12ff
> 
> I added this to lilo and it gets a series of messages that quickly scroll
> off the screen

I need to see the exact messages.  Can you use a serial console to
capture the messages?  To avoid unwanted command timeouts, you should
run your serial console at a reasonable speed (115200 or faster).

--
Justin

Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx

[Ion Badulescu]

On Sun, 05 Jan 2003 08:50:06 -0700, Justin T. Gibbs <gibbs@scsiguy.com> wrote:
>> Out of this, two problems :
>>  - AIC7xxx fails to use DMA, with :
>> aic7xxx: PCI Device 0:8:0 failed memory mapped test.  Using PIO.
>> scsi0: PCI error Interrupt at seqaddr = 0x3
>> scsi0: Signaled a Target Abort
> 
> This is because your system is violating the PCI spec.  There is
> now an explicit test for this during driver initialization so that
> the driver doesn't unexpectedly fail later.  I can change the driver
> so that it doesn't print out the diagnostic if it would make you
> feel better. 8-)

The problem with the message is that it makes people think PIO vs DMA
(which matters a lot for e.g. IDE), not PIO vs MMIO which is what it
really is, and doesn't matter nearly as much.

Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.