I don't see the problem with 53C8xx controllers referenced. Here's the
message from some time ago to refresh your memory:
: From: Alan Cox <alan@lxorguk.ukuu.org.uk>
: Subject: Re: Problem w/ 2.2.10-ac12 & NCR53c875
: Date: Thu, 29 Jul 1999 17:13:38 +0100 (BST)
: Message-Id: <E11AHdg-00015E-00@the-village.bc.nu>
:
: > If the reason is that this bad changes in the pyxis_core stuff only affect
: > the sym53c8xx devices and only on Alpha machines and thus guys think it is
: > not important, then they just appear as not interesting people to me. I am
: > wondering about what would have happened facing a bad change that affected
: > also (or only) Adaptec devices on Intel platforms.
:
: I've got some queued patches from Rth that hopefully fix this. So people
: *do* care.
FYI this problem is still there in 2.2.11 (and in patch-2.2.12pre7);
I tripped over this last night. Do you still have those patches queued?
As stated in that thread, copying over the old core_*.[ch] from an older
2.2.x kernel (I tried 2.2.5) fixes the symptom perfectly. Maybe not the
optimal solution, but at least it my system then has a usable scsi
controller again...
Paul Slootman
-- home: paul@wurtel.demon.nl http://www.wurtel.demon.nl/ work: paul@murphy.nl http://www.murphy.nl/ debian: paul@debian.org http://www.debian.org/ isdn4linux: paul@isdn4linux.de http://www.isdn4linux.de/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/