From: Vojtech Pavlik <vojtech@suse.cz>
To: monkeyiq@dingoblue.net.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: idebus=xx on a ISA only 486
Date: Wed, 18 Apr 2001 08:46:52 +0200 [thread overview]
Message-ID: <20010418084652.A369@suse.cz> (raw)
In-Reply-To: <3ADAE8A4.87DFBF92@dingoblue.net.au>
In-Reply-To: <3ADAE8A4.87DFBF92@dingoblue.net.au>; from monkeyiq@dingoblue.net.au on Mon, Apr 16, 2001 at 10:42:12PM +1000
On Mon, Apr 16, 2001 at 10:42:12PM +1000, monkeyiq@dingoblue.net.au wrote:
> Hi,
> This may be harmless but I noticed a warning msg when I went to
> 2.4.3 on a ISA only 486 mobo.
>
> Feb 18 18:01:41 speedy kernel: ide: Assuming 50MHz system bus speed for
> PIO modes; override with idebus=xx
>
> My first thought was to drop idebus to 8Mhz (I think this is the
> ISA speed ?),
> but using that
> Feb 18 18:01:41 speedy kernel: Kernel command line: auto BOOT_IMAGE=243
> ro root=301 BOOT_FILE=/boot/vmlinuz-2.4.3 idebus=8
> Feb 18 18:01:41 speedy kernel: ide_setup: idebus=8 -- BAD BUS SPEED!
> Expected value from 20 to 66
>
> and then a quick grep/poke in the src gave this
>
> ./drivers/ide/ide.c
> Version 5.50 allow values as small as 20 for idebus=
>
> and at line 350 it seems that its pci or nothing for the bus speed.
>
> the only deterministic problem (so far that I can directly attribute to
> that kernel) with the
> 2.4.3 booted kernel is that ssh2 locks up for random amounts of time at
> randomish intervals.
>
> I can't seem to dig up other info on this problem, I am sorry if this is
> the wrong place
> to ask. If there are better places to be looking for this data I am
> happy to RTFM there.
>
> Now trying 2.4.3-ac6 to see what happens there.
idebus= isn't used in case there is no VL-BUS or PCI bus in your system.
--
Vojtech Pavlik
SuSE Labs
prev parent reply other threads:[~2001-04-18 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 12:42 idebus=xx on a ISA only 486 monkeyiq
2001-04-18 6:46 ` Vojtech Pavlik [this message]
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=20010418084652.A369@suse.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=monkeyiq@dingoblue.net.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.