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

Newegg Daily Deals

Reply
 
Thread Tools
Old 01-12-09, 04:21 PM   #1
ozra
Registered User
 
Join Date: Nov 2008
Posts: 10
Default 8200 IGP: NVIDIA driver cause SATA errors as below. Proven. Yes it can!!

Good day everybody.

On Ubuntu 8.10:

Has anybody encountered SATA errors when they load the Proprietary 173 or 177 NVIDIA drivers? The same happens with NVIDIA binary drivers 180.11 / 180.18 and 180.22.

The errors disappear if loading the native Ubuntu Intrepid VESA driver instead of the NVIDIA supplied driver.

Symptoms:

I noticed "hard resetting link" and SError: { Handshk } SATA errors in dmesg on my Intrepid 8.10 2.6.27-11-generic up to date on 12 Jan 2009 Ubuntu box. (Desktop i386)

It is a Nvidia 8200 Gigabyte GA-M78SM-S2H motherboard (latest Bios installed today). 4 gig Ram. AMD x2 3000 MHz CPU. 1 x 300GB Maxtor SATA HD + 2 x 750GB Western Digital SATA HD's. Pioneer SATA DVD writer.

I have apt-get install bonnie to test my HD's

I have the latest NVIDIA binary 180.22 driver installed.

Running bonnie via terminal window in GDM to exercise my HD's I will see dmesg running lots of the following errors ONLY for the two 750 GB HD's (/dev/sdb and /dev/sdc )(no errors get logged for /dev/sda):

[ 247.123447] ata2.00: exception Emask 0x10 SAct 0x201 SErr 0x400000 action 0x6 frozen
[ 247.123452] ata2.00: irq_stat 0x08000000, interface fatal error
[ 247.123455] ata2: SError: { Handshk }
[ 247.123459] ata2.00: cmd 61/00:00:cf:ff:2e/04:00:05:00:00/40 tag 0 ncq 524288 out
[ 247.123460] res 40/00:04:cf:ff:2e/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
[ 247.123462] ata2.00: status: { DRDY }
[ 247.123466] ata2.00: cmd 61/40:48:e7:05:2f/02:00:05:00:00/40 tag 9 ncq 294912 out
[ 247.123467] res 40/00:04:cf:ff:2e/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
[ 247.123469] ata2.00: status: { DRDY }
[ 247.123473] ata2: hard resetting link
[ 247.604021] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 247.605562] ata2.00: configured for UDMA/133
[ 247.605575] ata2: EH complete
[ 247.605828] sd 1:0:0:0: [sdb] 1465149168 512-byte hardware sectors (750156 MB)
[ 247.605842] sd 1:0:0:0: [sdb] Write Protect is off
[ 247.605845] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 247.605863] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

The above is an example but gets logged for both sdb and sdc.

I bought a new PSU: Thermaltake 550W (TR2-550) to replace the 300W PSU but the above continues regardless of which PSU I use.

