Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 May 2016 09:32:56 -0400
From:      Ken Merry <ken@freebsd.org>
To:        Olli Hauer <ohauer@gmx.de>
Cc:        "Oleg V. Nauman" <oleg@opentransfer.com>, current@freebsd.org
Subject:   Re: ATA? related trouble with r300299
Message-ID:  <4ACA80CF-8267-4AEA-8806-BD014B291953@freebsd.org>
In-Reply-To: <trinity-1450b7d1-7cdf-4a8b-9549-f7737cbfb56d-1464064938736@msvc-mesg-gmx002>
References:  <trinity-1450b7d1-7cdf-4a8b-9549-f7737cbfb56d-1464064938736@msvc-mesg-gmx002>

next in thread | previous in thread | raw e-mail | index | archive | help
As Oleg mentioned, that was due to the compatibility shims for the old =
ATA layer getting removed.  The only thing required to get those =
machines to boot would be to change /dev/ad* in /boot/loader.conf to the =
correct /dev/ada device.

Ken
=E2=80=94=20
Ken Merry
ken@FreeBSD.ORG



> On May 24, 2016, at 12:42 AM, Olli Hauer <ohauer@gmx.de> wrote:
>=20
> Not sure, but maybe related.
> I had 5 old ata systems running, doing ntp and dns cache (running =
since 5.0 lifted over time to 10.x) The systems showed no smart or any =
other defects.=20
> Last year they began stop working with strange messages like adaX not =
found where in fstab still was ataX (back from 5.x) ...
> Meanwhile the systems are replaced and thrown away.
> If from interest i can look for old logs.
>=20
>=20
> On 23/05/2016, 21:25 "Kenneth D. Merry" <ken@FreeBSD.ORG> wrote:
> On Sat, May 21, 2016 at 09:30:35 +0300, Oleg V. Nauman wrote:
> >
> > I have faced the issue with fresh CURRENT stopped to boot on my old =
desktop
> > after update to r300299
> > Verbose boot shows the endless cycle of
> >
> > ata2: SATA reset: ports status=3D0x05
> > ata2: reset tp1 mask=3D03 ostat0=3D50 ostat1=3D50
> > ata2: stat0=3D0x50 err=3D0x01 lsb=3D0x00 msb=3D0x00
> > ata2: stat1=3D0x50 err=3D0x01 lsb=3D0x00 msb=3D0x00
> > ata2: reset tp2 stat0=3D50 stat1=3D50 devices=3D0x3
> > messages logged to console.
> >
> > Below is the relevant portion of ATA controller/devices =
probed/attached during
> > the boot:
> >
> > atapci0: <Intel ICH7 UDMA100 controller> port
> > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on =
pci0
> > ata0: <ATA channel> at channel 0 on atapci0
> > atapci1: <Intel ICH7 SATA300 controller> port 0xd080-0xd087, =
0xd000-0xd003,
> > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on =
pci0
> > ata2: <ATA channel> at channel 0 on atapci1
> > ata3: <ATA channel> at channel 1 on atapci1
> > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > ada0: <SAMSUNG HD200HJ KF100-06> ATA-7 SATA 2.x device
> > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > ada1: <ST500DM002-1BC142 JC4B> ATA8-ACS SATA 3.x device
> > cd0 at ata0 bus 0 scbus0 target 0 lun 0
> > cd0: <_NEC DVD_RW ND-3570A 1.11> Removable CD-ROM SCSI device
>=20
> I'm not entirely sure what is causing the problem with your system, =
but
> hopefully we can narrow it down a bit.
>=20
> There is a bug that came in with my SMR changes in revision 300207 =
that
> broke the quirk functionality in the ada(4) driver. I don't think that =
is
> the problem you're seeing, though.
>=20
> Can you try out this patch:
>=20
> https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt =
<https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt>;
>=20
> In /boot/loader.conf, put the following:
>=20
> kern.cam.ada.0.quirks=3D"0x04"
> kern.cam.ada.1.quirks=3D"0x04"
>=20
> If you're able to boot with those quirk entries in the loader.conf, =
try
> taking one of them out, and reboot. If that works, try taking the =
other
> one out and reboot.
>=20
> What I'm trying to figure out here is where the problem lies:
>=20
> 1. The bug with the ada(4) driver (in where it loaded the quirks).
> 2. The extra probe steps in the ada(4) driver might be causing a =
problem
> with ada0 (Samsung drive).
> 3. The extra probe steps in the ada(4) driver might be causing a =
problem
> with ada1 (Seagate drive).
> 4. Something else.
>=20
> So, if you can try the patch and try to eliminate a few possibilities, =
we
> may be able to narrow it down.
>=20
> Thanks,
>=20
> Ken
> --
> Kenneth Merry
> ken@FreeBSD.ORG
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current =
<https://lists.freebsd.org/mailman/listinfo/freebsd-current>;
> To unsubscribe, send any mail to =
"freebsd-current-unsubscribe@freebsd.org"
>=20




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ACA80CF-8267-4AEA-8806-BD014B291953>