From: Duncan Laurie <duncan@sun.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: problem with Serverworks CSB5 IDE
Date: Thu, 24 Apr 2003 16:52:09 -0700 [thread overview]
Message-ID: <3EA878A9.40106@sun.com> (raw)
In-Reply-To: <3EA85C5C.7060402@sun.com>
Duncan Laurie wrote:
> Olivier Bornet wrote:
>
>> Hi all,
>>
>> I reply to myself, after having test this solution.
>>
>>
>>> At this time, I have compiled and installed a 2.4.20-ac2 + some cobalt
>>> patches. Is the bug also fixed in 2.4.20-ac2, or must I rebuild the
>>> 2.4.20 with the check commented out ?
>>
>>
>>
>> The 2.4.20-ac2 patched kernel help a little : the system don't crash
>> anymore. But the disk is marked as defective, and is removed from the
>> raid1 metadevice.
>>
>> One other problem with the -ac2 is the speed for the rebuild : it seems
>> to be 2 times slower than with the Ducan patch. (about 2 hours instead
>> of 1 hour).
>>
>> So, my solution is to use the patch from Ducan. I hope it (or a
>> derivative form of it) will be included in the next kernel releases.
>>
>> Good day, and thanks all for the help.
>>
>
> Here is a 2.4.21-rc1 version of the patch, with a few modificaions
> due to the changes in IDE..
>
> Actually UDMA mode detection is not working at all for CSB5 in
> 2.4.21-rc1 because svwks_revision variable is set in __init function
> so was reading as 0 in svwks_ratemask(). This made it think UDMA
Oops, this analysis is wrong.. The svwks_revision variable is set
in the init_chipset_svwks() function, which doesn't appear to ever
get called because dev->irq==0. The init_chipset function is also
responsible for the call to ide_pci_register_host_proc(), so since
it isn't being called there is no /proc/ide/svwks.
I think for Serverworks IDE you will never get a valid dev->irq out
of the pci config register, so maybe should there still be a call to
d->init_chipset in this block from drivers/ide/setup-pci.c:
} else if (!pciirq) {
if (noisy)
printk(KERN_WARNING "%s: bad irq (%d): will probe later\n",
d->name, pciirq);
pciirq = 0;
}
-duncan
next prev parent reply other threads:[~2003-04-24 23:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 21:27 problem with a cobalt RaQ550 system and DMA (Serverworks OSB4 in impossible state) Olivier Bornet
2003-04-23 22:21 ` Alan Cox
2003-04-23 23:29 ` Olivier Bornet
2003-04-24 8:00 ` Olivier Bornet
2003-04-24 21:51 ` problem with Serverworks CSB5 IDE Duncan Laurie
2003-04-24 23:52 ` Duncan Laurie [this message]
2003-04-25 11:00 ` Alan Cox
2003-04-25 16:39 ` Duncan Laurie
2003-04-25 15:42 ` Alan Cox
2003-04-25 18:52 ` Duncan Laurie
2003-04-25 18:02 ` Alan Cox
2003-04-28 13:03 ` Alan Cox
2003-04-24 0:02 ` problem with a cobalt RaQ550 system and DMA (Serverworks OSB4 in impossible state) Duncan Laurie
2003-04-24 7:55 ` Olivier Bornet
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=3EA878A9.40106@sun.com \
--to=duncan@sun.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).