Date: Wed, 22 Jan 2003 07:31:30 -0800 From: Nathan Kinkade <nkinkade@dsl-only.net> To: questions@freebsd.org Subject: Re: ata1 resetting Message-ID: <20030122153130.GI25795@sub21-156.member.dsl-only.net> In-Reply-To: <20030122075114.Y4174-100000@voo.doo.net> References: <20030122075114.Y4174-100000@voo.doo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--nO3oAMapP4dBpMZi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 22, 2003 at 07:58:31AM +0100, Marc Schneiders wrote: > Does someone see some sort of pattern in the times (from > /var/log/messages) below? I do but know not what. >=20 > And what could explain it? >=20 > Please, note that it occurs on both harddisks and on both controllers. >=20 > Something cron related? Something swap related, since there is swap > space on both disks? I think, however, that swap is hardly used: >=20 > Device 1K-blocks Used Avail Capacity Type > /dev/ad0s1b 524160 16 524144 0% Interleaved > /dev/rad2b 524160 0 524160 0% Interleaved > Total 1048320 16 1048304 0% >=20 <snip> >=20 > Jan 21 18:49:40 pan /kernel: ad2: WRITE command timeout tag=3D0 serv=3D0 - > resetting > Jan 21 18:49:40 pan /kernel: ata1: resetting devices .. ata1-slave: > ATA identify retries exceeded > Jan 21 18:49:40 pan /kernel: done > Jan 21 19:47:39 pan /kernel: ad2: WRITE command timeout tag=3D0 serv=3D0 - > resetting > Jan 21 19:47:39 pan /kernel: ata1: resetting devices .. ata1-slave: > ATA identify retries exceeded > Jan 21 19:47:39 pan /kernel: done > Jan 21 22:06:39 pan /kernel: ad0: WRITE command timeout tag=3D0 serv=3D0 - > resetting <snip> Do you have DMA enabled on those drives when possibly they don't support it? What type of ribbon cable are you using - a 40 or 80 conductor? Try setting the sysctl(8) value "hw.ata.ata_dmai" to 0 and see what results you get. The errors you are getting look similar to ones I've seen where the kernel is trying to use DMA on a drive that doesn't support it, or on a drive that supports DMA that is using an improper 40 conductor cable instead of the correct 80 conductor cable. You can use the atacontrol(8) utilitly to find out more about the capabilities of your devices. For example, `atacontrol cap 0 0` should give you all manner of info about your primary master ATA device. If you want to set the value of "hw.ata.ata_dma" on boot, you will have to put the command in the file /boot/loader.conf as a line with the text "hw.ata.ata_dma=3D0". It needs to go here rather /etc/sysctl.conf because by the time /etc/sysctl.conf is processes the disk subsystems have already been activated. Nathan --=20 GPG Public Key ID: 0x4250A04C gpg --keyserver pgp.mit.edu --recv-keys 4250A04C http://63.105.21.156/gpg_nkinkade_4250A04C.asc --nO3oAMapP4dBpMZi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+LrlSWZYS9EJQoEwRAgCzAKCNtxHNYjKhtVEzDbivroUzC8kWjwCfVuv1 i4BDkQ/rvPSjaiRoqRNrJhQ= =BZjd -----END PGP SIGNATURE----- --nO3oAMapP4dBpMZi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030122153130.GI25795>