Re: 2.4.27 -> 2.4.28 breaks i810-tco watchdog timer

From: Willy Tarreau (willy_at_w.ods.org)
Date: 12/08/04

  • Next message: Chris Wright: "Re: oops in proc_pid_stat() on task->real_parent?"
    Date:	Wed, 8 Dec 2004 06:48:34 +0100
    To: Simon Byrnand <simon@igrin.co.nz>
    
    

    Hi,

    On Wed, Dec 08, 2004 at 08:59:35AM +1300, Simon Byrnand wrote:
    (...)
    > e400-e47f : motherboard
    > e800-e81f : motherboard
    > ec00-ec3f : motherboard
    > f000-f00f : Intel Corp. 82801DB Ultra ATA Storage Controller
    > f000-f007 : ide0
    > f008-f00f : ide1
    >
    > Clearly the IO range the driver is trying to open is already in use by
    > "motherboard". If I check another almost identical machine still running
    > 2.4.27 but with the watchdog timer unloaded, /proc/ioports gives:

    grep -r shows that it's ACPI which declares this "motherboard" name. I
    seem to remember about a change in the ACPI resource reservation. You
    might want to check with Len or Marcelo. I believe you cannot disable
    it if you want to use HT.

    (...)
     
    > For some reason a blanket range of IO addresses are being allocated which
    > include the range needed by the i810-tco watchdog timer. Why ? I don't see
    > any changes to the code for the watchdog timer itself so it seems that
    > something else is allocating that range first. Does anyone know of a patch
    > to fix this ? Running without a watchdog timer until the next kernel
    > version doesnt appeal :( (I can't go back to 2.4.27 due to other problems
    > with that version)

    Maybe you can hack the driver if you absolutely need to load 2.4.28+TCO.
    Simply comment out the "return -EIO" at line 402. It will still print
    the message but should load.

    Regards,
    Willy

    -
    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/


  • Next message: Chris Wright: "Re: oops in proc_pid_stat() on task->real_parent?"

    Relevant Pages

    • Re: 2.6.13-rc3 Battery times at 100/250/1000 Hz = Zero difference
      ... >> Ok, so with an idle machine, different HZ makes no noticeable ... >> load and with a heavy load. ... With all the abbreviations in the ACPI field ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Using DMA in read/write, setting block size for I/O -> max_sectors
      ... > Can I set this parameter during startup for scsi_mod.ko during load? ... no it's a property of the hardware and as such the DRIVER has to set it. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: POSTing of video cards (WAS: Solo Xgl..)
      ... >> What about the x86 case of VGA devices that run without a driver being ... Do we force people to load an fbdev driver to get the reset? ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: powernow-k8-acpi driver
      ... >> refuses to works on them. ... > I really dislike the idea of having>1 driver for this. ... that would probably not even link on kernel without ACPI... ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Cleanups for powernow-k8
      ... > non-ACPI capability there for those people who do not want to enable ACPI ... I'd suggest to leave old driver there (possibly let me clean it up ... ;-)))), and create new powernow-k8-acpi, or powernow-acpi or something ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)