Christian wrote:
I've tested multiple kernels (including -mm series) in the range of 2.6.19.7
(before sata_nv adma support went in) up to 2.6.20-rc4.
Every NCQ enabled kernel I've tested showed ata errors in dmesg. So I came to
the conclusion that my system was faulty. I ran memtest86+ for a
On Monday 19 March 2007 08:39:15 Tejun Heo wrote:
> Christian wrote:
> > Yes, for me the problem was introduced recently. I have moved around
> > terabytes (sic!) on my discs with older kernels and I never got errors.
>
> There is always the possibility of disk going bad, so it would be great
> if
On Monday 19 March 2007 08:39:15 Tejun Heo wrote:
Christian wrote:
Yes, for me the problem was introduced recently. I have moved around
terabytes (sic!) on my discs with older kernels and I never got errors.
There is always the possibility of disk going bad, so it would be great
if you can
Christian wrote:
I've tested multiple kernels (including -mm series) in the range of 2.6.19.7
(before sata_nv adma support went in) up to 2.6.20-rc4.
Every NCQ enabled kernel I've tested showed ata errors in dmesg. So I came to
the conclusion that my system was faulty. I ran memtest86+ for a
On 2007/03/19 13:09, Jeff Garzik <[EMAIL PROTECTED]> wrote:
> I may have missed the answer to this before, but: does the problem
> go away if you disable preempt?
On my system (same problem, original bug report), preemption is
disabled.
Max
-
To unsubscribe from this list: send the line
On 2007/03/19 13:09, Jeff Garzik [EMAIL PROTECTED] wrote:
I may have missed the answer to this before, but: does the problem
go away if you disable preempt?
On my system (same problem, original bug report), preemption is
disabled.
Max
-
To unsubscribe from this list: send the line unsubscribe
Christian wrote:
On Sunday 18 March 2007 06:43:09 you wrote:
Christian wrote:
This does indeed look like a drive side issue to me (the controller is
reporting CPBs with response flags 2 which as far as I can tell
indicates it's still waiting for the drive to complete the request).
Christian wrote:
On Monday 19 March 2007 03:48:14 you wrote:
Christian wrote:
On Sunday 18 March 2007 06:43:09 you wrote:
Christian wrote:
This does indeed look like a drive side issue to me (the controller is
reporting CPBs with response flags 2 which as far as I can tell
indicates it's
Christian wrote:
> Yes, for me the problem was introduced recently. I have moved around
> terabytes
> (sic!) on my discs with older kernels and I never got errors.
There is always the possibility of disk going bad, so it would be great
if you can boot an older kernel and verify that the problem
On Monday 19 March 2007 03:48:14 you wrote:
> Christian wrote:
> > On Sunday 18 March 2007 06:43:09 you wrote:
> >> Christian wrote:
> This does indeed look like a drive side issue to me (the controller is
> reporting CPBs with response flags 2 which as far as I can tell
> indicates
On Monday 19 March 2007 03:48:14 you wrote:
Christian wrote:
On Sunday 18 March 2007 06:43:09 you wrote:
Christian wrote:
This does indeed look like a drive side issue to me (the controller is
reporting CPBs with response flags 2 which as far as I can tell
indicates it's still waiting
Christian wrote:
Yes, for me the problem was introduced recently. I have moved around
terabytes
(sic!) on my discs with older kernels and I never got errors.
There is always the possibility of disk going bad, so it would be great
if you can boot an older kernel and verify that the problem
Christian wrote:
On Monday 19 March 2007 03:48:14 you wrote:
Christian wrote:
On Sunday 18 March 2007 06:43:09 you wrote:
Christian wrote:
This does indeed look like a drive side issue to me (the controller is
reporting CPBs with response flags 2 which as far as I can tell
indicates it's
Christian wrote:
On Sunday 18 March 2007 06:43:09 you wrote:
Christian wrote:
This does indeed look like a drive side issue to me (the controller is
reporting CPBs with response flags 2 which as far as I can tell
indicates it's still waiting for the drive to complete the request).
Christian wrote:
> On Sunday 18 March 2007 06:43:09 you wrote:
>> Christian wrote:
This does indeed look like a drive side issue to me (the controller is
reporting CPBs with response flags 2 which as far as I can tell
indicates it's still waiting for the drive to complete the
On Sunday 18 March 2007 06:43:09 you wrote:
> Christian wrote:
> >> This does indeed look like a drive side issue to me (the controller is
> >> reporting CPBs with response flags 2 which as far as I can tell
> >> indicates it's still waiting for the drive to complete the request).
> >
> > I have
On Sunday 18 March 2007 06:43:09 you wrote:
Christian wrote:
This does indeed look like a drive side issue to me (the controller is
reporting CPBs with response flags 2 which as far as I can tell
indicates it's still waiting for the drive to complete the request).
I have been using this
Christian wrote:
On Sunday 18 March 2007 06:43:09 you wrote:
Christian wrote:
This does indeed look like a drive side issue to me (the controller is
reporting CPBs with response flags 2 which as far as I can tell
indicates it's still waiting for the drive to complete the request).
I have
Christian wrote:
>> This does indeed look like a drive side issue to me (the controller is
>> reporting CPBs with response flags 2 which as far as I can tell
>> indicates it's still waiting for the drive to complete the request).
>
> I have been using this hw-config (SATA II, NCQ) since the
Christian wrote:
This does indeed look like a drive side issue to me (the controller is
reporting CPBs with response flags 2 which as far as I can tell
indicates it's still waiting for the drive to complete the request).
I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA
> This does indeed look like a drive side issue to me (the controller is
> reporting CPBs with response flags 2 which as far as I can tell
> indicates it's still waiting for the drive to complete the request).
I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA support
made it
On Friday 16 March 2007 12:20:02 Max Kellermann wrote:
> Hi,
>
> I have been trying to upgrade my 2.6.19 kernel for a while now,
> without success. All kernel versions since 2.6.20 failed with a
> timeout while trying to write to my SATA hard disk. After I wait for
> a while (during which all
(linux-ide cc'ed)
Max Kellermann wrote:
Hi,
I have been trying to upgrade my 2.6.19 kernel for a while now,
without success. All kernel versions since 2.6.20 failed with a
timeout while trying to write to my SATA hard disk. After I wait for
a while (during which all I/O to the hard disk
On Friday 16 March 2007 12:20:02 Max Kellermann wrote:
Hi,
I have been trying to upgrade my 2.6.19 kernel for a while now,
without success. All kernel versions since 2.6.20 failed with a
timeout while trying to write to my SATA hard disk. After I wait for
a while (during which all I/O to
This does indeed look like a drive side issue to me (the controller is
reporting CPBs with response flags 2 which as far as I can tell
indicates it's still waiting for the drive to complete the request).
I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA support
made it in
(linux-ide cc'ed)
Max Kellermann wrote:
Hi,
I have been trying to upgrade my 2.6.19 kernel for a while now,
without success. All kernel versions since 2.6.20 failed with a
timeout while trying to write to my SATA hard disk. After I wait for
a while (during which all I/O to the hard disk
26 matches
Mail list logo
