Hi Douglas,
On Fri, 03 Aug 2007, Douglas Allan Tutty wrote:
> On Fri, Aug 03, 2007 at 02:28:58PM -0400, Brad Sawatzky wrote:
> > On Fri, 03 Aug 2007, Francois Duranleau wrote:
> > [ . . . ]
> > > Now, when I boot my computer using the new kernel, I get an error
> > > message during filesystem check saying it contains errors (sorry, I
> > > don't have a more precise error message, and I have no logs) and
> > > it then mounts the filesystem read-only. If I boot back with the
> > > 2.4.27 kernel, no problems. I do get often though an error message
> > > like this:
> > > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> > > and then sometimes:
> > > ide0: reset: success
> > > I have been having this for a long time (even after I changed to a
> > > new hard drive), and only when DMA is active, but I never noticed
> > > anything bad happening except for those error messages.
> > [ . . . ]
>
> But why would he only get the errors with a new kernel?
Perhaps I misunderstood, but I thought he got the errors with the old
kernel (and had for a long time) but they did not trigger a filesystem
check. My hunch was that the 2.6.x IDE driver (or ext3 driver) is handling
the error condition in a different way. Perhaps not retrying at all on the
CRC error, or maybe having a shorter time-out on the retry, who knows...
If he only gets the errors under 2.6.x and not 2.4.27 then it looks more
like a driver issue. Perhaps his 2.6.x kernel is using the new 'merged'
SATA+PATA subsystem to handle his PATA drive instead of the old ATA/ATAPI
driver and that is causing the problem.
-- Brad
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
