public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Ivar Rykkelid <jonry@pvv.org>
To: linux-kernel@vger.kernel.org
Cc: Prakash Punnoor <prakash@punnoor.de>,
	Robert Hancock <hancockr@shaw.ca>, Tejun Heo <htejun@gmail.com>,
	Jeff Garzik <jeff@garzik.org>
Subject: Re: sata_nv issues with MCP51 SATA controller
Date: Sat, 15 Sep 2007 12:14:34 +0200	[thread overview]
Message-ID: <46EBB08A.5050709@pvv.org> (raw)
In-Reply-To: <200709150912.28358.prakash@punnoor.de>

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 rebooted with the kernel option 
"acpi_use_timer_override" (this is the correct spelling, isn't it? - 
Kernel didn't complain.). Didn't help, the same error received as 
before. - I'll have to connect all disks back to my PCI-connected SATA 
controllers and start rebuilding my RAID yet again.

It seems random which disk is first affected (This far, I know that it 
has happened to ata1, ata3 and ata4, three of my potential disks) - I 
guess it just happens to the disk that is being used at the moment when 
the driver / controller acts up.)

I'm about to give in. I think I'll try to replace both ( Gigabyte 
GA-N650SLI-DS4 ) motherboards, as the driver simply isn't working for 
the on-board controller of these boards. Could be a combination of the 
controllers and some other HW on the motherboards of course, but all is 
working when I connect all disks to my non-nvidia controllers. - Guess 
I'll opt for a motherboard with an intel-chipset after all...

BR
Jon Ivar

  reply	other threads:[~2007-09-15 10:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13  7:46 sata_nv issues with MCP51 SATA controller Jon Ivar Rykkelid
2007-09-13 14:20 ` Jeff Garzik
2007-09-13 15:05   ` Jon Ivar Rykkelid
2007-09-13 15:14     ` Tejun Heo
2007-09-13 18:01       ` Jon Ivar Rykkelid
2007-09-13 19:26         ` Jon Ivar Rykkelid
2007-09-13 19:54           ` Jeff Garzik
2007-09-13 21:15             ` Jon Ivar Rykkelid
2007-09-14  0:37             ` Robert Hancock
2007-09-14 12:10               ` Jon Ivar Rykkelid
2007-09-14 13:29         ` Prakash Punnoor
2007-09-14 14:17           ` Jon Ivar Rykkelid
2007-09-14 14:25             ` Jeff Garzik
2007-09-14 14:39               ` Tejun Heo
     [not found]                 ` <46EAAA9A.1020903@pvv.org>
2007-09-14 15:58                   ` Jeff Garzik
2007-09-14 18:38                     ` Jon Ivar Rykkelid
2007-09-14 20:24                       ` auxsvr
2007-09-14 20:35             ` Jon Ivar Rykkelid
2007-09-15  7:12               ` Prakash Punnoor
2007-09-15 10:14                 ` Jon Ivar Rykkelid [this message]
2007-09-15 14:47                   ` John Stoffel
2007-09-15 19:29                     ` Jon Ivar Rykkelid
     [not found]                 ` <46EBA82C.6050000@pvv.org>
2007-09-15 11:30                   ` Prakash Punnoor
  -- strict thread matches above, loose matches on Subject: below --
2007-09-13  7:18 Jon Ivar Rykkelid
2007-09-13  9:16 ` Tejun Heo

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=46EBB08A.5050709@pvv.org \
    --to=jonry@pvv.org \
    --cc=hancockr@shaw.ca \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prakash@punnoor.de \
    /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