From: "Dead2" <dead2@circlestorm.org>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Scsi
Date: Tue, 19 Jun 2001 13:00:52 +0200 [thread overview]
Message-ID: <05fd01c0f8af$1d1a4500$d2c0ecd5@dead2> (raw)
In-Reply-To: <Pine.LNX.4.20_heb2.08.0106191305060.1005-100000@pomela2.cs.huji.ac.il>
Attached below: original mail to the 'linux-scsi' list
Please read attachment first.
It seems that the Davicom NIC's is the problem in this system.
I have tried to swap them with new davicom cards, and tried
with only one of them.
Davicom DM9102AF is the chip on all the cards.
Adaptec SCSI 19160 Ultra160, 68/50pin (7892B, rev2)
I changed the Davicom's with Intel cards (same IRQ), and now it works
flawlessly. I think this might be an error worth looking at..
Hans K. Rosbach aka. Dead2
CircleStorm Productions
-START ATTACHMENT-
Hi, i'm getting the following errors constantly while accessing my scsi disk
(10x per second or more)
"Kernel: scsi0: PCI error Interrupt at seqaddr = 0x*"
"Kernel: scsi0: Data Parity Error Detected during address or write data
phase"
(where * is a number, most often 8 or 9)
I'm running Kernel 2.4.6pre1 (also got it with 2.4.5)
Worked fine with the distro's kernel 2.4.0
Hardware:
Adaptec SCSI 19160 Ultra160, 68/50pin (7892B, rev2)
MSI K7T-PRO2 motherboard (VIA chipset)
Amd Duron 750Mhz cpu
Winbond SDRAM (7ns)
2x Davicom PCI 10/100 cards
ATI 3D Rage IIc AGP
The computer is running SuSE 7.1 without X or other fancy
packages, as it is going to run a squid cache server.
The Scsi drivers are compiled into the kernel.
Hans K. Rosbach aka. Dead2
CircleStorm Productions
-END ATTACHMENT-
prev parent reply other threads:[~2001-06-19 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 10:34 [BUG] bug in mmap_kmem Yoav Etsion
2001-06-19 11:00 ` Dead2 [this message]
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='05fd01c0f8af$1d1a4500$d2c0ecd5@dead2' \
--to=dead2@circlestorm.org \
--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