lkml.org 
[lkml]   [2005]   [Jun]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Promise ATA/133 Errors With 2.6.10+


    On Sat, 25 Jun 2005, Erik Slagter wrote:

    > On Fri, 2005-06-24 at 16:55 -0400, Justin Piszcz wrote:
    >
    >> Jun 24 15:24:18 localhost kernel: PDC202XX: Primary channel reset.
    >> Jun 24 15:24:18 localhost kernel: hde: timeout waiting for DMA
    >> Jun 24 15:24:18 localhost kernel: hde: status error: status=0x58 {
    >> DriveReady SeekComplete DataRequest }
    >> Jun 24 15:24:18 localhost kernel:
    >> Jun 24 15:24:18 localhost kernel: ide: failed opcode was: unknown
    >> Jun 24 15:24:18 localhost kernel: hde: drive not ready for command
    >> Jun 24 15:24:18 localhost kernel: hde: status timeout: status=0xd0 { Busy
    >> }
    >> Jun 24 15:24:18 localhost kernel:
    >> Jun 24 15:24:18 localhost kernel: ide: failed opcode was: unknown
    >> Jun 24 15:24:18 localhost kernel: PDC202XX: Primary channel reset.
    >> Jun 24 15:24:18 localhost kernel: hde: no DRQ after issuing MULTWRITE_EXT
    >> Jun 24 15:24:18 localhost kernel: ide2: reset: success
    >
    > I have exactly this (these messages) but then with a amd/via ata driver
    > on tyan/amd motherboard with an IBM/Hitachi harddisk.
    >
    > It looks like the drive cpu locks up every now and then, notably when
    > the environmental temperature and/or the drive's temperature are high
    > and there is much activity on the drive.
    >
    > A reset (either from the driver or manually using hdparm) helps
    > (temporarily).
    >
    > I was going to buy new drives for this fact (from another brand) but it
    > looks that won't necessarily mean my problem will be solved :-(
    >
    > BTW I have another, exactly identical harddisk in the same computer
    > (well, ok, 1 year younger) and that one doesn't show the problem.
    >
    > BTW2 could it be that somewhere a timeout has been lowered in recent
    > kernels? That must have been pre-2.6.11 then.
    >

    ^^

    I think so!

    The box has worked for the past 6 months and started to have hiccups when
    I upgraded it to 2.6.11.x or 2.6.12.x.

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-06-25 10:39    [W:0.024 / U:0.208 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site