Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 07-12-05, 02:01 PM   #1
MQMan
Registered User
 
Join Date: Jul 2005
Posts: 15
Unhappy SCSI Partiy Errors when using nVidia Driver

Hi,

When I'm using the nVidia driver, version 1.0-7667, I get the following errors when I load the "aic7xxx" module. This is running Slackware 10.1 with the 2.6.10 kernel.

Here's what I get when I "modprobe aic7xxx":

Jul 8 01:08:40 The-Tardis kernel: ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
Jul 8 01:08:40 The-Tardis kernel: <Adaptec 2940 SCSI adapter>
Jul 8 01:08:40 The-Tardis kernel: aic7870: Single Channel A, SCSI Id=7, 16/253 SCBs
Jul 8 01:08:40 The-Tardis kernel:
Jul 8 01:08:47 The-Tardis kernel: scsi0: PCI error Interrupt at seqaddr = 0x7
Jul 8 01:08:47 The-Tardis kernel: scsi0: Data Parity Error Detected during address or write data phase
Jul 8 01:08:54 The-Tardis kernel: scsi0: PCI error Interrupt at seqaddr = 0x8
Jul 8 01:08:54 The-Tardis kernel: scsi0: Data Parity Error Detected during address or write data phase
Jul 8 01:08:57 The-Tardis kernel: (scsi0:A:0): 5.000MB/s transfers (5.000MHz, offset 15)
Jul 8 01:08:59 The-Tardis kernel: Attached scsi tape st0 at scsi0, channel 0, id 0, lun 0
Jul 8 01:08:59 The-Tardis kernel: st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 1048575
Jul 8 01:09:07 The-Tardis kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Jul 8 01:09:07 The-Tardis kernel: scsi0: Data Parity Error Detected during address or write data phase
Jul 8 01:09:13 The-Tardis kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Jul 8 01:09:13 The-Tardis kernel: scsi0: Data Parity Error Detected during address or write data phase
Jul 8 01:09:17 The-Tardis kernel: st0: Block limits 1 - 16777215 bytes.
Jul 8 01:09:24 The-Tardis kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Jul 8 01:09:24 The-Tardis kernel: scsi0: Data Parity Error Detected during address or write data phase
Jul 8 01:09:31 The-Tardis kernel: scsi0: PCI error Interrupt at seqaddr = 0x7
Jul 8 01:09:31 The-Tardis kernel: scsi0: Data Parity Error Detected during address or write data phase
Jul 8 01:09:37 The-Tardis kernel: scsi0: PCI error Interrupt at seqaddr = 0x7
Jul 8 01:09:37 The-Tardis kernel: scsi0: Data Parity Error Detected during address or write data phase
Jul 8 01:09:43 The-Tardis kernel: scsi0: PCI error Interrupt at seqaddr = 0x8
Jul 8 01:09:43 The-Tardis kernel: scsi0: Data Parity Error Detected during address or write data phase

And the errors keep repeating every 8 seconds, or so. After I actually use the drive, the messages change to:

Jul 8 01:10:03 The-Tardis kernel: scsi0: PCI error Interrupt at seqaddr = 0x8
Jul 8 01:10:03 The-Tardis kernel: scsi0: Data Parity Error Detected during address or write data phase
Jul 8 01:10:03 The-Tardis kernel: scsi0: WARNING WARNING WARNING WARNING
Jul 8 01:10:03 The-Tardis kernel: scsi0: Too many PCI parity errors observed as a target.
Jul 8 01:10:03 The-Tardis kernel: scsi0: Some device on this bus is generating bad parity.
Jul 8 01:10:03 The-Tardis kernel: scsi0: This is an error *observed by*, not *generated by*, this controller.
Jul 8 01:10:03 The-Tardis kernel: scsi0: PCI parity error checking has been disabled.
Jul 8 01:10:03 The-Tardis kernel: scsi0: WARNING WARNING WARNING WARNING
Jul 8 01:10:10 The-Tardis kernel: scsi0: PCI error Interrupt at seqaddr = 0x9
Jul 8 01:10:10 The-Tardis kernel: scsi0: Data Parity Error Detected during address or write data phase
Jul 8 01:10:10 The-Tardis kernel: scsi0: WARNING WARNING WARNING WARNING
Jul 8 01:10:10 The-Tardis kernel: scsi0: Too many PCI parity errors observed as a target.
Jul 8 01:10:10 The-Tardis kernel: scsi0: Some device on this bus is generatingbad parity.
Jul 8 01:10:10 The-Tardis kernel: scsi0: This is an error *observed by*, not *generated by*, this controller.
Jul 8 01:10:10 The-Tardis kernel: scsi0: PCI parity error checking has been disabled.
Jul 8 01:10:10 The-Tardis kernel: scsi0: WARNING WARNING WARNING WARNING
Jul 8 01:11:07 The-Tardis kernel: scsi0: PCI error Interrupt at seqaddr = 0x8
Jul 8 01:11:07 The-Tardis kernel: scsi0: Data Parity Error Detected during address or write data phase
Jul 8 01:11:07 The-Tardis kernel: scsi0: WARNING WARNING WARNING WARNING
Jul 8 01:11:07 The-Tardis kernel: scsi0: Too many PCI parity errors observed as a target.
Jul 8 01:11:07 The-Tardis kernel: scsi0: Some device on this bus is generating bad parity.
Jul 8 01:11:07 The-Tardis kernel: scsi0: This is an error *observed by*, not *generated by*, this controller.
Jul 8 01:11:07 The-Tardis kernel: scsi0: PCI parity error checking has been disabled.
Jul 8 01:11:07 The-Tardis kernel: scsi0: WARNING WARNING WARNING WARNING

