Date: Wed, 2 May 2001 19:26:16 -0700 (PDT) From: iron-eagle@mailcity.com To: freebsd-gnats-submit@FreeBSD.org Subject: kern/27048: Bus support (I believe) broken in freeBSD 4.2 and above for whatever bus is found in a Compaq Presario 633 Message-ID: <200105030226.f432QGi24598@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 27048 >Category: kern >Synopsis: Bus support (I believe) broken in freeBSD 4.2 and above for whatever bus is found in a Compaq Presario 633 >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed May 02 19:30:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Gabriel Mastico >Release: 4.3 (upgraded from 4.1.1) >Organization: N/A >Environment: FreeBSD midnight.masticate.yi.org 4.3-RELEASE FreeBSD 4.3-RELEASE #0: Wed May 2 16:35:05 PDT 20001 root@midnight.masticate.yi.org:/usr/src/sys/compile/MIDNIGHT i386 >Description: I originally discovered this problem when I upgraded from 4.1.1 to 4.2, and found that I was getting 'hard errors' whenever any process tried to access the hard drive (these occured on boot as well). I then reinstalled 4.1.1, and waited for 4.3 to be released. I just rebuilt the system with the 4.3 code, and found that this same error is occuring. The error is as follows: The system is still (barely) functional, but I cannot perform any operation which would require a write to the disk (this is not quite true, writes to disk work occasionally). All read operations complete just fine, however. The following are example of the errors, as found in dmesg: ad0s1a: hard error writing fsbn 415 of 176-191 (ad0s1 bn 415; cn 0 tn 6 sn 37) status=51 error=04 ad0s1f: hard error writing fsbn 6003135 of 2884288-2884303 (ad0s1 bn 6003135; cn 1488 tn 56 sn 23) status=51 error=04 >How-To-Repeat: The only way to do this, I imagine, would be to attempt a write to the hard drive on the affected computer. As such, I am willing to give a developer ssh access to the affected computer, and root access if (as I suspect is the case) necessary. >Fix: Perhaps isolate what exactly has changed in the relevant code since 4.1.1, and return it to its original state. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105030226.f432QGi24598>