If I kill GDM (/etc/init.d/gdm stop) and run bonnie on either sdb or sdc or on all 3 drives (multiple terminals (F1/F2/F3 and F4 to watch dmesg / messages) simultaneously, no errors get logged. start GDM and the errors multiply continuously. (Except for no errors on sda as stated previously)

Please note: sda is my boot. sdb1 is not in use but mounted /media/storage1 and sdc1 is mounted /media/storage2. sdc1 is used as myth data drive.

If I boot off the Ubuntu 8.10 i386 desktop live CD into GDM: Apt-get install bonnie etc and then run tests, no errors get logged for ANY drives.

Errors only get logged for sdb and sdc when booting off sda (sda1) and with GDM running (NVIDIA driver 180.22)

Using the VESA driver stops the SATA errors.

Installing Proprietary driver 173 or 177 causes the errors to re-appear.

Reverting back to the VESA driver causes the errors to stop.

Installing the binary 180.11 / 180.18 / 180.22 driver causes the errors to re-appear.

Reverting back to the VESA driver causes the errors to stop.

Any suggestions on what I can do to stop the SATA reset errors whilst using the 180.22 driver?


It has now started to cause file corruption on my myth data drive (sdc) fsck fixes it and it is ok for a couple of days after that until it gets too much. ONLY the 750GB drives are affected. Disabling NCQ ( $ echo 1 > /sys/block/sdb/device/queue_depth) and Write caching (hdparm -W0 /dev/sdb)on these two drives does not stop the errors either.

Thank You kindly.

Here is some more info:

myth@myth:~$ uname -r
2.6.27-11-generic
myth@myth:~$ sudo hdparm -i /dev/sda
[sudo] password for myth:

/dev/sda:

Model=Maxtor 6L300S0 , FwRev=BANC1G10, SerialNo=L60DMQWG
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=586114704
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: ATA/ATAPI-7 T13 1532D revision 0: ATA/ATAPI-1,2,3,4,5,6,7

* signifies the current active mode

myth@myth:~$ sudo hdparm -i /dev/sdb

/dev/sdb:

Model=WDC WD7500AACS-00D6B0 , FwRev=01.01A01, SerialNo= WD-WCAU41064087
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
BuffType=unknown, BuffSize=16384kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=1465149168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 udma6
AdvancedPM=no WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7

* signifies the current active mode

(The above was running in udma6 mode until the errors start, then it negotiates udma5)

myth@myth:~$ sudo hdparm -i /dev/sdc

/dev/sdc:

Model=WDC WD7500AACS-00D6B0 , FwRev=01.01A01, SerialNo= WD-WCAU40908795
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
BuffType=unknown, BuffSize=16384kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=1465149168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=no WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7

* signifies the current active mode

myth@myth:~$
myth@myth:~$

dmesg excerpt:

[ 247.123447] ata2.00: exception Emask 0x10 SAct 0x201 SErr 0x400000 action 0x6 frozen
[ 247.123452] ata2.00: irq_stat 0x08000000, interface fatal error
[ 247.123455] ata2: SError: { Handshk }
[ 247.123459] ata2.00: cmd 61/00:00:cf:ff:2e/04:00:05:00:00/40 tag 0 ncq 524288 out
[ 247.123460] res 40/00:04:cf:ff:2e/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
[ 247.123462] ata2.00: status: { DRDY }
[ 247.123466] ata2.00: cmd 61/40:48:e7:05:2f/02:00:05:00:00/40 tag 9 ncq 294912 out
[ 247.123467] res 40/00:04:cf:ff:2e/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
[ 247.123469] ata2.00: status: { DRDY }
[ 247.123473] ata2: hard resetting link
[ 247.604021] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 247.605562] ata2.00: configured for UDMA/133
[ 247.605575] ata2: EH complete
[ 247.605828] sd 1:0:0:0: [sdb] 1465149168 512-byte hardware sectors (750156 MB)
[ 247.605842] sd 1:0:0:0: [sdb] Write Protect is off
[ 247.605845] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 247.605863] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 247.743411] ata2.00: exception Emask 0x10 SAct 0x7ffef SErr 0x400000 action 0x6 frozen

Last edited by ozra; 01-13-09 at 03:44 PM. Reason: Further testing.
ozra is offline   Reply With Quote
Old 01-13-09, 02:22 PM   #2
ozra
Registered User
 
Join Date: Nov 2008
Posts: 10
Unhappy Re: 8200: Can using NVIDIA driver cause SATA errors as below? Ubuntu 8.10

OK. Problem Solved.

The answer is yes that 8200 IGP with NVIDIA drivers can cause the SATA errors.

I have swopped the 8200 IGP with a PCIE 7200 add-in card and a 7300 add-in card.

The SATA errors stop if I use the external add-in VGA cards.

The bonus is that HDMI video out that has last worked in driver 173 for the 8200 IGP is now working again on the add-in cards 7200 and 7300 using driver 180.22.

Using 8200 IGP the HDMI video out stopped working in any driver after 173.

Good stuff NVIDIA. How do you break basic things that WERE working?

Keep adding features but don't fix basic functionality.

The HDMI video out problem is not new either. See how many users with Laptops trying to use HDMI out are having problems. The NVIDIA moderators on here have acknowledged the problem. It is not fixed yet but funnily enough, it is also not mentioned in existing problems in the README's.

