lkml.org 
[lkml]   [2000]   [Oct]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: Possible critical VIA vt82c686a chip bug (private question)
    From
    Date
    Vojtech Pavlik <vojtech@suse.cz> writes:

    > On Thu, Oct 26, 2000 at 01:42:29PM -0400, Richard B. Johnson wrote:
    >
    > > > > ../drivers/block/ide.c, line 162, on version 2.2.17 does bad things
    > > > > to the timer. It writes 0 to the control-word for timer 0. This
    > > > > does the following:
    > > [Snipped...]
    > > >
    > > > Well, at least on 2.4.0-test9, the above timing code is #ifed to
    > > > DISK_RECOVERY_TIME > 0, which in turn is #defined to 0 in
    > > > include/linux/ide.h.
    > > >
    > > > So this is not our problem here. Anyway I guess it's time to hunt for
    > > > i8259 accesses in the kernel that lack the necessary spinlock, even when
    > > > they're not probably the cause of the problem we see here.
    > >
    > > Okay, good.
    >
    > Ok, here is a list of places within the kernel that access the PIT
    > timer, plus the method of locking (i386 arch only):

    [...]

    Ok, I just tested if the problem was always present without
    the IDE subsystem...

    The answer is it is not... so it isn't an IDE problem.

    --
    -- Yoann http://www.mandrakesoft.com/~yoann/
    An engineer from NVidia, while asking him to release cards specs said :
    "Actually, we do write our drivers without documentation."
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 12:45    [W:0.021 / U:59.492 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site