From: Jens Axboe <axboe@suse.de>
To: Anton Altaparmakov <aia21@cantab.net>
Cc: Andre Hedrick <andre@linux-ide.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: ide double init? + Re: BUG: Current 2.5-BK tree dies on boot!
Date: Thu, 19 Sep 2002 12:08:31 +0200 [thread overview]
Message-ID: <20020919100831.GC31033@suse.de> (raw)
In-Reply-To: <20020919094520.GB31033@suse.de>
On Thu, Sep 19 2002, Jens Axboe wrote:
> > Note there is something odd wrt IDE initialization. The driver seems to be
> > trying to initialize twice and there quite a few messages output which
> > don't reflect reality (probably a consequence of the double init). For
> > example it says DMA disabled but checking with hdparm and in /proc/ide/via
> > DMA is enabled just fine. And it says neither IDE port enabled (BIOS) which
> > isn't true either.
>
> Yes you are right, it does seem to try and init twice. Wonder why. I'll
> take a look at that.
Seems to be ide probe calling the pci probe functions, and then they get
called by the pci layer later when they register. Dunno what the best
way to handle this is. Alan quotes ordering constraints as the reason.
Then maybe the easiest fix is to just do
chipset_init(bla)
{
if (chipset already setup)
return;
do_init();
}
Alan?
--
Jens Axboe
next prev parent reply other threads:[~2002-09-19 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 20:44 BUG: Current 2.5-BK tree dies on boot! Anton Altaparmakov
2002-09-18 22:58 ` Anton Blanchard
2002-09-19 8:47 ` Jens Axboe
2002-09-19 9:33 ` ide double init? + " Anton Altaparmakov
2002-09-19 9:45 ` Jens Axboe
2002-09-19 10:08 ` Jens Axboe [this message]
2002-09-19 10:58 ` Alan Cox
2002-09-19 11:14 ` Jens Axboe
2002-09-19 13:28 ` Alan Cox
2002-09-19 13:27 ` Jens Axboe
2002-09-19 17:48 ` Patrick Mochel
2002-09-19 18:02 ` Alan Cox
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=20020919100831.GC31033@suse.de \
--to=axboe@suse.de \
--cc=aia21@cantab.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
/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