8200 IGP was touted to be perfect for HTPC.

Lesson Learnt regarding NVIDIA.

Thank You

Regards
ozra is offline   Reply With Quote
Old 01-19-09, 11:11 AM   #3
kconger
Registered User
 
Join Date: Mar 2008
Posts: 3
Unhappy Re: 8200: Can using NVIDIA driver cause SATA errors as below? Ubuntu 8.10

I just got a new board, MSI K9N2GM-FIH it has an integrated 8200. Its running Ubuntu 8.10 with the 180.22. I see the same errors start when I run mythfrontend using Xv or VDPAU. When running mythfrontend with Xv enabled I see high Xorg and mythfrontend usage also. We VPDAU low usage but same errors.

Previously I had an Abit AN-M2HD with an integrated 7050 running the same system above I just swapped the boards. These errors don't occur.

Here are the errors I get in dmesg:
[ 140.249127] ata7.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 140.249136] ata7.01: BMDMA stat 0x64
[ 140.249140] ata7.01: cmd ca/00:00:d7:cc:0c/00:00:00:00:00/f6 tag 0 dma 131072 out
[ 140.249141] res 51/84:00:d6:cd:0c/00:00:00:00:00/f6 Emask 0x10 (ATA bus error)
[ 140.249144] ata7.01: status: { DRDY ERR }
[ 140.249145] ata7.01: error: { ICRC ABRT }
[ 140.249166] ata7: soft resetting link
[ 140.421647] ata7: nv_mode_filter: 0x3f01f&0x3f01f->0x3f01f, BIOS=0x3f000 (0xc6c60000) ACPI=0x3f01f (20:20:0x15)
[ 140.421653] ata7: nv_mode_filter: 0x3f01f&0x3f01f->0x3f01f, BIOS=0x3f000 (0xc6c60000) ACPI=0x3f01f (20:20:0x15)
[ 140.437650] ata7.00: configured for UDMA/100
[ 140.453878] ata7.01: configured for UDMA/100
[ 140.453895] ata7: EH complete
[ 140.455369] sd 6:0:0:0: [sdc] 234441648 512-byte hardware sectors (120034 MB)
[ 140.456828] sd 6:0:0:0: [sdc] Write Protect is off
[ 140.456832] sd 6:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 140.457673] sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 140.457726] sd 6:0:1:0: [sdd] 234441648 512-byte hardware sectors (120034 MB)
[ 140.457752] sd 6:0:1:0: [sdd] Write Protect is off
[ 140.457753] sd 6:0:1:0: [sdd] Mode Sense: 00 3a 00 00
[ 140.457797] sd 6:0:1:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 140.457841] sd 6:0:0:0: [sdc] 234441648 512-byte hardware sectors (120034 MB)
[ 140.457863] sd 6:0:0:0: [sdc] Write Protect is off
[ 140.457864] sd 6:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 140.457907] sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 140.457952] sd 6:0:1:0: [sdd] 234441648 512-byte hardware sectors (120034 MB)
[ 140.457976] sd 6:0:1:0: [sdd] Write Protect is off
[ 140.457978] sd 6:0:1:0: [sdd] Mode Sense: 00 3a 00 00
[ 140.458024] sd 6:0:1:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
kconger is offline   Reply With Quote
Old 02-01-09, 12:06 AM   #4
MiLK_MaN
Registered User
 
Join Date: Jan 2009
Posts: 4
Default Re: 8200: Can using NVIDIA driver cause SATA errors as below? Ubuntu 8.10

Hello Nvidia,

Can you please address this issue? I also have a GeForce 8200 on board gpu, and as soon as I start using mplayer with vdpau, SATA resets occur all over the place, causing video the be unplayable....

