It seems Greg Lehey wrote:
> On Monday, 13 December 1999 at 9:03:16 +0100, Soren Schmidt wrote:
> > It seems [EMAIL PROTECTED] wrote:
> >> Will the backdown to PIO mode be permanent till the next reboot of the
> >> machine, or will the driver be able to attempt to return to DMA mode after
> >> a
On Monday, 13 December 1999 at 9:03:16 +0100, Soren Schmidt wrote:
> It seems [EMAIL PROTECTED] wrote:
>> Will the backdown to PIO mode be permanent till the next reboot of the
>> machine, or will the driver be able to attempt to return to DMA mode after
>> a timeout period. I'm only seeing thes
It seems Andrew Gallatin wrote:
>
> Looks like the world is safe for Promise Ultra users:
>
> Dec 13 18:42:37 waffle /kernel.test: ad2: UDMA CRC READ ERROR blk #22057647 retrying
> Dec 13 18:49:21 waffle xntpd[122]: time reset (step) 0.389151 s
> Dec 13 19:11:45 waffle xntpd[122]: time reset (st
Andrew Gallatin writes:
>
> Soren Schmidt writes:
> > I've fixed it here (I hope), and it will be in the next batch of fixes.
> > I hope to get through my mailbox today :)
>
> Thanks. I'm running a kernel built with them now. If/when we see CRC
> errors, I'll let you know what happ
Soren Schmidt writes:
> It seems Andrew Gallatin wrote:
> > > These are UDMA CRC errors, if you upgrade to the latest current, ata
> > > knows to retry these, only if they persist, something is wrong.
> > > However it could indicate cable problems, ie bad connectors or maybe
> > > too lo
It seems [EMAIL PROTECTED] wrote:
> Will the backdown to PIO mode be permanent till the next reboot of the
> machine, or will the driver be able to attempt to return to DMA mode after
> a timeout period. I'm only seeing these errors under really heavy disk
> activity (mutlitple nfs readers and wr
It seems Andrew Gallatin wrote:
> > These are UDMA CRC errors, if you upgrade to the latest current, ata
> > knows to retry these, only if they persist, something is wrong.
> > However it could indicate cable problems, ie bad connectors or maybe
> > too long cables..
> >
>
> He said the dis
> I've got a striped vinum partition that is occasionally going stale when
> I get spurrious errors from the ata driver.
>
> I can setstate the drives and the volume back up and an fsck of the
> partition doesn't show any obvious corruption.
>
> What do these errors indicate?
Your disk is going
Will the backdown to PIO mode be permanent till the next reboot of the
machine, or will the driver be able to attempt to return to DMA mode after
a timeout period. I'm only seeing these errors under really heavy disk
activity (mutlitple nfs readers and writers plus rsync/mirror jobs to the
vinum
Soren Schmidt writes:
> It seems [EMAIL PROTECTED] wrote:
> > I've got a striped vinum partition that is occasionally going stale when
> > I get spurrious errors from the ata driver.
> >
> > I can setstate the drives and the volume back up and an fsck of the
> > partition doesn't show any
It seems [EMAIL PROTECTED] wrote:
> I've got a striped vinum partition that is occasionally going stale when
> I get spurrious errors from the ata driver.
>
> I can setstate the drives and the volume back up and an fsck of the
> partition doesn't show any obvious corruption.
>
> What do these er
[EMAIL PROTECTED] writes:
> I've got a striped vinum partition that is occasionally going stale when
> I get spurrious errors from the ata driver.
>
> I can setstate the drives and the volume back up and an fsck of the
> partition doesn't show any obvious corruption.
>
> What do these er
I've got a striped vinum partition that is occasionally going stale when
I get spurrious errors from the ata driver.
I can setstate the drives and the volume back up and an fsck of the
partition doesn't show any obvious corruption.
What do these errors indicate?
ad5: status=51 error=84
ad_inter
13 matches
Mail list logo
