From: Brad Boyer <flar@allandria.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Kenn Humborg <kenn@linux.ie>,
linux scsi <linux-scsi@vger.kernel.org>,
linux m68k <linux-m68k@vger.kernel.org>
Subject: Re: mac_scsi boot crash, was Re: [PATCH] m68k link error and NCR5380_exit()
Date: Tue, 8 Mar 2005 09:39:40 -0800 [thread overview]
Message-ID: <20050308173939.GA17983@pants.nu> (raw)
In-Reply-To: <Pine.LNX.4.61.0503090156380.1135@loopy.telegraphics.com.au>
On Wed, Mar 09, 2005 at 02:16:45AM +1100, Finn Thain wrote:
> That seems to have helped. It still crashes with the same bus error, but
> the preceding issue/disconnect/abort cycle is gone now. Log is below.
> Hopefully I'll get a chance to look at the bus error soon.
I notice it got through all the device identify stuff. It dies as soon
as it actually tries to tranfer a real block of data (the partition map)
and do something useful with it. Could you see if disabling PDMA helps?
There's a way to do it with the command line, but that is messy. If you
don't mind recompiling, just set the FLAG_NO_PSEUDO_DMA flag like it
always does for the IIfx case. The performance will be terrible, but
it might help narrow down the problem.
Brad Boyer
flar@allandria.com
next prev parent reply other threads:[~2005-03-08 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.0502110155440.7310@loopy.telegraphics.com.au>
[not found] ` <20050210171518.GA22265@pants.nu>
[not found] ` <Pine.LNX.4.61.0502111930340.11381@loopy.telegraphics.com.au>
[not found] ` <Pine.LNX.4.61.0502121539440.20941@loopy.telegraphics.com.au>
[not found] ` <20050212075645.GA30669@pants.nu>
[not found] ` <Pine.LNX.4.61.0502122135230.21876@loopy.telegraphics.com.au>
[not found] ` <20050213040948.GA10198@orchestra.cs.caltech.edu>
[not found] ` <Pine.LNX.4.61.0502131618470.25204@loopy.telegraphics.com.au>
[not found] ` <20050213063225.GA17415@orchestra.cs.caltech.edu>
[not found] ` <Pine.LNX.4.61.0502131736300.25553@loopy.telegraphics.com.au>
[not found] ` <20050213075506.GA18622@orchestra.cs.caltech.edu>
[not found] ` <Pine.LNX.4.61.0502212233290.15372@loopy.telegraphics.com.au>
2005-03-07 6:30 ` [PATCH] m68k link error and NCR5380_exit() Finn Thain
2005-03-07 6:37 ` Christoph Hellwig
2005-03-07 13:45 ` Finn Thain
2005-03-07 17:53 ` Brad Boyer
2005-03-07 23:42 ` Kenn Humborg
2005-03-08 15:16 ` mac_scsi boot crash, was " Finn Thain
2005-03-08 17:39 ` Brad Boyer [this message]
2005-03-09 12:00 ` [PATCH] mac_scsi boot crash fix Finn Thain
2005-03-09 12:06 ` Kenn Humborg
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=20050308173939.GA17983@pants.nu \
--to=flar@allandria.com \
--cc=fthain@telegraphics.com.au \
--cc=kenn@linux.ie \
--cc=linux-m68k@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.