Feb 1 16:04:04 htpc-livingroom kernel: [ 1595.519642] ata1: hard resetting link
Feb 1 16:04:05 htpc-livingroom kernel: [ 1596.000027] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 1 16:04:05 htpc-livingroom kernel: [ 1596.018379] ata1.00: configured for UDMA/133
Feb 1 16:04:05 htpc-livingroom kernel: [ 1596.018393] ata1: EH complete
Feb 1 16:04:05 htpc-livingroom kernel: [ 1596.018444] sd 0:0:0:0: [sda] 976771055 512-byte hardware sectors: (500 GB/465 GiB)
Feb 1 16:04:05 htpc-livingroom kernel: [ 1596.018458] sd 0:0:0:0: [sda] Write Protect is off
Feb 1 16:04:05 htpc-livingroom kernel: [ 1596.018477] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 1 16:05:25 htpc-livingroom kernel: [ 1676.893423] ata3: hard resetting link
Feb 1 16:05:26 htpc-livingroom kernel: [ 1677.376527] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 1 16:05:26 htpc-livingroom kernel: [ 1677.380892] ata3.00: configured for UDMA/66
Feb 1 16:05:26 htpc-livingroom kernel: [ 1677.416032] ata3.00: configured for UDMA/66
Feb 1 16:05:26 htpc-livingroom kernel: [ 1677.416047] ata3: EH complete
Feb 1 16:05:58 htpc-livingroom kernel: [ 1702.750961] ata1: hard resetting link
Feb 1 16:05:58 htpc-livingroom kernel: [ 1703.456036] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 1 16:05:58 htpc-livingroom kernel: [ 1703.456044] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40)
Feb 1 16:05:58 htpc-livingroom kernel: [ 1708.456029] ata1: hard resetting link
Feb 1 16:05:58 htpc-livingroom kernel: [ 1708.940023] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 1 16:05:58 htpc-livingroom kernel: [ 1708.945592] ata1.00: configured for UDMA/133
Feb 1 16:05:58 htpc-livingroom kernel: [ 1708.949455] ata1.00: configured for UDMA/133
Feb 1 16:05:58 htpc-livingroom kernel: [ 1708.949461] ata1: EH complete
Feb 1 16:05:58 htpc-livingroom kernel: [ 1708.949502] sd 0:0:0:0: [sda] 976771055 512-byte hardware sectors: (500 GB/465 GiB)
Feb 1 16:05:58 htpc-livingroom kernel: [ 1708.949516] sd 0:0:0:0: [sda] Write Protect is off
Feb 1 16:05:58 htpc-livingroom kernel: [ 1708.949535] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 1 16:05:58 htpc-livingroom kernel: [ 1708.949554] sd 0:0:0:0: [sda] 976771055 512-byte hardware sectors: (500 GB/465 GiB)
Feb 1 16:05:58 htpc-livingroom kernel: [ 1708.949564] sd 0:0:0:0: [sda] Write Protect is off
Feb 1 16:05:58 htpc-livingroom kernel: [ 1708.949582] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 1 16:10:00 htpc-livingroom kernel: [ 1951.023964] ata3: hard resetting link
Feb 1 16:10:00 htpc-livingroom kernel: [ 1951.504527] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 1 16:10:00 htpc-livingroom kernel: [ 1951.509002] ata3.00: configured for UDMA/66
Feb 1 16:10:00 htpc-livingroom kernel: [ 1951.545037] ata3.00: configured for UDMA/66
Feb 1 16:10:00 htpc-livingroom kernel: [ 1951.545051] ata3: EH complete
Feb 1 16:10:44 htpc-livingroom kernel: [ 1995.733711] ata1: limiting SATA link speed to 1.5 Gbps
Feb 1 16:10:44 htpc-livingroom kernel: [ 1995.733739] ata1: hard resetting link
Feb 1 16:10:45 htpc-livingroom kernel: [ 1996.216524] ata1: SATA link up <unknown> (SStatus 103 SControl 310)
Feb 1 16:10:45 htpc-livingroom kernel: [ 1996.229321] ata1.00: configured for UDMA/133
Feb 1 16:10:45 htpc-livingroom kernel: [ 1996.229332] ata1: EH complete
Feb 1 16:10:45 htpc-livingroom kernel: [ 1996.229373] sd 0:0:0:0: [sda] 976771055 512-byte hardware sectors: (500 GB/465 GiB)
Feb 1 16:10:45 htpc-livingroom kernel: [ 1996.229387] sd 0:0:0:0: [sda] Write Protect is off
Feb 1 16:10:45 htpc-livingroom kernel: [ 1996.229407] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Even the DVD drive is being reset, and its not even in use at the time.

