From: Chris Dearman <chris@mips.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: [MIPS] SMTC: Fix crash on bootup with idebus= command line argument.
Date: Mon, 03 Sep 2007 16:50:06 +0100 [thread overview]
Message-ID: <46DC2D2E.8080408@mips.com> (raw)
In-Reply-To: <20070904.000501.41013092.anemo@mba.ocn.ne.jp>
Atsushi Nemoto wrote:
> Why pci_get_class() in ide_default_io_base() cause crash on SMTC?
The bug wasn't really SMTC specific, it was just that it showed up on
SMTC builds. The failure was caused by the early parsing of the
idebus=xx argument. The argument parser ended up calling
pci_scan that unconditionally enabled interrupts prematurely.
Ralf says this has now been fixed in head of tree:
> Turns out our dear friends at Intel recently had trouble with some JVC CDROM
> drive and their changes made a proper fix for us fairly easy.
>
> master: 00cc123703425aa362b0af75616134cbad4e0689
> 2.6.22: 50a32ae87aed46b01c8e0c2e90cd6f06a3800c33
>
> For older kernels the generic PCI code doesn't have the necessary bits in so
> that'd be somewhat more surgery than I want in lmo.
Chris
--
Chris Dearman 7200 Cambridge Research Park +44 1223 203108
MIPS Technologies (UK) Waterbeach, Cambs CB25 9TL fax +44 1223 203181
next prev parent reply other threads:[~2007-09-03 15:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S20024438AbXHGQ1m/20070807162742Z+2733@ftp.linux-mips.org>
2007-09-03 15:05 ` [MIPS] SMTC: Fix crash on bootup with idebus= command line argument Atsushi Nemoto
2007-09-03 15:50 ` Chris Dearman [this message]
2007-09-04 12:50 ` Ralf Baechle
2007-09-04 14:02 ` Atsushi Nemoto
2007-09-13 13:55 ` Ralf Baechle
2007-09-10 13:27 ` Maciej W. Rozycki
2007-09-10 15:18 ` Atsushi Nemoto
2007-09-11 13:40 ` Maciej W. Rozycki
2007-09-11 14:07 ` Atsushi Nemoto
2007-09-11 14:28 ` Maciej W. Rozycki
2007-09-12 15:18 ` Atsushi Nemoto
2007-09-12 15:54 ` Maciej W. Rozycki
2007-09-12 16:55 ` Atsushi Nemoto
2007-09-12 17:19 ` Maciej W. Rozycki
2007-09-13 13:49 ` Ralf Baechle
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=46DC2D2E.8080408@mips.com \
--to=chris@mips.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.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