And again, they repeat every 8 seconds.

Any thoughts on what the problem might be, or how I can fix it. I really would like to go back to using a driver other than the default "nv".

Cheers.
MQMan is offline   Reply With Quote
Old 07-12-05, 02:32 PM   #2
MQMan
Registered User
 
Join Date: Jul 2005
Posts: 15
Default Re: SCSI Partiy Errors when using nVidia Driver

Forgot to mention, this is what /proc/pci says about the card:

VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev 178).

Cheers.
MQMan is offline   Reply With Quote
Old 07-12-05, 07:41 PM   #3
energyman76b
Registered User
 
Join Date: Dec 2002
Location: Clausthal/Germany
Posts: 1,104
Default Re: SCSI Partiy Errors when using nVidia Driver

Hi,

I don't have that problems, but maybe you could sove your problems, by check that <our card has an interrupt for itself, that it has not to share with anybody?
energyman76b is offline   Reply With Quote
Old 07-28-05, 05:05 PM   #4
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: SCSI Partiy Errors when using nVidia Driver

This sounds like an SBIOS IRQ assignment/management problem to me. First thing I'd suggest is making sure that you've got the most recent motherboard SBIOS applied.

If that checks out, you could try moving the SCSI card to a different PCI slot.

Also, what does /proc/interrupts look like when you've got the nvidia driver loaded?
netllama is offline   Reply With Quote
Old 07-28-05, 07:08 PM   #5
bck
Registered User
 
Join Date: Jan 2005
Posts: 23
Default Re: SCSI Partiy Errors when using nVidia Driver

If you are getting pci parity errors, as suggested by your error log, then the problem surely has nothing to do with interrupt handling, but rather that the scsi card and the nvidia card are on the same physical bus and somehow the nvidia card is disturbing the communications with the scsi card. Amazing that this could be driver dependent. Either one of the cards isn't robustly following the pci rules, or perhaps the bus is too heavily loaded or one of the cards isn't quite seated properly. Since the pci "bus" doesn't allow many devices on the same physical bus, maybe it is a power problem. Perhaps you can move the scsi card to a different slot and end up serviced by a different bridge chip. Maybe it is a hardware problem - hard to see why it would depend on the driver. Parity is only one bit for 36 lines - could mean you are writing to random pci addresses, meaning you have already a fatal cancer in your system.
bck is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
nvidia driver quality decrease? legluondunet NVIDIA Linux 17 06-26-12 10:03 AM
NVIDIA Driver Installation flores.facundo NVIDIA Linux 2 06-24-12 08:37 AM
Need Help Installing NVIDIA Tesla M2070Q in Linux RHEL5 Ferianto85 NVIDIA Linux 0 05-18-12 08:35 PM
Getting the proprietary nvidia driver to run with Debian 3.0 r0 (woody) Katchina404 NVIDIA Linux 9 01-12-03 08:49 AM
nvidia + 2.4.19 gentoo = messed up ulukay NVIDIA Linux 18 11-01-02 11:58 PM

All times are GMT -5. The time now is 11:32 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.