John Stoffel wrote:
What happens when you just have ONE disk connected to the motherboard
controller, and the rest connected to PCI controllers? Does it crap
out then? You've just such a nice repeatable problem across
motherboards that it's a shame to waste this debugging time.
Sorry, I
Prakash Punnoor wrote:
I don't have exaclty the same hw, but the same chipset and I don't have any
problems - even with the swncq patch applied. Do you have an hpet? If not,
try booting with acpi_use_time_override. My system won't work with skipping
the override.
Hi , I reconnected and
Prakash Punnoor wrote:
I don't have exaclty the same hw, but the same chipset and I don't have any
problems - even with the swncq patch applied. Do you have an hpet? If not,
try booting with acpi_use_time_override. My system won't work with skipping
the override.
Hi , I reconnected and
John Stoffel wrote:
What happens when you just have ONE disk connected to the motherboard
controller, and the rest connected to PCI controllers? Does it crap
out then? You've just such a nice repeatable problem across
motherboards that it's a shame to waste this debugging time.
Sorry, I
hands on / change to another (non-nvidia) chipset in a day or two, as
the sata_nv with this chipset apparently isn't working.
(Or have anyone EVER been successful with the latest kernel/driver on
this HW)?
Attaching everything relevant from /var/log/messages...
Jon Ivar Rykkelid wrote:
I'm
Jeff Garzik wrote:
Jon Ivar Rykkelid wrote:
I'm going to test another (identical) motherboard this evening to
establish whether it could be a HW-issue.
Not just motherboard. It is more likely to be a cable, drive or PSU
problem.
It is NOT the PSU, nor is it cables, as all the drives work
Prakash Punnoor wrote:
I don't think it will matter, as adma doesn't affect MCP51, but only nforce4.
So I'd look for other trouble makers.
Robert told me. (And you're correct - It didn't help).
I'm going to test another (identical) motherboard this evening to
establish whether it could be
wrote:
Jeff Garzik wrote:
Jon Ivar Rykkelid wrote:
Hi,
I now tested with the adma=0 option, but if anything I got a crash
quicker than before. Same error message started coming in, but this
time the system hung before I was able to capture the log as well
(but I saw the error, and it was the sa
:
Jon Ivar Rykkelid wrote:
Hi,
I now tested with the adma=0 option, but if anything I got a crash
quicker than before. Same error message started coming in, but this
time the system hung before I was able to capture the log as well
(but I saw the error, and it was the same as before, except
Prakash Punnoor wrote:
I don't think it will matter, as adma doesn't affect MCP51, but only nforce4.
So I'd look for other trouble makers.
Robert told me. (And you're correct - It didn't help).
I'm going to test another (identical) motherboard this evening to
establish whether it could be
Jeff Garzik wrote:
Jon Ivar Rykkelid wrote:
I'm going to test another (identical) motherboard this evening to
establish whether it could be a HW-issue.
Not just motherboard. It is more likely to be a cable, drive or PSU
problem.
It is NOT the PSU, nor is it cables, as all the drives work
hands on / change to another (non-nvidia) chipset in a day or two, as
the sata_nv with this chipset apparently isn't working.
(Or have anyone EVER been successful with the latest kernel/driver on
this HW)?
Attaching everything relevant from /var/log/messages...
Jon Ivar Rykkelid wrote:
I'm
? - Can anyone confirm
that the driver is working for this HW? I would feel awkward to try to
claim a warranty replacement if it is proved that the HW is OK after
all, and the problem is with the linux-driver...
BR
Jon Ivar
Jeff Garzik wrote:
Jon Ivar Rykkelid wrote:
Hi,
I now tested
it was
the ata3-channel that first started acting up..) - To remind you all
what this is about, I have reattached the log that I originally captured...
Any help / clever suggestions is appreciated.
Jon Ivar Rykkelid wrote:
I fixed /etc/modprobe.conf to include the following two lines:
"
Resending, as my first attempts contained HTML and was blocked...
Tejun Heo wrote:
Jon Ivar Rykkelid wrote:
Thanks for the suggestion, but sata_nv is not built modular in my
current kernel, so "no can do" at the moment
(However, if some expert REALLY thinks this will fix
Jeff Garzik wrote:
Jon Ivar Rykkelid wrote:
Hi, I'm resending (didn't see my first attempt appear on the maillist):
I'm having serious disk-issues when using the on-board nvidia controller
for my HDDs (My motherboard is a Gigabyte GA-N650SLI-DS4 with nvidia
chipset, cpu is intel Core2Quad
Hi, I was told to forward my error report to this address.
I am keen to test again if someone has a good suggestion / updated
driver etc... (Give me a couple of days in that case...)
-
Hi,
I'm having serious disk-issues when using the on-board nvidia controller
for my HDDs (My
Hi, I'm resending (didn't see my first attempt appear on the maillist):
I'm having serious disk-issues when using the on-board nvidia controller
for my HDDs (My motherboard is a Gigabyte GA-N650SLI-DS4 with nvidia
chipset, cpu is intel Core2Quad)
excerpt from "lspci":
00:0d.0 IDE interface:
Hi, I'm resending (didn't see my first attempt appear on the maillist):
I'm having serious disk-issues when using the on-board nvidia controller
for my HDDs (My motherboard is a Gigabyte GA-N650SLI-DS4 with nvidia
chipset, cpu is intel Core2Quad)
excerpt from lspci:
00:0d.0 IDE interface:
Hi, I was told to forward my error report to this address.
I am keen to test again if someone has a good suggestion / updated
driver etc... (Give me a couple of days in that case...)
-
Hi,
I'm having serious disk-issues when using the on-board nvidia controller
for my HDDs (My
Jeff Garzik wrote:
Jon Ivar Rykkelid wrote:
Hi, I'm resending (didn't see my first attempt appear on the maillist):
I'm having serious disk-issues when using the on-board nvidia controller
for my HDDs (My motherboard is a Gigabyte GA-N650SLI-DS4 with nvidia
chipset, cpu is intel Core2Quad
Resending, as my first attempts contained HTML and was blocked...
Tejun Heo wrote:
Jon Ivar Rykkelid wrote:
Thanks for the suggestion, but sata_nv is not built modular in my
current kernel, so no can do at the moment
(However, if some expert REALLY thinks this will fix things, I
it was
the ata3-channel that first started acting up..) - To remind you all
what this is about, I have reattached the log that I originally captured...
Any help / clever suggestions is appreciated.
Jon Ivar Rykkelid wrote:
I fixed /etc/modprobe.conf to include the following two lines:
alias
? - Can anyone confirm
that the driver is working for this HW? I would feel awkward to try to
claim a warranty replacement if it is proved that the HW is OK after
all, and the problem is with the linux-driver...
BR
Jon Ivar
Jeff Garzik wrote:
Jon Ivar Rykkelid wrote:
Hi,
I now tested
24 matches
Mail list logo
