From: Matthew Wilcox <matthew@wil.cx>
To: Marc Dietrich <marvin24@gmx.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Sym2 driver timeouts on powerstacks
Date: Tue, 4 Jan 2005 13:08:52 +0000 [thread overview]
Message-ID: <20050104130852.GS18080@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200501041354.50294.marvin24@gmx.de>
On Tue, Jan 04, 2005 at 01:54:49PM +0100, Marc Dietrich wrote:
> This machine runs fine on 2.4 series kernels, but fails on 2.6 due to timeouts
> in the scsi driver. The 2.4 series kernels used the (I guess now obsoleted)
> ncr53c8xx.c/sym53c8xx.c driver.
> There were some PReP specific "fixed" in the old driver, which not have been
> ported to the sym2 driver. I tried to backport the "latency" and the
> "pci_command_master/parity" fixes (see the 2.4 log), but even with this I had
> no success.
I'm not surprised, those patches ought to have no effect.
PCI_COMMAND_MASTER is set when the driver calls pci_set_master().
PCI_COMMAND_PARITY should be set by the platform code, but afaict is
currently not set on ppc.
> I attached the full debug output of both 2.4 and 2.6 kernels.
Umm. Not terribly helpful. Could you delete all the spurious blank lines
next time, and it'd be much more helpful if you could boot with the option
"sym53c8xx.debug=0x1fff"
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2005-01-04 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 12:54 Sym2 driver timeouts on powerstacks Marc Dietrich
2005-01-04 13:08 ` Matthew Wilcox [this message]
2005-01-07 14:48 ` Matthew Wilcox
2005-01-07 18:20 ` marvin24
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=20050104130852.GS18080@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=linux-scsi@vger.kernel.org \
--cc=marvin24@gmx.de \
/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