Just to provide some feedback, I was having the exact problem and this patch
appears to resolved it.
I CVSUP late afternoon, and make world with no problem on CPQ 1600 PII450
with Smart 2P controller.
Thanks
cuneyt
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jonathan Lemon
> Sent: Friday, October 08, 1999 2:43 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Compaq Proliant 2500 file corruptions
>
>
> In article
> <local.mail.freebsd-hackers/[EMAIL PROTECTED]> you write:
> >My school has recently acquired a Compaq Proliant 2500 and we are trying
> >to set up FreeBSD on it. I download the 3.3 kern and mfsroot disks and
> >replaced the kernel with a custom one that had the IDA driver included
> >in it. Everything installed fine. Then I started working on it again
> >and
> >whenever I'd cvsup or download ports the files would get corrupted.
>
> Let me guess, the symptom is that blocks of zeros are scattered
> randomly throughout the file? If this is the case, the IDA driver
> in 3.3 is the culprit.
>
>
> >3. Would I be better off running the newer driver in current? I keep
> >tabs with whats going on in the current list, I just need a somewhat
> >stable machine. It's only going to get light usage.
>
> This probably is one solution. Another is to try a couple of patches
> to see if they fix the problem; attached is some code that might help.
> --
> Jonathan
>
>
> Index: ida.c
> ===================================================================
> RCS file: /ncvs/src/sys/i386/isa/Attic/ida.c,v
> retrieving revision 1.1.2.3
> diff -u -r1.1.2.3 ida.c
> --- ida.c 1999/08/29 16:07:18 1.1.2.3
> +++ ida.c 1999/10/08 19:41:57
> @@ -1206,7 +1206,8 @@
>
> if (PCI_CONTROLLER(ida)) {
> qcbp->hdr.priority = 0x00;
> - qcbp->hdr.flags = 0x24;
> + qcbp->hdr.flags =
> + (sizeof(struct ida_req) + sizeof(struct ida_sgb) *
> IDA_MAX_SGLEN) >>
> } else {
> qcbp->hdr.priority = IDA_DEF_PRIORITY;
> qcbp->hdr.flags = 0x10;
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