I have tried 180.22 and 180.27, both display the same issue. I have also tried both 2.6.27 and 2.6.28 (from jaunty), no different either, so it has to be the display drivers causing it.
MiLK_MaN is offline   Reply With Quote
Old 02-21-09, 03:56 PM   #5
scytheshy
Registered User
 
Join Date: Feb 2009
Posts: 1
Default Re: 8200: Can using NVIDIA driver cause SATA errors as below? Ubuntu 8.10

I have no driver support for my board. I can't get my sata hard drives or dvdr to work at all with ubuntu. I had to plug in IDE cables into an old hard drive in order to load 8.10. Any help getting my sata drives to even be noticed would be greatly helpful.
scytheshy is offline   Reply With Quote
Old 03-26-09, 11:15 PM   #6
pcjason
Registered User
 
Join Date: Dec 2007
Posts: 17
Default Re: 8200: Can using NVIDIA driver cause SATA errors as below? Ubuntu 8.10

Did anybody ever get anywhere with this? I just replaced my 250G PATA drive in my HTPC with a 1TB SATA Samsung drive and am now seeing this issue using an 8200 IGP. I swear, this chipset has been a complete nightmare for me in linux! I would capture a log, but I can't because my drive always falls back to read only mode!
pcjason is offline   Reply With Quote
Old 03-27-09, 04:12 PM   #7
thefirstm
Registered User
 
Join Date: Feb 2009
Posts: 226
Default Re: 8200: Can using NVIDIA driver cause SATA errors as below? Ubuntu 8.10

Can people who are affected by this problem please post the output of "cat /proc/interrupts" ? I have a theory that I would like to test.
thefirstm is offline   Reply With Quote
Old 03-27-09, 07:08 PM   #8
MiLK_MaN
Registered User
 
Join Date: Jan 2009
Posts: 4
Default Re: 8200: Can using NVIDIA driver cause SATA errors as below? Ubuntu 8.10

Quote:
Originally Posted by thefirstm View Post
Can people who are affected by this problem please post the output of "cat /proc/interrupts" ? I have a theory that I would like to test.
root@htpc-livingroom:~# cat /proc/interrupts
CPU0 CPU1
0: 127 2971 IO-APIC-edge timer
1: 0 2 IO-APIC-edge i8042
6: 0 5 IO-APIC-edge floppy
7: 1 0 IO-APIC-edge
8: 0 1 IO-APIC-edge rtc0
9: 0 0 IO-APIC-fasteoi acpi
14: 0 0 IO-APIC-edge pata_amd
15: 0 0 IO-APIC-edge pata_amd
16: 0 0 IO-APIC-fasteoi uhci_hcd:usb6
17: 0 0 IO-APIC-fasteoi uhci_hcd:usb7
18: 96459 79001149 IO-APIC-fasteoi ehci_hcd:usb3
20: 21018 2300838 IO-APIC-fasteoi ohci_hcd:usb4, nvidia
21: 145148 18641344 IO-APIC-fasteoi ehci_hcd:usb2, HDA Intel
22: 0 3 IO-APIC-fasteoi ehci_hcd:usb1
23: 10 1823 IO-APIC-fasteoi ohci_hcd:usb5
2302: 406721 51388952 PCI-MSI-edge eth0
2303: 23445 2602113 PCI-MSI-edge ahci
NMI: 0 0 Non-maskable interrupts
LOC: 77456364 157289184 Local timer interrupts
RES: 9108428 2528746 Rescheduling interrupts
CAL: 3597 4280 Function call interrupts
TLB: 120918 111486 TLB shootdowns
SPU: 0 0 Spurious interrupts
ERR: 1
MIS: 0

Im trying the new 185.x nvidia drivers, still happening with these too. This really only occurs for me when vdpau is in use within mythtv or mplayer, if I use something other than vdpau, I dont tend to see the errors as often.
MiLK_MaN is offline   Reply With Quote

Old 03-31-09, 10:01 PM   #9
ozra
Registered User
 
