From: Dave Hansen <haveblue@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux scsi <linux-scsi@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Alexis Bruemmer <alexisb@us.ibm.com>,
Mike Anderson <andmike@us.ibm.com>
Subject: Re: aic7xxx broken in 2.6.18-rc3-mm2
Date: Fri, 11 Aug 2006 16:06:43 -0700 [thread overview]
Message-ID: <1155337603.7574.61.camel@localhost.localdomain> (raw)
In-Reply-To: <1155336653.3552.54.camel@mulgrave.il.steeleye.com>
On Fri, 2006-08-11 at 17:50 -0500, James Bottomley wrote:
> > 0000:02:01.0 0100: 9005:00cf (rev 01)
> > 0000:02:01.1 0100: 9005:00cf (rev 01)
>
> OK strike that. The aic94xx cards all have IDs like 9005:04XX
>
> There does seem to be a cockup in the initialisation tables, but I can't
> see how it could affect what you're seeing. (PCI_DEVICE() uses the .name
> = value initialisation method and the fields following are unnamed). Do
> you build both of these into the kernel, and if so does it work when
> they're both modular?
Yep, I build both of them in. Making them both modular will require a
wee bit more time, as the aic7xxx has my root disk on it, and I don't
have any initrds.
In any case, I'm starting to get some funky results. I can't get the
problem to reappear in the tree where I was doing the bisect, but my
development tree where I first saw it is still broken.
I'll do some more digging and get out a more reliable bug report.
-- Dave
next prev parent reply other threads:[~2006-08-11 23:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 22:11 aic7xxx broken in 2.6.18-rc3-mm2 Dave Hansen
2006-08-11 22:27 ` James Bottomley
2006-08-11 22:31 ` Dave Hansen
2006-08-11 22:50 ` James Bottomley
2006-08-11 23:05 ` Doug Maxey
2006-08-11 23:06 ` Dave Hansen [this message]
2006-08-11 23:21 ` Andrew Morton
2006-08-12 0:17 ` Dave Hansen
2006-08-12 0:36 ` Andrew Morton
2006-08-12 1:03 ` Greg KH
2006-08-12 18:05 ` Daniel Ritz
2006-08-12 22:02 ` Daniel Ritz
2006-08-14 12:17 ` Marcus Better
2006-08-14 16:05 ` Dave Hansen
2006-08-14 16:58 ` Daniel Ritz
2006-08-14 17:04 ` Dave Hansen
2006-08-14 17:16 ` Dave Hansen
2006-08-14 18:21 ` Daniel Ritz
2006-08-14 19:56 ` Dave Hansen
2006-08-14 20:19 ` Daniel Ritz
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=1155337603.7574.61.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=alexisb@us.ibm.com \
--cc=andmike@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 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.