On Wed, May 25, 2016 at 07:35:06 +0700, Alex V. Petrov wrote:
>
>
> 25.05.16 03:18, Kenneth D. Merry ??:
> > On Tue, May 24, 2016 at 21:59:53 +0700, Alex V. Petrov wrote:
> >> 24.05.16 20:21, Kenneth D. Merry ??:
> >>> On Tue, May 24, 2016 at 08:04:21 +0300, Oleg V. Nauman wrote:
25.05.16 03:18, Kenneth D. Merry пишет:
> On Tue, May 24, 2016 at 21:59:53 +0700, Alex V. Petrov wrote:
>> 24.05.16 20:21, Kenneth D. Merry ??:
>>> On Tue, May 24, 2016 at 08:04:21 +0300, Oleg V. Nauman wrote:
On Monday 23 May 2016 19:08:16 Kenneth D. Merry wrote:
> On Tue, May 2
On 24/05/2016 21:56, Kenneth D. Merry wrote:
On Tue, May 24, 2016 at 23:54:09 +0300, Oleg V. Nauman wrote:
On Tuesday 24 May 2016 16:17:33 you wrote:
Okay, I've got a basic idea of what may be going on. The resets that are
getting sent are triggering another probe, which then triggers a rese
On Tue, May 24, 2016 at 23:54:09 +0300, Oleg V. Nauman wrote:
> On Tuesday 24 May 2016 16:17:33 you wrote:
> > Okay, I've got a basic idea of what may be going on. The resets that are
> > getting sent are triggering another probe, which then triggers a reset,
> > which triggers a probe...and so on
On Tuesday 24 May 2016 16:17:33 you wrote:
> Okay, I've got a basic idea of what may be going on. The resets that are
> getting sent are triggering another probe, which then triggers a reset,
> which triggers a probe...and so on.
>
> So here is another patch that should work for you:
>
> https:/
On Tue, May 24, 2016 at 21:59:53 +0700, Alex V. Petrov wrote:
> 24.05.16 20:21, Kenneth D. Merry ??:
> > On Tue, May 24, 2016 at 08:04:21 +0300, Oleg V. Nauman wrote:
> >> On Monday 23 May 2016 19:08:16 Kenneth D. Merry wrote:
> >>> On Tue, May 24, 2016 at 00:59:34 +0300, Oleg V. Nauman wro
On Tue, May 24, 2016 at 20:46:33 +0300, Oleg V. Nauman wrote:
> On Tuesday 24 May 2016 13:13:29 Kenneth D. Merry wrote:
> > On Tue, May 24, 2016 at 18:21:19 +0300, Oleg V. Nauman wrote:
> > > On Tuesday 24 May 2016 10:02:09 you wrote:
> > > > On Tue, May 24, 2016 at 16:38:40 +0300, Oleg V. Nauman w
On Tuesday 24 May 2016 13:13:29 Kenneth D. Merry wrote:
> On Tue, May 24, 2016 at 18:21:19 +0300, Oleg V. Nauman wrote:
> > On Tuesday 24 May 2016 10:02:09 you wrote:
> > > On Tue, May 24, 2016 at 16:38:40 +0300, Oleg V. Nauman wrote:
> > > > On Tuesday 24 May 2016 09:21:17 Kenneth D. Merry wrote:
On Tue, May 24, 2016 at 18:21:19 +0300, Oleg V. Nauman wrote:
> On Tuesday 24 May 2016 10:02:09 you wrote:
> > On Tue, May 24, 2016 at 16:38:40 +0300, Oleg V. Nauman wrote:
> > > On Tuesday 24 May 2016 09:21:17 Kenneth D. Merry wrote:
> > > > On Tue, May 24, 2016 at 08:04:21 +0300, Oleg V. Nauman w
On Tuesday 24 May 2016 10:02:09 you wrote:
> On Tue, May 24, 2016 at 16:38:40 +0300, Oleg V. Nauman wrote:
> > On Tuesday 24 May 2016 09:21:17 Kenneth D. Merry wrote:
> > > On Tue, May 24, 2016 at 08:04:21 +0300, Oleg V. Nauman wrote:
> > > > On Monday 23 May 2016 19:08:16 Kenneth D. Merry wrote:
>
24.05.16 20:21, Kenneth D. Merry пишет:
> On Tue, May 24, 2016 at 08:04:21 +0300, Oleg V. Nauman wrote:
>> On Monday 23 May 2016 19:08:16 Kenneth D. Merry wrote:
>>> On Tue, May 24, 2016 at 00:59:34 +0300, Oleg V. Nauman wrote:
On Monday 23 May 2016 17:30:45 you wrote:
> On Tue, May 24, 20
On Tue, May 24, 2016 at 16:38:40 +0300, Oleg V. Nauman wrote:
> On Tuesday 24 May 2016 09:21:17 Kenneth D. Merry wrote:
> > On Tue, May 24, 2016 at 08:04:21 +0300, Oleg V. Nauman wrote:
> > > On Monday 23 May 2016 19:08:16 Kenneth D. Merry wrote:
> > > > On Tue, May 24, 2016 at 00:59:34 +0300, Oleg
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
—
Ken Merry
k...@freebsd.org
> On May 24, 2016, at 12:
On Tuesday 24 May 2016 09:21:17 Kenneth D. Merry wrote:
> On Tue, May 24, 2016 at 08:04:21 +0300, Oleg V. Nauman wrote:
> > On Monday 23 May 2016 19:08:16 Kenneth D. Merry wrote:
> > > On Tue, May 24, 2016 at 00:59:34 +0300, Oleg V. Nauman wrote:
> > > > On Monday 23 May 2016 17:30:45 you wrote:
>
On Tue, May 24, 2016 at 08:04:21 +0300, Oleg V. Nauman wrote:
> On Monday 23 May 2016 19:08:16 Kenneth D. Merry wrote:
> > On Tue, May 24, 2016 at 00:59:34 +0300, Oleg V. Nauman wrote:
> > > On Monday 23 May 2016 17:30:45 you wrote:
> > > > On Tue, May 24, 2016 at 00:15:25 +0300, Oleg V. Nauman wro
On Tuesday 24 May 2016 06:42:18 you wrote:
> 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.
> Last year they began stop working with strange messages like adaX n
On Monday 23 May 2016 19:08:16 Kenneth D. Merry wrote:
> On Tue, May 24, 2016 at 00:59:34 +0300, Oleg V. Nauman wrote:
> > On Monday 23 May 2016 17:30:45 you wrote:
> > > On Tue, May 24, 2016 at 00:15:25 +0300, Oleg V. Nauman wrote:
> > > > On Monday 23 May 2016 17:11:34 Kenneth D. Merry wrote:
> >
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Tue, May 24, 2016 at 00:59:34 +0300, Oleg V. Nauman wrote:
> On Monday 23 May 2016 17:30:45 you wrote:
> > On Tue, May 24, 2016 at 00:15:25 +0300, Oleg V. Nauman wrote:
> > > On Monday 23 May 2016 17:11:34 Kenneth D. Merry wrote:
> > > > On Tue, May 24, 2016 at 00:05:49 +0300, Oleg V. Nauman wro
On Monday 23 May 2016 17:30:45 you wrote:
> On Tue, May 24, 2016 at 00:15:25 +0300, Oleg V. Nauman wrote:
> > On Monday 23 May 2016 17:11:34 Kenneth D. Merry wrote:
> > > On Tue, May 24, 2016 at 00:05:49 +0300, Oleg V. Nauman wrote:
> > > > On Monday 23 May 2016 16:53:55 Kenneth D. Merry wrote:
> >
On Tue, May 24, 2016 at 00:15:25 +0300, Oleg V. Nauman wrote:
> On Monday 23 May 2016 17:11:34 Kenneth D. Merry wrote:
> > On Tue, May 24, 2016 at 00:05:49 +0300, Oleg V. Nauman wrote:
> > > On Monday 23 May 2016 16:53:55 Kenneth D. Merry wrote:
> > > > On Mon, May 23, 2016 at 23:21:32 +0300, Oleg
On Monday 23 May 2016 17:11:34 Kenneth D. Merry wrote:
> On Tue, May 24, 2016 at 00:05:49 +0300, Oleg V. Nauman wrote:
> > On Monday 23 May 2016 16:53:55 Kenneth D. Merry wrote:
> > > On Mon, May 23, 2016 at 23:21:32 +0300, Oleg V. Nauman wrote:
> > > > On Monday 23 May 2016 15:25:39 Kenneth D. Mer
On Tue, May 24, 2016 at 00:05:49 +0300, Oleg V. Nauman wrote:
> On Monday 23 May 2016 16:53:55 Kenneth D. Merry wrote:
> > On Mon, May 23, 2016 at 23:21:32 +0300, Oleg V. Nauman wrote:
> > > On Monday 23 May 2016 15:25:39 Kenneth D. Merry wrote:
> > > > On Sat, May 21, 2016 at 09:30:35 +0300, Oleg
On Monday 23 May 2016 16:53:55 Kenneth D. Merry wrote:
> On Mon, May 23, 2016 at 23:21:32 +0300, Oleg V. Nauman wrote:
> > On Monday 23 May 2016 15:25:39 Kenneth D. Merry wrote:
> > > On Sat, May 21, 2016 at 09:30:35 +0300, Oleg V. Nauman wrote:
> > > > I have faced the issue with fresh CURRENT st
On Mon, May 23, 2016 at 23:21:32 +0300, Oleg V. Nauman wrote:
> On Monday 23 May 2016 15:25:39 Kenneth D. Merry 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 updat
On Monday 23 May 2016 15:25:39 Kenneth D. Merry 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: SA
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=0x05
> ata2: reset tp1 mask=03 ostat0=50 ostat1=5
27 matches
Mail list logo