From: Doug Ledford <dledford@redhat.com>
To: Philippe Troin <phil@fifi.org>
Cc: Hanna Linder <hannal@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
tmolina@cox.net, haveblue@us.ibm.com
Subject: Re: more aic7xxx boot failure
Date: Thu, 24 Oct 2002 23:53:53 -0400 [thread overview]
Message-ID: <20021025035353.GA3556@redhat.com> (raw)
In-Reply-To: <87hefbxw3d.fsf@ceramic.fifi.org>
On Thu, Oct 24, 2002 at 04:20:38PM -0700, Philippe Troin wrote:
> Hanna Linder <hannal@us.ibm.com> writes:
>
> > Pending list: 2
> > Kernel Free SCB list: 1 0
> > Untagged Q(0): 2
> > DevQ(0:0:0):0 waiting
> > qinpos = 0, SCB index = 3
> > Kernel panic: Loop 1
>
> Had the same problem.
>
> Booted noapic, problem solved...
>
> Now, if the driver could be fixed, that would be nicer...
If noapic solves the problem then the driver isn't where the bug is, it's
in the SMP irq table or ACPI irq routing or PCI interrupt routing, but it
is *not* the driver.
I will repeat, if "noapic" ever solves a driver bug, then the problem
wasn't a driver bug in the first place!
/me has been listening to people wrongly accuse drivers of IRQ routing
bugs for going on three years now, ever since the MP table parsing and
IO-APIC code was first put into the linux kernel and now tends to be a bit
testy when people make the mistake of calling an IRQ routing bug a driver
bug.
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
prev parent reply other threads:[~2002-10-25 3:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 22:25 more aic7xxx boot failure Hanna Linder
2002-10-24 22:46 ` Philippe Troin
2002-10-24 23:12 ` Hanna Linder
2002-10-24 23:20 ` Philippe Troin
2002-10-24 23:56 ` SL Baur
2002-10-25 0:39 ` Philippe Troin
2002-10-25 3:53 ` Doug Ledford [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=20021025035353.GA3556@redhat.com \
--to=dledford@redhat.com \
--cc=hannal@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=phil@fifi.org \
--cc=tmolina@cox.net \
/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.