public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: aic7xxx broken in 2.6.18-rc3-mm2
Date: Fri, 11 Aug 2006 15:11:48 -0700	[thread overview]
Message-ID: <1155334308.7574.50.camel@localhost.localdomain> (raw)

My scsi card stopped being detected in 2.6.18-rc3-mm2, but works in
plain 2.6.18-rc3.  I bisected all the way down to the git-sas.patch.  I
then noticed that if I enable the AIC94XX driver, my card works again.

I'm digging through it right now, but I figured I'd post in case anyone
else had seen this.  This error mode seems vaguely familiar as well.
Any ideas?

-- Dave


             reply	other threads:[~2006-08-11 22:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 22:11 Dave Hansen [this message]
2006-08-11 22:27 ` aic7xxx broken in 2.6.18-rc3-mm2 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
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=1155334308.7574.50.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox