All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: berkley@cs.wustl.edu
Subject: [Bug 1584] New: 2.6.0-test10 hangs in aix79xxx after	iocell_workaround message
Date: Mon, 24 Nov 2003 09:23:39 -0800	[thread overview]
Message-ID: <11330000.1069694619@flay> (raw)

http://bugme.osdl.org/show_bug.cgi?id=1584

           Summary: 2.6.0-test10 hangs in aix79xxx after iocell_workaround
                    message
    Kernel Version: 2.6.0-test10 SMP
            Status: NEW
          Severity: blocking
             Owner: andmike@us.ibm.com
         Submitter: berkley@cs.wustl.edu


Distribution:
Hardware Environment: P4-Xeon-2.4GHz 2GB Adaptec 39320/AIC7902
Software Environment: Redhat 9.0
Problem Description:
Booting 2.6.0-test10 fails in AIC79XX (spinlock problem?) after executing
iocell_workaround in aic79xx_core.c (last message with ahd_debug set to 15)
since there were no changes to aic* since -test9 (which works fine) I'm assuming
the problem is in scsi.c which has many changes, most involving adding spinlocks.
The aic79xx module is loaded in the kernel (=y, not as a module =m)
at compile time.

Steps to reproduce:

boot -test10 kernel with either a 39320 U320 scsi controller or the motherboard
equivalent the AIC7902. With no debug on, the kernel hangs hard (no
<ctrl-alt-del>) just after showing the IDE partitions.
Setting the module parameter ahd_debug=15 to enable lots of messages shows
printf("%s: Setting up iocell workaround\n", ahd_name(ahd)); at 5383 in
aic79xx.c as the last known entry in syslog.


                 reply	other threads:[~2003-11-24 16:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=11330000.1069694619@flay \
    --to=mbligh@aracnet.com \
    --cc=berkley@cs.wustl.edu \
    --cc=linux-kernel@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.