Join Date: Nov 2008
Posts: 10
Default Re: 8200: Can using NVIDIA driver cause SATA errors as below? Ubuntu 8.10

Quote:
Originally Posted by MiLK_MaN View Post
This really only occurs for me when vdpau is in use within mythtv or mplayer, if I use something other than vdpau, I dont tend to see the errors as often.
Try using bonnie to stress test your SATA HD's to see whether it occurs in other situations.

It should NEVER reset under normal/everyday situations, even when using Bonnie or VDPAU.

I have upgraded from a 7200/7300 PCIE card to a 9400 Card (for VDPAU) and running Bonnie over and over, have not seen my problem return with 8200 IGP disabled.

Using 8200 IGP, I get SATA disconnect errors (randomly under Idle situations) that I can replicate by running Bonnie. Disconnect errors instantly. So under moderate to high data throughput situations to SATA. I also have no HDMI video out on the 8200IGP. Eitther by using HDMI straight cable or DVI to HDMI converter. To use HDMI video out on 8200IGP I have to revert back to driver 173.x. Which fixes HDMI out but introduces SATA Disconnect Errors.

Using VESA driver and not NVIDIA driver stops the SATA errors.

Conclusion:

Using 8200 IGP:
All NVIDIA drivers causes SATA disconnect errors. HDMI video out stops working after driver version 173.x
SATA disconnect Errors stop when using VESA driver.


Using any NVIDIA Add-In PCIE card and disabling 8200IGP:
No SATA disconnect errors at all when using VESA or NVIDIA drivers. Even when stressing the HD's

HDMI Video out works with all drivers.

Good Luck
ozra is offline   Reply With Quote
Old 04-02-09, 01:56 AM   #10
pcjason
Registered User
 
Join Date: Dec 2007
Posts: 17
Default Re: 8200: Can using NVIDIA driver cause SATA errors as below? Ubuntu 8.10

Can anybody who is having this issue please post the hardware configuration that you are using? I'm wondering if this is possibly related to a certain motherboard vendor/bios version or hard drive vendor/firmware version. I have been digging at this for the last few days and have finally given up and bought a SATA PCI card just so I could actually use my computer, but this issue is still very bothersome. Let me kick things off:

Motherboard: Gigabyte GA-M78SM-S2H
BIOS Version: F3H (latest as of 4/1/09)
Hard Drive: HD103UJ
Hard Drive Firmware: 1AA01113
CPU: AMD Sempron(tm) Processor 3200+
Memory: 2GB Patriot DDR 6400 (1x2G)
DVD Drive: HL-DT-STDVD-ROM GDR8162B (PATA, but have disconnected it and still seen the errors)

The attached log is with the offending drive connected, but booting from a PATA drive.
Attached Files
File Type: gz nvidia-bug-report.log.gz (31.3 KB, 126 views)
pcjason is offline   Reply With Quote
Old 04-02-09, 04:01 AM   #11
tzp
Registered User
 
tzp's Avatar
 
Join Date: Sep 2007
Location: Hungary
Posts: 92
Exclamation Re: 8200: Can using NVIDIA driver cause SATA errors as below? Ubuntu 8.10

Quote:
Originally Posted by scytheshy View Post
I have no driver support for my board. I can't get my sata hard drives or dvdr to work at all with ubuntu. I had to plug in IDE cables into an old hard drive in order to load 8.10. Any help getting my sata drives to even be noticed would be greatly helpful.
Also check your motherboard chipset. If it's nForce: This page gives some hints on which kernel modules to use as drivers for nForce based MB-s.
tzp is offline   Reply With Quote
Old 04-03-09, 07:33 PM   #12
pcjason
Registered User
 
Join Date: Dec 2007
Posts: 17
Default Re: 8200: Can using NVIDIA driver cause SATA errors as below? Ubuntu 8.10

Could somebody from NVIDIA at least confirm that they have seen this thread? I posted my log file and I am willing to try anything to help with the debugging.
pcjason 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
GT650M not recognized by 295.59 Driver on Ubuntu 12.04 hvontres NVIDIA Linux 13 06-22-12 01:33 PM
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 05:39 AM.


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