From: Willy Tarreau <willy@w.ods.org>
To: Simon Byrnand <simon@igrin.co.nz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.27 -> 2.4.28 breaks i810-tco watchdog timer
Date: Wed, 8 Dec 2004 06:48:34 +0100 [thread overview]
Message-ID: <20041208054834.GD17946@alpha.home.local> (raw)
In-Reply-To: <17545.210.54.153.131.1102449575.squirrel@210.54.153.131>
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
next prev parent reply other threads:[~2004-12-08 6:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 19:59 Simon Byrnand
2004-12-08 5:48 ` Willy Tarreau [this message]
2004-12-08 6:34 ` Len Brown
2004-12-09 21:29 ` Simon Byrnand
2004-12-18 18:45 ` Marcelo Tosatti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041208054834.GD17946@alpha.home.local \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@igrin.co.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome