Date: Wed, 12 Mar 1997 17:29:37 +0200 (EET) From: mika ruohotie <bsdhack@shadows.aeon.net> To: tom@sdf.com (Tom Samplonius) Cc: hackers@freebsd.org Subject: Re: Panic with ahc driver Message-ID: <199703121529.RAA07609@shadows.aeon.net> In-Reply-To: <Pine.NEB.3.94.970311184637.17091A-100000@misery.sdf.com> from Tom Samplonius at "Mar 11, 97 06:55:41 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> Sorry, I just remembered I forgot to include that. I actually cvsup'ped > stable this yesterday. It still calls itself 2.1.7, but I guess it really > is 2.1.7++. aic7xxx.c is rev 1.29.2.32 (stable version number). > > I just checked current and stable sources on ftp.freebsd.org, and it > appears that some things in aic7xxx.c haven't been committed to stable > yet, including changes to the NO_IDENT case. These changes leave out the > panic. just wondering... i had to break apart my ccd last weekend, after having serious probs with it, though i'm not sure they're ahc oriented, but it appears to be... (i have posted error msgs earlier) is there known prob with ccd and changing versions without twiddling with the system? coz i originally fired up the ccd on 2.1.5 and went to 2.1.7 and then to stable and still fast disk i/o caused atleast scsi hangs... occasionally reboots... though i had one reboot without any messages for me to take a peek after weekend too, all the latest panics happened while doing daily. the ccd was hosed rather well, i got my data out from some ccdes, didnt even attempt from the ones that gave me most troubles coz i decided the information wasnt crucial... ofcourse, i might've suffered drive heatings too... (last error messages i had, had some SCBs stuff too, earlier ones only had "timed out when idle/data out phase") and slightly related question, why 2.1.7 -> 2.1-STABLE blew out chunks from /usr/ports? mickey
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703121529.RAA07609>