Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: Alex <mysqlstudent@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: aacraid problems on 2.6.35-rc3
Date: Wed, 30 Jun 2010 15:02:28 -0500	[thread overview]
Message-ID: <1277928148.2839.364.camel@mulgrave.site> (raw)
In-Reply-To: <AANLkTinRg1WIRWIBE1odKkvbECBPLPUoY2mVKmAjqpKZ@mail.gmail.com>

On Wed, 2010-06-30 at 10:57 -0400, Alex wrote:
> Hi,
> 
> >> It only prints the following when booting:
> >>
> >> Adaptec aacraid driver 1.1-5[2456]-ms
> >
> > That driver comes from a rather old kernel (2.6.29 or before).  Could
> > you try with a modern version (which should print 1.1-5[26400]-ms just
> > in case the problem got fixed in the interim.
> 
> Yes, my apologies. This was from the working kernel, which is 2.6.27.
> I am working with 2.6.35-rc3.
> 
> >> The dmesg output from a working system is here:
> >>
> >> http://pastebin.com/0AnVBV7s
> >
> > This trace shows your system won't configure interrupts correctly
> > without ACPI ... if ACPI isn't working, more than just the aacraid will
> > be non functional.  A dmesg of the failing system would be definitive in
> > diagnosing this.
> 
> How can I do this? The kernel panics without mounting a filesystem.

You need a serial or net console to capture the output.  At a guess, the
latest ACPI cockup is this one:

commit b430acbd7c4b919886fa7fd92eeb7a695f1940d3
Author: Len Brown <len.brown@intel.com>
Date:   Thu May 6 17:41:08 2010 -0400

    ACPICA: simplify SCI_EN workaround

Try reverting that and seeing if it boots.

James



      reply	other threads:[~2010-06-30 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30 14:28 aacraid problems on 2.6.35-rc3 Alex
2010-06-30 14:54 ` James Bottomley
2010-06-30 14:57   ` Alex
2010-06-30 20:02     ` James Bottomley [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=1277928148.2839.364.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mysqlstudent@gmail.com \
    /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