From: uaca@alumni.uv.es
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: aic7xxx broken in 2.5.53/54 ?
Date: Mon, 6 Jan 2003 17:36:25 +0100 [thread overview]
Message-ID: <20030106163624.GA11873@pusa.informat.uv.es> (raw)
In-Reply-To: <274040000.1041869813@aslan.scsiguy.com>
Hi hav
I have to report the same problem, tomorrow I will complete the info,
including bios version and read-only tests on a disk device
At least I can say I've saw the message
> scsi0: PCI error Interrupt at seqaddr = 0x2
> scsi0: Signaled a Target Abort
> scsi1: PCI error Interrupt at seqaddr = 0x2
> scsi1: Signaled a Target Abort
> It would be good to know the chipset on the motherboard. As to why
> the old driver worked, for 6.X.X drivers, you may have just been lucky.
> For 5.X.X drivers, they perform a read after every register write to
> "manually" prevent any byte-merging. These reads are actually more
> expensive than just using PIO. Neither of these older drivers included
> a test to try and catch fishy behavior.
Kernel 2.4.x works fine
now some info about chipset, etc...
00:00.0 Host bridge: Intel Corporation 440GX - 82443GX Host bridge
Flags: bus master, medium devsel, latency 64
Memory at f8000000 (32-bit, prefetchable) [size=64M]
Capabilities: <available only to root>
00:01.0 PCI bridge: Intel Corporation 440GX - 82443GX AGP bridge (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 64
Bus: primary=00, secondary=01, subordinate=02, sec-latency=64
00:0b.0 ATM network controller: FORE Systems Inc PCA-200E
Flags: bus master, medium devsel, latency 64, IRQ 18
Memory at f4000000 (32-bit, non-prefetchable) [size=2M]
Expansion ROM at <unassigned> [disabled] [size=8K]
00:0c.0 SCSI storage controller: Adaptec 7896
Subsystem: Adaptec: Unknown device 0053
Flags: bus master, medium devsel, latency 64, IRQ 19
BIST result: 00
I/O ports at 2000 [disabled] [size=256]
Memory at f4300000 (64-bit, non-prefetchable) [size=4K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: <available only to root>
00:0c.1 SCSI storage controller: Adaptec 7896
Subsystem: Adaptec: Unknown device 0053
Flags: bus master, medium devsel, latency 64, IRQ 19
BIST result: 00
I/O ports at 2400 [disabled] [size=256]
Memory at f4301000 (64-bit, non-prefetchable) [size=4K]
Capabilities: <available only to root>
00:0e.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 08)
Subsystem: Intel Corporation 82559 Fast Ethernet LAN on Motherboard
Flags: bus master, medium devsel, latency 64, IRQ 21
Memory at f4302000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 2800 [size=64]
Memory at f4200000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at <unassigned> [disabled] [size=1M]
Capabilities: <available only to root>
00:12.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
Flags: bus master, medium devsel, latency 0
00:12.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) (prog-if 80 [Master])
Flags: bus master, medium devsel, latency 64
I/O ports at 2860 [size=16]
00:12.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) (prog-if 00 [UHCI])
Flags: bus master, medium devsel, latency 64, IRQ 21
I/O ports at 2840 [size=32]
00:12.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02)
Flags: medium devsel, IRQ 9
00:14.0 VGA compatible controller: Cirrus Logic GD 5480 (rev 23) (prog-if 00 [VGA])
Subsystem: Cirrus Logic CL-GD5480
Flags: bus master, medium devsel, latency 64
Memory at f6000000 (32-bit, prefetchable) [size=32M]
Memory at f4303000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at <unassigned> [disabled] [size=32K]
01:0f.0 PCI bridge: Digital Equipment Corporation DECchip 21150 (rev 06) (prog-if 00 [Normal decode])
Flags: bus master, fast Back2Back, 66Mhz, medium devsel, latency 240
Bus: primary=01, secondary=02, subordinate=02, sec-latency=68
Capabilities: <available only to root>
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping : 3
cpu MHz : 796.559
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1589.24
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping : 3
cpu MHz : 796.559
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1592.52
Debian GNU/Linux: a dream come true
-----------------------------------------------------------------------------
"Computers are useless. They can only give answers." Pablo Picasso
---> Visita http://www.valux.org/ para saber acerca de la <---
---> Asociación Valenciana de Usuarios de Linux <---
next prev parent reply other threads:[~2003-01-06 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 10:16 Dipankar Sarma
2003-01-03 15:14 ` Justin T. Gibbs
2003-01-06 7:32 ` Dipankar Sarma
2003-01-06 16:16 ` Justin T. Gibbs
2003-01-06 16:36 ` uaca [this message]
2003-01-07 11:36 ` uaca
2003-01-08 2:41 ` Tomas Szepe
2003-01-08 4:23 ` Justin T. Gibbs
2003-01-08 10:05 ` Tomas Szepe
2003-01-08 15:39 ` uaca
2003-01-09 11:52 ` David Lang
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=20030106163624.GA11873@pusa.informat.uv.es \
--to=uaca@alumni.uv.es \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®