Re: ATA? related trouble with r300299

[Kenneth D. Merry]

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:
>  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:
> > 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 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=50
> >> ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> >> ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> >> ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> >> messages logged to console.
> >>
> >> Below is the relevant portion of ATA controller/devices
> >> probed/attached
> >> during the boot:
> >>
> >> atapci0:  port
> >> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at
> >> device
> >> 31.1
> >> on
> >> pci0
> >> ata0:  at channel 0 on atapci0
> >> atapci1:  port
> >> 0xd080-0xd087,
> >> 0xd000-0xd003,
> >> 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device
> >> 31.2 on
> >> pci0
> >> ata2:  at channel 0 on atapci1
> >> ata3:  at channel 1 on atapci1
> >> ada0 at ata2 bus 0 scbus1 target 0 lun 0
> >> ada0:  ATA-7 SATA 2.x device
> >> ada1 at ata2 bus 0 scbus1 target 1 lun 0
> >> ada1:  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
> >
> > I'm not entirely sure what is causing the problem with your
> > system,
> > but
> > hopefully we can narrow it down a bit.
> >
> > 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.
> >
> > Can you try out this patch:
> >
> > https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1
> > .txt
> >
> > In /boot/loader.conf, put the following:
> >
> > kern.cam.ada.0.quirks="0x04"
> > kern.cam.ada.1.quirks="0x04"
> >
> > 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.
> >
> > What I'm trying to figure out here is where the problem
> > lies:
> >
> > 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.
> >
> > So, if you can try the patch and try to eliminate a few
> > possibilities,
> > we
> > may be able to narrow it down.
>   
>   I was able to boot after applying the patch ;
> 
>  kern.cam.ada.0.quirks="0x04"
>  was the quirk in effect. It is quirk for my Samsung HD200HJ
>  KF100-06
> 

Re: ATA? related trouble with r300299

[Alex V. Petrov]

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 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 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 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=50
>> ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
>> ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
>> ata2: reset tp2 stat0=50 stat1=50 devices=0x3
>> messages logged to console.
>>
>> Below is the relevant portion of ATA controller/devices
>> probed/attached
>> during the boot:
>>
>> atapci0:  port
>> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at
>> device
>> 31.1
>> on
>> pci0
>> ata0:  at channel 0 on atapci0
>> atapci1:  port
>> 0xd080-0xd087,
>> 0xd000-0xd003,
>> 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device
>> 31.2 on
>> pci0
>> ata2:  at channel 0 on atapci1
>> ata3:  at channel 1 on atapci1
>> ada0 at ata2 bus 0 scbus1 target 0 lun 0
>> ada0:  ATA-7 SATA 2.x device
>> ada1 at ata2 bus 0 scbus1 target 1 lun 0
>> ada1:  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
>
> I'm not entirely sure what is causing the problem with your
> system,
> but
> hopefully we can narrow it down a bit.
>
> 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.
>
> Can you try out this patch:
>
> https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1
> .txt
>
> In /boot/loader.conf, put the following:
>
> kern.cam.ada.0.quirks="0x04"
> kern.cam.ada.1.quirks="0x04"
>
> 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.
>
> What I'm trying to figure out here is where the problem
> lies:
>
> 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.
>
> So, if you can try the patch and try to eliminate a few
> possibilities,
> we
> may be able to narrow it down.
  
  I was able to boot after applying the patch ;

 kern.cam.ada.0.quirks="0x04"
 was the quirk in effect. It is quirk for my Samsung HD200HJ
 KF100-06
 hard
 drive.
>>>
>>> Okay.  Just so we can narrow it down a little more, can you try
>>> this:
>>>
>>> First, let's try getting an ATA Log directory using the PIO
>>> version
>>> of
>>> the
>>> command:
>>>
>>> 

Re: ATA? related trouble with r300299

[Steven Hartland]

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 reset,
which triggers a probe...and so on.

So here is another patch that should work for you:

https://people.freebsd.org/~ken/cam_smr_ada_patch.20160524.2.txt

I have commented out the quirk for this drive, and the driver will now only
start the SMR probe on drives that claim to be SMR-capable.  So, for the
vast majority of drives out there right now, it won't even start the extra
probe steps.

  It fixes this issue. I was able to boot with your latest patch.

Great!  I'll check it in with that fix as well as a quirk entry.  That way,
if we have other reasons later on to issue a read log, we'll know that
it doesn't work for those drives.
Might be worth seeing if smartmontools can read the log from that drive 
before committing the quirk as a double check.


Regards
Steve

___
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"

Re: ATA? related trouble with r300299

[Kenneth D. Merry]

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.
> > 
> > So here is another patch that should work for you:
> > 
> > https://people.freebsd.org/~ken/cam_smr_ada_patch.20160524.2.txt
> > 
> > I have commented out the quirk for this drive, and the driver will now only
> > start the SMR probe on drives that claim to be SMR-capable.  So, for the
> > vast majority of drives out there right now, it won't even start the extra
> > probe steps.
> 
>  It fixes this issue. I was able to boot with your latest patch.

Great!  I'll check it in with that fix as well as a quirk entry.  That way,
if we have other reasons later on to issue a read log, we'll know that
it doesn't work for those drives.

Ken
-- 
Kenneth Merry
k...@freebsd.org
___
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"

Re: ATA? related trouble with r300299

[Oleg V. Nauman]

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://people.freebsd.org/~ken/cam_smr_ada_patch.20160524.2.txt
> 
> I have commented out the quirk for this drive, and the driver will now only
> start the SMR probe on drives that claim to be SMR-capable.  So, for the
> vast majority of drives out there right now, it won't even start the extra
> probe steps.

 It fixes this issue. I was able to boot with your latest patch.

Thank you!

> 
> Ken

___
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"

Re: ATA? related trouble with r300299

[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 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 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 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=50
>  ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
>  ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
>  ata2: reset tp2 stat0=50 stat1=50 devices=0x3
>  messages logged to console.
> 
>  Below is the relevant portion of ATA controller/devices
>  probed/attached
>  during the boot:
> 
>  atapci0:  port
>  0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at
>  device
>  31.1
>  on
>  pci0
>  ata0:  at channel 0 on atapci0
>  atapci1:  port
>  0xd080-0xd087,
>  0xd000-0xd003,
>  0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device
>  31.2 on
>  pci0
>  ata2:  at channel 0 on atapci1
>  ata3:  at channel 1 on atapci1
>  ada0 at ata2 bus 0 scbus1 target 0 lun 0
>  ada0:  ATA-7 SATA 2.x device
>  ada1 at ata2 bus 0 scbus1 target 1 lun 0
>  ada1:  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
> >>>
> >>> I'm not entirely sure what is causing the problem with your
> >>> system,
> >>> but
> >>> hopefully we can narrow it down a bit.
> >>>
> >>> 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.
> >>>
> >>> Can you try out this patch:
> >>>
> >>> https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1
> >>> .txt
> >>>
> >>> In /boot/loader.conf, put the following:
> >>>
> >>> kern.cam.ada.0.quirks="0x04"
> >>> kern.cam.ada.1.quirks="0x04"
> >>>
> >>> 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.
> >>>
> >>> What I'm trying to figure out here is where the problem
> >>> lies:
> >>>
> >>> 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.
> >>>
> >>> So, if you can try the patch and try to eliminate a few
> >>> possibilities,
> >>> we
> >>> may be able to narrow it down.
> >>  
> >>  I was able to boot after applying the patch ;
> >>
> >> kern.cam.ada.0.quirks="0x04"
> >> was the quirk in effect. It is quirk for my Samsung HD200HJ
> >> KF100-06
> >> hard
> >> drive.
> >
> > Okay.  Just so we can narrow it down a little more, can you try
> > this:
> >
> > First, let's try getting an ATA Log directory using the PIO
> > version
> > of
> > the
> > command:
> >
> > camcontrol cmd ada0 -v -a "2f 0 0 0 0 0 0 0 

Re: ATA? related trouble with r300299

[Kenneth D. Merry]

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 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 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
> > > 
> > > 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 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=50
> > > > > > > > > > > > > > > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > > > > > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > > > > > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > > > > > > > > > > > > > > messages logged to console.
> > > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > > Below is the relevant portion of ATA
> > > > > > > > > > > > > > > > > controller/devices
> > > > > > > > > > > > > > > > > probed/attached
> > > > > > > > > > > > > > > > > during the boot:
> > > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > > atapci0:  port
> > > > > > > > > > > > > > > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xf
> > > > > > > > > > > > > > > > > faf
> > > > > > > > > > > > > > > > > at
> > > > > > > > > > > > > > > > > device
> > > > > > > > > > > > > > > > > 31.1
> > > > > > > > > > > > > > > > > on
> > > > > > > > > > > > > > > > > pci0
> > > > > > > > > > > > > > > > > ata0:  at channel 0 on atapci0
> > > > > > > > > > > > > > > > > atapci1:  port
> > > > > > > > > > > > > > > > > 0xd080-0xd087,
> > > > > > > > > > > > > > > > > 0xd000-0xd003,
> > > > > > > > > > > > > > > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq
> > > > > > > > > > > > > > > > > 19
> > > > > > > > > > > > > > > > > at
> > > > > > > > > > > > > > > > > device
> > > > > > > > > > > > > > > > > 31.2 on
> > > > > > > > > > > > > > > > > pci0
> > > > > > > > > > > > > > > > > ata2:  at channel 0 on atapci1
> > > > > > > > > > > > > > > > > ata3:  at channel 1 on atapci1
> > > > > > > > > > > > > > > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > > > > > > > > > > > > > > ada0:  ATA-7 SATA
> > > > > > > > > > > > > > > > > 2.x
> > > > > > > > > > > > > > > > > device
> > > > > > > > > > > > > > > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > > > > > > > > > > > > > > ada1:  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
> > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > I'm not entirely sure what is causing the
> > > > > > > > > > > > > > > > problem
> > > > > > > > > > > > > > > > with
> > > > > > > > > > > > > > > > your
> > > > > > > > > > > > > > > > system,
> > > > > > > > > > > > > > > > but
> > > > > > > > > > > > > > > > hopefully we can narrow it down a bit.
> > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > There is a bug that came in with my SMR changes
> > > > > > > > > > > > > > > > in
> > > > > > > > > > > > > > > > revision
> > > > > > > > > > > > > > > > 300207
> > > > > > > > > > > > > > > > that
> > > > > > > > > > > > 

Re: ATA? related trouble with r300299

[Oleg V. Nauman]

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 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 
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 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 update to r300299
> > > > > > > > > > > > > > > > Verbose boot shows the endless cycle of
> > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > ata2: SATA reset: ports status=0x05
> > > > > > > > > > > > > > > > ata2: reset tp1 mask=03 ostat0=50 ostat1=50
> > > > > > > > > > > > > > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > > > > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > > > > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > > > > > > > > > > > > > messages logged to console.
> > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > Below is the relevant portion of ATA
> > > > > > > > > > > > > > > > controller/devices
> > > > > > > > > > > > > > > > probed/attached
> > > > > > > > > > > > > > > > during the boot:
> > > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > > atapci0:  port
> > > > > > > > > > > > > > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xf
> > > > > > > > > > > > > > > > faf
> > > > > > > > > > > > > > > > at
> > > > > > > > > > > > > > > > device
> > > > > > > > > > > > > > > > 31.1
> > > > > > > > > > > > > > > > on
> > > > > > > > > > > > > > > > pci0
> > > > > > > > > > > > > > > > ata0:  at channel 0 on atapci0
> > > > > > > > > > > > > > > > atapci1:  port
> > > > > > > > > > > > > > > > 0xd080-0xd087,
> > > > > > > > > > > > > > > > 0xd000-0xd003,
> > > > > > > > > > > > > > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq
> > > > > > > > > > > > > > > > 19
> > > > > > > > > > > > > > > > at
> > > > > > > > > > > > > > > > device
> > > > > > > > > > > > > > > > 31.2 on
> > > > > > > > > > > > > > > > pci0
> > > > > > > > > > > > > > > > ata2:  at channel 0 on atapci1
> > > > > > > > > > > > > > > > ata3:  at channel 1 on atapci1
> > > > > > > > > > > > > > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > > > > > > > > > > > > > ada0:  ATA-7 SATA
> > > > > > > > > > > > > > > > 2.x
> > > > > > > > > > > > > > > > device
> > > > > > > > > > > > > > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > > > > > > > > > > > > > ada1:  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
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > I'm not entirely sure what is causing the
> > > > > > > > > > > > > > > problem
> > > > > > > > > > > > > > > with
> > > > > > > > > > > > > > > your
> > > > > > > > > > > > > > > system,
> > > > > > > > > > > > > > > but
> > > > > > > > > > > > > > > hopefully we can narrow it down a bit.
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > 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
> > > > > > > > > > > > > > > 

Re: ATA? related trouble with r300299

[Kenneth D. Merry]

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 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 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 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 update to r300299
> > > > > > > > > > > > > > > Verbose boot shows the endless cycle of
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > ata2: SATA reset: ports status=0x05
> > > > > > > > > > > > > > > ata2: reset tp1 mask=03 ostat0=50 ostat1=50
> > > > > > > > > > > > > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > > > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > > > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > > > > > > > > > > > > messages logged to console.
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > Below is the relevant portion of ATA
> > > > > > > > > > > > > > > controller/devices
> > > > > > > > > > > > > > > probed/attached
> > > > > > > > > > > > > > > during the boot:
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > atapci0:  port
> > > > > > > > > > > > > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf
> > > > > > > > > > > > > > > at
> > > > > > > > > > > > > > > device
> > > > > > > > > > > > > > > 31.1
> > > > > > > > > > > > > > > on
> > > > > > > > > > > > > > > pci0
> > > > > > > > > > > > > > > ata0:  at channel 0 on atapci0
> > > > > > > > > > > > > > > atapci1:  port
> > > > > > > > > > > > > > > 0xd080-0xd087,
> > > > > > > > > > > > > > > 0xd000-0xd003,
> > > > > > > > > > > > > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19
> > > > > > > > > > > > > > > at
> > > > > > > > > > > > > > > device
> > > > > > > > > > > > > > > 31.2 on
> > > > > > > > > > > > > > > pci0
> > > > > > > > > > > > > > > ata2:  at channel 0 on atapci1
> > > > > > > > > > > > > > > ata3:  at channel 1 on atapci1
> > > > > > > > > > > > > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > > > > > > > > > > > > ada0:  ATA-7 SATA 2.x
> > > > > > > > > > > > > > > device
> > > > > > > > > > > > > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > > > > > > > > > > > > ada1:  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
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > I'm not entirely sure what is causing the problem
> > > > > > > > > > > > > > with
> > > > > > > > > > > > > > your
> > > > > > > > > > > > > > system,
> > > > > > > > > > > > > > but
> > > > > > > > > > > > > > hopefully we can narrow it down a bit.
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > 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.
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > Can you try out this patch:
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > https://people.freebsd.org/~ken/cam_smr_ada_patch.20
> > > > > > > > > > > > > > 1605
> > > > > > > > > > > > > > 23.1
> > > > > > > > > > > > > > .txt
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > In /boot/loader.conf, put the following:
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > kern.cam.ada.0.quirks="0x04"
> > > 

Re: ATA? related trouble with r300299

[Oleg V. Nauman]

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:
> > > > > 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 
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 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=50
> > > > > > > > > > > > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > > > > > > > > > > > messages logged to console.
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > Below is the relevant portion of ATA
> > > > > > > > > > > > > > controller/devices
> > > > > > > > > > > > > > probed/attached
> > > > > > > > > > > > > > during the boot:
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > atapci0:  port
> > > > > > > > > > > > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf
> > > > > > > > > > > > > > at
> > > > > > > > > > > > > > device
> > > > > > > > > > > > > > 31.1
> > > > > > > > > > > > > > on
> > > > > > > > > > > > > > pci0
> > > > > > > > > > > > > > ata0:  at channel 0 on atapci0
> > > > > > > > > > > > > > atapci1:  port
> > > > > > > > > > > > > > 0xd080-0xd087,
> > > > > > > > > > > > > > 0xd000-0xd003,
> > > > > > > > > > > > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19
> > > > > > > > > > > > > > at
> > > > > > > > > > > > > > device
> > > > > > > > > > > > > > 31.2 on
> > > > > > > > > > > > > > pci0
> > > > > > > > > > > > > > ata2:  at channel 0 on atapci1
> > > > > > > > > > > > > > ata3:  at channel 1 on atapci1
> > > > > > > > > > > > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > > > > > > > > > > > ada0:  ATA-7 SATA 2.x
> > > > > > > > > > > > > > device
> > > > > > > > > > > > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > > > > > > > > > > > ada1:  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
> > > > > > > > > > > > > 
> > > > > > > > > > > > > I'm not entirely sure what is causing the problem
> > > > > > > > > > > > > with
> > > > > > > > > > > > > your
> > > > > > > > > > > > > system,
> > > > > > > > > > > > > but
> > > > > > > > > > > > > hopefully we can narrow it down a bit.
> > > > > > > > > > > > > 
> > > > > > > > > > > > > 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.
> > > > > > > > > > > > > 
> > > > > > > > > > > > > Can you try out this patch:
> > > > > > > > > > > > > 
> > > > > > > > > > > > > https://people.freebsd.org/~ken/cam_smr_ada_patch.20
> > > > > > > > > > > > > 1605
> > > > > > > > > > > > > 23.1
> > > > > > > > > > > > > .txt
> > > > > > > > > > > > > 
> > > > > > > > > > > > > In /boot/loader.conf, put the following:
> > > > > > > > > > > > > 
> > > > > > > > > > > > > kern.cam.ada.0.quirks="0x04"
> > > > > > > > > > > > > kern.cam.ada.1.quirks="0x04"
> > > > > > > > > > > > > 
> > > > > > > > > > > > > If you're able to boot with those quirk entries in
> > > > > > > > > > > > > the
> > > > > > > > > > > > > loader.conf,
> > > > > > > > > > > > > try
> > > > > > 

Re: ATA? related trouble with r300299

[Alex V. Petrov]

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, 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 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 update to r300299
 Verbose boot shows the endless cycle of

 ata2: SATA reset: ports status=0x05
 ata2: reset tp1 mask=03 ostat0=50 ostat1=50
 ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
 ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
 ata2: reset tp2 stat0=50 stat1=50 devices=0x3
 messages logged to console.

 Below is the relevant portion of ATA controller/devices
 probed/attached
 during the boot:

 atapci0:  port
 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at
 device
 31.1
 on
 pci0
 ata0:  at channel 0 on atapci0
 atapci1:  port
 0xd080-0xd087,
 0xd000-0xd003,
 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device
 31.2 on
 pci0
 ata2:  at channel 0 on atapci1
 ata3:  at channel 1 on atapci1
 ada0 at ata2 bus 0 scbus1 target 0 lun 0
 ada0:  ATA-7 SATA 2.x device
 ada1 at ata2 bus 0 scbus1 target 1 lun 0
 ada1:  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
>>>
>>> I'm not entirely sure what is causing the problem with your
>>> system,
>>> but
>>> hopefully we can narrow it down a bit.
>>>
>>> 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.
>>>
>>> Can you try out this patch:
>>>
>>> https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1
>>> .txt
>>>
>>> In /boot/loader.conf, put the following:
>>>
>>> kern.cam.ada.0.quirks="0x04"
>>> kern.cam.ada.1.quirks="0x04"
>>>
>>> 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.
>>>
>>> What I'm trying to figure out here is where the problem
>>> lies:
>>>
>>> 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.
>>>
>>> So, if you can try the patch and try to eliminate a few
>>> possibilities,
>>> we
>>> may be able to narrow it down.
>>  
>>  I was able to boot after applying the patch ;
>>
>> kern.cam.ada.0.quirks="0x04"
>> was the quirk in effect. It is quirk for my Samsung HD200HJ
>> KF100-06
>> hard
>> drive.
>
> Okay.  Just so we can narrow it down a little more, can you try
> this:
>
> First, let's try getting an ATA Log directory using the PIO
> version
> of
> the
> command:
>
> camcontrol cmd ada0 -v -a "2f 0 0 0 0 0 0 0 0 0 1 0" -i 512 -
> |hd
>
> If that works (you should get hexdump output), try the DMA
> version
> of
> the
> command:
>
> camcontrol cmd ada0 -v -d -a "47 0 0 0 0 0 0 0 0 0 1 0" -i 512 -
> |hd

 "Expecting a character pointer 

Re: ATA? related trouble with r300299

[Kenneth D. Merry]

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 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 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 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=50
> > > > > > > > > > > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > > > > > > > > > > messages logged to console.
> > > > > > > > > > > > > 
> > > > > > > > > > > > > Below is the relevant portion of ATA
> > > > > > > > > > > > > controller/devices
> > > > > > > > > > > > > probed/attached
> > > > > > > > > > > > > during the boot:
> > > > > > > > > > > > > 
> > > > > > > > > > > > > atapci0:  port
> > > > > > > > > > > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at
> > > > > > > > > > > > > device
> > > > > > > > > > > > > 31.1
> > > > > > > > > > > > > on
> > > > > > > > > > > > > pci0
> > > > > > > > > > > > > ata0:  at channel 0 on atapci0
> > > > > > > > > > > > > atapci1:  port
> > > > > > > > > > > > > 0xd080-0xd087,
> > > > > > > > > > > > > 0xd000-0xd003,
> > > > > > > > > > > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at
> > > > > > > > > > > > > device
> > > > > > > > > > > > > 31.2 on
> > > > > > > > > > > > > pci0
> > > > > > > > > > > > > ata2:  at channel 0 on atapci1
> > > > > > > > > > > > > ata3:  at channel 1 on atapci1
> > > > > > > > > > > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > > > > > > > > > > ada0:  ATA-7 SATA 2.x device
> > > > > > > > > > > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > > > > > > > > > > ada1:  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
> > > > > > > > > > > > 
> > > > > > > > > > > > I'm not entirely sure what is causing the problem with
> > > > > > > > > > > > your
> > > > > > > > > > > > system,
> > > > > > > > > > > > but
> > > > > > > > > > > > hopefully we can narrow it down a bit.
> > > > > > > > > > > > 
> > > > > > > > > > > > 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.
> > > > > > > > > > > > 
> > > > > > > > > > > > Can you try out this patch:
> > > > > > > > > > > > 
> > > > > > > > > > > > https://people.freebsd.org/~ken/cam_smr_ada_patch.201605
> > > > > > > > > > > > 23.1
> > > > > > > > > > > > .txt
> > > > > > > > > > > > 
> > > > > > > > > > > > In /boot/loader.conf, put the following:
> > > > > > > > > > > > 
> > > > > > > > > > > > kern.cam.ada.0.quirks="0x04"
> > > > > > > > > > > > kern.cam.ada.1.quirks="0x04"
> > > > > > > > > > > > 
> > > > > > > > > > > > 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.
> > > > > > > > > > > > 
> > > > > > > > > > > > What I'm trying to figure out here is where the problem
> > > > > > > > > > > > lies:
> > > > > > > > > > > > 
> > > > > > > > > > > > 1. The bug with the ada(4) driver (in where it loaded
> > > > > > > > > > > > the
> > > > > > > > > > > > quirks).
> > > > 

Re: ATA? related trouble with r300299

[Ken Merry]

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:42 AM, Olli Hauer  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 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.
> 
> 
> On 23/05/2016, 21:25 "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: SATA reset: ports status=0x05
> > ata2: reset tp1 mask=03 ostat0=50 ostat1=50
> > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > messages logged to console.
> >
> > Below is the relevant portion of ATA controller/devices probed/attached 
> > during
> > the boot:
> >
> > atapci0:  port
> > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0
> > ata0:  at channel 0 on atapci0
> > atapci1:  port 0xd080-0xd087, 0xd000-0xd003,
> > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on pci0
> > ata2:  at channel 0 on atapci1
> > ata3:  at channel 1 on atapci1
> > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > ada0:  ATA-7 SATA 2.x device
> > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > ada1:  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
> 
> I'm not entirely sure what is causing the problem with your system, but
> hopefully we can narrow it down a bit.
> 
> 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.
> 
> Can you try out this patch:
> 
> https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt 
> 
> 
> In /boot/loader.conf, put the following:
> 
> kern.cam.ada.0.quirks="0x04"
> kern.cam.ada.1.quirks="0x04"
> 
> 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.
> 
> What I'm trying to figure out here is where the problem lies:
> 
> 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.
> 
> So, if you can try the patch and try to eliminate a few possibilities, we
> may be able to narrow it down.
> 
> Thanks,
> 
> Ken
> --
> Kenneth Merry
> k...@freebsd.org
> ___
> 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"
> 

___
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"

Re: ATA? related trouble with r300299

[Oleg V. Nauman]

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 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 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 update to r300299
> > > > > > > > > > > > Verbose boot shows the endless cycle of
> > > > > > > > > > > > 
> > > > > > > > > > > > ata2: SATA reset: ports status=0x05
> > > > > > > > > > > > ata2: reset tp1 mask=03 ostat0=50 ostat1=50
> > > > > > > > > > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > > > > > > > > > messages logged to console.
> > > > > > > > > > > > 
> > > > > > > > > > > > Below is the relevant portion of ATA
> > > > > > > > > > > > controller/devices
> > > > > > > > > > > > probed/attached
> > > > > > > > > > > > during the boot:
> > > > > > > > > > > > 
> > > > > > > > > > > > atapci0:  port
> > > > > > > > > > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at
> > > > > > > > > > > > device
> > > > > > > > > > > > 31.1
> > > > > > > > > > > > on
> > > > > > > > > > > > pci0
> > > > > > > > > > > > ata0:  at channel 0 on atapci0
> > > > > > > > > > > > atapci1:  port
> > > > > > > > > > > > 0xd080-0xd087,
> > > > > > > > > > > > 0xd000-0xd003,
> > > > > > > > > > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at
> > > > > > > > > > > > device
> > > > > > > > > > > > 31.2 on
> > > > > > > > > > > > pci0
> > > > > > > > > > > > ata2:  at channel 0 on atapci1
> > > > > > > > > > > > ata3:  at channel 1 on atapci1
> > > > > > > > > > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > > > > > > > > > ada0:  ATA-7 SATA 2.x device
> > > > > > > > > > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > > > > > > > > > ada1:  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
> > > > > > > > > > > 
> > > > > > > > > > > I'm not entirely sure what is causing the problem with
> > > > > > > > > > > your
> > > > > > > > > > > system,
> > > > > > > > > > > but
> > > > > > > > > > > hopefully we can narrow it down a bit.
> > > > > > > > > > > 
> > > > > > > > > > > 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.
> > > > > > > > > > > 
> > > > > > > > > > > Can you try out this patch:
> > > > > > > > > > > 
> > > > > > > > > > > https://people.freebsd.org/~ken/cam_smr_ada_patch.201605
> > > > > > > > > > > 23.1
> > > > > > > > > > > .txt
> > > > > > > > > > > 
> > > > > > > > > > > In /boot/loader.conf, put the following:
> > > > > > > > > > > 
> > > > > > > > > > > kern.cam.ada.0.quirks="0x04"
> > > > > > > > > > > kern.cam.ada.1.quirks="0x04"
> > > > > > > > > > > 
> > > > > > > > > > > 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.
> > > > > > > > > > > 
> > > > > > > > > > > What I'm trying to figure out here is where the problem
> > > > > > > > > > > lies:
> > > > > > > > > > > 
> > > > > > > > > > > 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 

Re: ATA? related trouble with r300299

[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, 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 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 update to r300299
> > > > > > > > > > > Verbose boot shows the endless cycle of
> > > > > > > > > > > 
> > > > > > > > > > > ata2: SATA reset: ports status=0x05
> > > > > > > > > > > ata2: reset tp1 mask=03 ostat0=50 ostat1=50
> > > > > > > > > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > > > > > > > > messages logged to console.
> > > > > > > > > > > 
> > > > > > > > > > > Below is the relevant portion of ATA controller/devices
> > > > > > > > > > > probed/attached
> > > > > > > > > > > during the boot:
> > > > > > > > > > > 
> > > > > > > > > > > atapci0:  port
> > > > > > > > > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at
> > > > > > > > > > > device
> > > > > > > > > > > 31.1
> > > > > > > > > > > on
> > > > > > > > > > > pci0
> > > > > > > > > > > ata0:  at channel 0 on atapci0
> > > > > > > > > > > atapci1:  port
> > > > > > > > > > > 0xd080-0xd087,
> > > > > > > > > > > 0xd000-0xd003,
> > > > > > > > > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device
> > > > > > > > > > > 31.2 on
> > > > > > > > > > > pci0
> > > > > > > > > > > ata2:  at channel 0 on atapci1
> > > > > > > > > > > ata3:  at channel 1 on atapci1
> > > > > > > > > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > > > > > > > > ada0:  ATA-7 SATA 2.x device
> > > > > > > > > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > > > > > > > > ada1:  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
> > > > > > > > > > 
> > > > > > > > > > I'm not entirely sure what is causing the problem with your
> > > > > > > > > > system,
> > > > > > > > > > but
> > > > > > > > > > hopefully we can narrow it down a bit.
> > > > > > > > > > 
> > > > > > > > > > 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.
> > > > > > > > > > 
> > > > > > > > > > Can you try out this patch:
> > > > > > > > > > 
> > > > > > > > > > https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1
> > > > > > > > > > .txt
> > > > > > > > > > 
> > > > > > > > > > In /boot/loader.conf, put the following:
> > > > > > > > > > 
> > > > > > > > > > kern.cam.ada.0.quirks="0x04"
> > > > > > > > > > kern.cam.ada.1.quirks="0x04"
> > > > > > > > > > 
> > > > > > > > > > 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.
> > > > > > > > > > 
> > > > > > > > > > What I'm trying to figure out here is where the problem
> > > > > > > > > > lies:
> > > > > > > > > > 
> > > > > > > > > > 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.
> > > > > > > > > > 
> > > > > > > > > > So, if you can try the patch and try to eliminate a few
> > > > > > > > > > possibilities,
> > > > > > > > > > we
> > > > > > > > > > may be able to narrow it down.
> > > > > > > > >  
> > > > > > > > >  I 

Re: ATA? related trouble with r300299

[Oleg V. Nauman]

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 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.

 I have performed device entries name transition when compatibility shims were 
removed in CURRENT.

 Thank you.


> 
> 
> On 23/05/2016, 21:25 "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: SATA reset: ports status=0x05
> > ata2: reset tp1 mask=03 ostat0=50 ostat1=50
> > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > messages logged to console.
> > 
> > Below is the relevant portion of ATA controller/devices probed/attached
> > during the boot:
> > 
> > atapci0:  port
> > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0
> > ata0:  at channel 0 on atapci0
> > atapci1:  port 0xd080-0xd087,
> > 0xd000-0xd003,
> > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on pci0
> > ata2:  at channel 0 on atapci1
> > ata3:  at channel 1 on atapci1
> > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > ada0:  ATA-7 SATA 2.x device
> > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > ada1:  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
> 
> I'm not entirely sure what is causing the problem with your system, but
> hopefully we can narrow it down a bit.
> 
> 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.
> 
> Can you try out this patch:
> 
> https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt
> 
> In /boot/loader.conf, put the following:
> 
> kern.cam.ada.0.quirks="0x04"
> kern.cam.ada.1.quirks="0x04"
> 
> 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.
> 
> What I'm trying to figure out here is where the problem lies:
> 
> 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.
> 
> So, if you can try the patch and try to eliminate a few possibilities, we
> may be able to narrow it down.
> 
> Thanks,
> 
> Ken
> --
> Kenneth Merry
> k...@freebsd.org
> ___
> 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"

___
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"

Re: ATA? related trouble with r300299

[Oleg V. Nauman]

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:
> > > > > 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 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=50
> > > > > > > > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > > > > > > > messages logged to console.
> > > > > > > > > > 
> > > > > > > > > > Below is the relevant portion of ATA controller/devices
> > > > > > > > > > probed/attached
> > > > > > > > > > during the boot:
> > > > > > > > > > 
> > > > > > > > > > atapci0:  port
> > > > > > > > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at
> > > > > > > > > > device
> > > > > > > > > > 31.1
> > > > > > > > > > on
> > > > > > > > > > pci0
> > > > > > > > > > ata0:  at channel 0 on atapci0
> > > > > > > > > > atapci1:  port
> > > > > > > > > > 0xd080-0xd087,
> > > > > > > > > > 0xd000-0xd003,
> > > > > > > > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device
> > > > > > > > > > 31.2 on
> > > > > > > > > > pci0
> > > > > > > > > > ata2:  at channel 0 on atapci1
> > > > > > > > > > ata3:  at channel 1 on atapci1
> > > > > > > > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > > > > > > > ada0:  ATA-7 SATA 2.x device
> > > > > > > > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > > > > > > > ada1:  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
> > > > > > > > > 
> > > > > > > > > I'm not entirely sure what is causing the problem with your
> > > > > > > > > system,
> > > > > > > > > but
> > > > > > > > > hopefully we can narrow it down a bit.
> > > > > > > > > 
> > > > > > > > > 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.
> > > > > > > > > 
> > > > > > > > > Can you try out this patch:
> > > > > > > > > 
> > > > > > > > > https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1
> > > > > > > > > .txt
> > > > > > > > > 
> > > > > > > > > In /boot/loader.conf, put the following:
> > > > > > > > > 
> > > > > > > > > kern.cam.ada.0.quirks="0x04"
> > > > > > > > > kern.cam.ada.1.quirks="0x04"
> > > > > > > > > 
> > > > > > > > > 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.
> > > > > > > > > 
> > > > > > > > > What I'm trying to figure out here is where the problem
> > > > > > > > > lies:
> > > > > > > > > 
> > > > > > > > > 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.
> > > > > > > > > 
> > > > > > > > > So, if you can try the patch and try to eliminate a few
> > > > > > > > > possibilities,
> > > > > > > > > we
> > > > > > > > > may be able to narrow it down.
> > > > > > > >  
> > > > > > > >  I was able to boot after applying the patch ;
> > > > > > > > 
> > > > > > > > kern.cam.ada.0.quirks="0x04"
> > > > > > > > was the quirk in effect. It is quirk for my Samsung HD200HJ
> > > > > > > > KF100-06
> > > > > > > > hard
> > > > > > > > drive.
> > > > > > > 
> > > > > > > Okay. 

Re: Re: ATA? related trouble with r300299

[Olli Hauer]

___
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"

Re: ATA? related trouble with r300299

[Kenneth D. Merry]

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 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 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=50
> > > > > > > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > > > > > > messages logged to console.
> > > > > > > > > 
> > > > > > > > > Below is the relevant portion of ATA controller/devices
> > > > > > > > > probed/attached
> > > > > > > > > during the boot:
> > > > > > > > > 
> > > > > > > > > atapci0:  port
> > > > > > > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device
> > > > > > > > > 31.1
> > > > > > > > > on
> > > > > > > > > pci0
> > > > > > > > > ata0:  at channel 0 on atapci0
> > > > > > > > > atapci1:  port 0xd080-0xd087,
> > > > > > > > > 0xd000-0xd003,
> > > > > > > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device
> > > > > > > > > 31.2 on
> > > > > > > > > pci0
> > > > > > > > > ata2:  at channel 0 on atapci1
> > > > > > > > > ata3:  at channel 1 on atapci1
> > > > > > > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > > > > > > ada0:  ATA-7 SATA 2.x device
> > > > > > > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > > > > > > ada1:  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
> > > > > > > > 
> > > > > > > > I'm not entirely sure what is causing the problem with your
> > > > > > > > system,
> > > > > > > > but
> > > > > > > > hopefully we can narrow it down a bit.
> > > > > > > > 
> > > > > > > > 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.
> > > > > > > > 
> > > > > > > > Can you try out this patch:
> > > > > > > > 
> > > > > > > > https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt
> > > > > > > > 
> > > > > > > > In /boot/loader.conf, put the following:
> > > > > > > > 
> > > > > > > > kern.cam.ada.0.quirks="0x04"
> > > > > > > > kern.cam.ada.1.quirks="0x04"
> > > > > > > > 
> > > > > > > > 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.
> > > > > > > > 
> > > > > > > > What I'm trying to figure out here is where the problem lies:
> > > > > > > > 
> > > > > > > > 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.
> > > > > > > > 
> > > > > > > > So, if you can try the patch and try to eliminate a few
> > > > > > > > possibilities,
> > > > > > > > we
> > > > > > > > may be able to narrow it down.
> > > > > > >  
> > > > > > >  I was able to boot after applying the patch ;
> > > > > > > 
> > > > > > > kern.cam.ada.0.quirks="0x04"
> > > > > > > was the quirk in effect. It is quirk for my Samsung HD200HJ
> > > > > > > KF100-06
> > > > > > > hard
> > > > > > > drive.
> > > > > > 
> > > > > > Okay.  Just so we can narrow it down a little more, can you try
> > > > > > this:
> > > > > > 
> > > > > > First, let's try getting an ATA Log directory using the PIO version
> > > > > > of
> > > > > > the
> > > > > > command:
> > > > > > 
> > > > > > camcontrol cmd ada0 -v -a "2f 0 0 0 0 0 0 0 0 0 1 0" -i 512 - |hd
> > > > > > 
> > > > > > If that works (you should get hexdump output), try the DMA version
> > > > > > of
> > > > > > the
> > > > > 

Re: ATA? related trouble with r300299

[Oleg V. Nauman]

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 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 update to r300299
> > > > > > > > Verbose boot shows the endless cycle of
> > > > > > > > 
> > > > > > > > ata2: SATA reset: ports status=0x05
> > > > > > > > ata2: reset tp1 mask=03 ostat0=50 ostat1=50
> > > > > > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > > > > > messages logged to console.
> > > > > > > > 
> > > > > > > > Below is the relevant portion of ATA controller/devices
> > > > > > > > probed/attached
> > > > > > > > during the boot:
> > > > > > > > 
> > > > > > > > atapci0:  port
> > > > > > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device
> > > > > > > > 31.1
> > > > > > > > on
> > > > > > > > pci0
> > > > > > > > ata0:  at channel 0 on atapci0
> > > > > > > > atapci1:  port 0xd080-0xd087,
> > > > > > > > 0xd000-0xd003,
> > > > > > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device
> > > > > > > > 31.2 on
> > > > > > > > pci0
> > > > > > > > ata2:  at channel 0 on atapci1
> > > > > > > > ata3:  at channel 1 on atapci1
> > > > > > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > > > > > ada0:  ATA-7 SATA 2.x device
> > > > > > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > > > > > ada1:  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
> > > > > > > 
> > > > > > > I'm not entirely sure what is causing the problem with your
> > > > > > > system,
> > > > > > > but
> > > > > > > hopefully we can narrow it down a bit.
> > > > > > > 
> > > > > > > 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.
> > > > > > > 
> > > > > > > Can you try out this patch:
> > > > > > > 
> > > > > > > https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt
> > > > > > > 
> > > > > > > In /boot/loader.conf, put the following:
> > > > > > > 
> > > > > > > kern.cam.ada.0.quirks="0x04"
> > > > > > > kern.cam.ada.1.quirks="0x04"
> > > > > > > 
> > > > > > > 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.
> > > > > > > 
> > > > > > > What I'm trying to figure out here is where the problem lies:
> > > > > > > 
> > > > > > > 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.
> > > > > > > 
> > > > > > > So, if you can try the patch and try to eliminate a few
> > > > > > > possibilities,
> > > > > > > we
> > > > > > > may be able to narrow it down.
> > > > > >  
> > > > > >  I was able to boot after applying the patch ;
> > > > > > 
> > > > > > kern.cam.ada.0.quirks="0x04"
> > > > > > was the quirk in effect. It is quirk for my Samsung HD200HJ
> > > > > > KF100-06
> > > > > > hard
> > > > > > drive.
> > > > > 
> > > > > Okay.  Just so we can narrow it down a little more, can you try
> > > > > this:
> > > > > 
> > > > > First, let's try getting an ATA Log directory using the PIO version
> > > > > of
> > > > > the
> > > > > command:
> > > > > 
> > > > > camcontrol cmd ada0 -v -a "2f 0 0 0 0 0 0 0 0 0 1 0" -i 512 - |hd
> > > > > 
> > > > > If that works (you should get hexdump output), try the DMA version
> > > > > of
> > > > > the
> > > > > command:
> > > > > 
> > > > > camcontrol cmd ada0 -v -d -a "47 0 0 0 0 0 0 0 0 0 1 0" -i 512 - |hd
> > > > 
> > > > "Expecting a character pointer argument." error for both commands.
> > > 
> > > Did the double quotes make it onto the command line?  Both of those work
> > > for me...
> >  
> >  

Re: ATA? related trouble with r300299

[Kenneth D. Merry]

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 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 update to r300299
> > > > > > > Verbose boot shows the endless cycle of
> > > > > > > 
> > > > > > > ata2: SATA reset: ports status=0x05
> > > > > > > ata2: reset tp1 mask=03 ostat0=50 ostat1=50
> > > > > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > > > > messages logged to console.
> > > > > > > 
> > > > > > > Below is the relevant portion of ATA controller/devices
> > > > > > > probed/attached
> > > > > > > during the boot:
> > > > > > > 
> > > > > > > atapci0:  port
> > > > > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1
> > > > > > > on
> > > > > > > pci0
> > > > > > > ata0:  at channel 0 on atapci0
> > > > > > > atapci1:  port 0xd080-0xd087,
> > > > > > > 0xd000-0xd003,
> > > > > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on
> > > > > > > pci0
> > > > > > > ata2:  at channel 0 on atapci1
> > > > > > > ata3:  at channel 1 on atapci1
> > > > > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > > > > ada0:  ATA-7 SATA 2.x device
> > > > > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > > > > ada1:  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
> > > > > > 
> > > > > > I'm not entirely sure what is causing the problem with your system,
> > > > > > but
> > > > > > hopefully we can narrow it down a bit.
> > > > > > 
> > > > > > 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.
> > > > > > 
> > > > > > Can you try out this patch:
> > > > > > 
> > > > > > https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt
> > > > > > 
> > > > > > In /boot/loader.conf, put the following:
> > > > > > 
> > > > > > kern.cam.ada.0.quirks="0x04"
> > > > > > kern.cam.ada.1.quirks="0x04"
> > > > > > 
> > > > > > 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.
> > > > > > 
> > > > > > What I'm trying to figure out here is where the problem lies:
> > > > > > 
> > > > > > 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.
> > > > > > 
> > > > > > So, if you can try the patch and try to eliminate a few
> > > > > > possibilities,
> > > > > > we
> > > > > > may be able to narrow it down.
> > > > >  
> > > > >  I was able to boot after applying the patch ;
> > > > > 
> > > > > kern.cam.ada.0.quirks="0x04"
> > > > > was the quirk in effect. It is quirk for my Samsung HD200HJ KF100-06
> > > > > hard
> > > > > drive.
> > > > 
> > > > Okay.  Just so we can narrow it down a little more, can you try this:
> > > > 
> > > > First, let's try getting an ATA Log directory using the PIO version of
> > > > the
> > > > command:
> > > > 
> > > > camcontrol cmd ada0 -v -a "2f 0 0 0 0 0 0 0 0 0 1 0" -i 512 - |hd
> > > > 
> > > > If that works (you should get hexdump output), try the DMA version of
> > > > the
> > > > command:
> > > > 
> > > > camcontrol cmd ada0 -v -d -a "47 0 0 0 0 0 0 0 0 0 1 0" -i 512 - |hd
> > > 
> > > "Expecting a character pointer argument." error for both commands.
> > 
> > Did the double quotes make it onto the command line?  Both of those work
> > for me...
> 
>  Something went wrong from my side, sorry.
> Below is the output of commands:
> 
> root@desktop:~ # camcontrol cmd ada0 -v -a "2f 0 0 0 0 0 0 0 0 0 1 0" -i 512 
> - 
> |hd
> camcontrol: error sending command
> (pass1:ata2:0:0:0): READ_LOG_EXT. ACB: 2f 00 00 00 00 00 00 00 00 00 01 00
> (pass1:ata2:0:0:0): CAM status: ATA Status Error
> (pass1:ata2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
> (pass1:ata2:0:0:0): RES: 51 04 00 00 00 00 00 

Re: ATA? related trouble with r300299

[Oleg V. Nauman]

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. 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: SATA reset: ports status=0x05
> > > > > > ata2: reset tp1 mask=03 ostat0=50 ostat1=50
> > > > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > > > messages logged to console.
> > > > > > 
> > > > > > Below is the relevant portion of ATA controller/devices
> > > > > > probed/attached
> > > > > > during the boot:
> > > > > > 
> > > > > > atapci0:  port
> > > > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1
> > > > > > on
> > > > > > pci0
> > > > > > ata0:  at channel 0 on atapci0
> > > > > > atapci1:  port 0xd080-0xd087,
> > > > > > 0xd000-0xd003,
> > > > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on
> > > > > > pci0
> > > > > > ata2:  at channel 0 on atapci1
> > > > > > ata3:  at channel 1 on atapci1
> > > > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > > > ada0:  ATA-7 SATA 2.x device
> > > > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > > > ada1:  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
> > > > > 
> > > > > I'm not entirely sure what is causing the problem with your system,
> > > > > but
> > > > > hopefully we can narrow it down a bit.
> > > > > 
> > > > > 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.
> > > > > 
> > > > > Can you try out this patch:
> > > > > 
> > > > > https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt
> > > > > 
> > > > > In /boot/loader.conf, put the following:
> > > > > 
> > > > > kern.cam.ada.0.quirks="0x04"
> > > > > kern.cam.ada.1.quirks="0x04"
> > > > > 
> > > > > 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.
> > > > > 
> > > > > What I'm trying to figure out here is where the problem lies:
> > > > > 
> > > > > 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.
> > > > > 
> > > > > So, if you can try the patch and try to eliminate a few
> > > > > possibilities,
> > > > > we
> > > > > may be able to narrow it down.
> > > >  
> > > >  I was able to boot after applying the patch ;
> > > > 
> > > > kern.cam.ada.0.quirks="0x04"
> > > > was the quirk in effect. It is quirk for my Samsung HD200HJ KF100-06
> > > > hard
> > > > drive.
> > > 
> > > Okay.  Just so we can narrow it down a little more, can you try this:
> > > 
> > > First, let's try getting an ATA Log directory using the PIO version of
> > > the
> > > command:
> > > 
> > > camcontrol cmd ada0 -v -a "2f 0 0 0 0 0 0 0 0 0 1 0" -i 512 - |hd
> > > 
> > > If that works (you should get hexdump output), try the DMA version of
> > > the
> > > command:
> > > 
> > > camcontrol cmd ada0 -v -d -a "47 0 0 0 0 0 0 0 0 0 1 0" -i 512 - |hd
> > 
> > "Expecting a character pointer argument." error for both commands.
> 
> Did the double quotes make it onto the command line?  Both of those work
> for me...

 Something went wrong from my side, sorry.
Below is the output of commands:

root@desktop:~ # camcontrol cmd ada0 -v -a "2f 0 0 0 0 0 0 0 0 0 1 0" -i 512 - 
|hd
camcontrol: error sending command
(pass1:ata2:0:0:0): READ_LOG_EXT. ACB: 2f 00 00 00 00 00 00 00 00 00 01 00
(pass1:ata2:0:0:0): CAM status: ATA Status Error
(pass1:ata2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
(pass1:ata2:0:0:0): RES: 51 04 00 00 00 00 00 00 00 01 00
root@desktop:~ # camcontrol cmd ada0 -v -d -a "47 0 0 0 0 0 0 0 0 0 1 0" -i 
512 - |hd
camcontrol: error sending command
(pass1:ata2:0:0:0): READ_LOG_DMA_EXT. ACB: 47 00 00 00 00 00 00 00 00 00 01 00
(pass1:ata2:0:0:0): CAM status: ATA Status Error
(pass1:ata2:0:0:0): ATA status: 51 (DRDY SERV ERR), 

Re: ATA? related trouble with r300299

[Kenneth D. Merry]

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 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=50
> > > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > > messages logged to console.
> > > > > 
> > > > > Below is the relevant portion of ATA controller/devices
> > > > > probed/attached
> > > > > during the boot:
> > > > > 
> > > > > atapci0:  port
> > > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on
> > > > > pci0
> > > > > ata0:  at channel 0 on atapci0
> > > > > atapci1:  port 0xd080-0xd087,
> > > > > 0xd000-0xd003,
> > > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on
> > > > > pci0
> > > > > ata2:  at channel 0 on atapci1
> > > > > ata3:  at channel 1 on atapci1
> > > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > > ada0:  ATA-7 SATA 2.x device
> > > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > > ada1:  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
> > > > 
> > > > I'm not entirely sure what is causing the problem with your system, but
> > > > hopefully we can narrow it down a bit.
> > > > 
> > > > 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.
> > > > 
> > > > Can you try out this patch:
> > > > 
> > > > https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt
> > > > 
> > > > In /boot/loader.conf, put the following:
> > > > 
> > > > kern.cam.ada.0.quirks="0x04"
> > > > kern.cam.ada.1.quirks="0x04"
> > > > 
> > > > 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.
> > > > 
> > > > What I'm trying to figure out here is where the problem lies:
> > > > 
> > > > 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.
> > > > 
> > > > So, if you can try the patch and try to eliminate a few possibilities,
> > > > we
> > > > may be able to narrow it down.
> > >  
> > >  I was able to boot after applying the patch ;
> > > 
> > > kern.cam.ada.0.quirks="0x04"
> > > was the quirk in effect. It is quirk for my Samsung HD200HJ KF100-06 hard
> > > drive.
> > 
> > Okay.  Just so we can narrow it down a little more, can you try this:
> > 
> > First, let's try getting an ATA Log directory using the PIO version of the
> > command:
> > 
> > camcontrol cmd ada0 -v -a "2f 0 0 0 0 0 0 0 0 0 1 0" -i 512 - |hd
> > 
> > If that works (you should get hexdump output), try the DMA version of the
> > command:
> > 
> > camcontrol cmd ada0 -v -d -a "47 0 0 0 0 0 0 0 0 0 1 0" -i 512 - |hd
> 
> "Expecting a character pointer argument." error for both commands.

Did the double quotes make it onto the command line?  Both of those work
for me...

Ken
-- 
Kenneth Merry
k...@freebsd.org
___
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"

Re: ATA? related trouble with r300299

[Oleg V. Nauman]

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 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=50
> > > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > > messages logged to console.
> > > > 
> > > > Below is the relevant portion of ATA controller/devices
> > > > probed/attached
> > > > during the boot:
> > > > 
> > > > atapci0:  port
> > > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on
> > > > pci0
> > > > ata0:  at channel 0 on atapci0
> > > > atapci1:  port 0xd080-0xd087,
> > > > 0xd000-0xd003,
> > > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on
> > > > pci0
> > > > ata2:  at channel 0 on atapci1
> > > > ata3:  at channel 1 on atapci1
> > > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > > ada0:  ATA-7 SATA 2.x device
> > > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > > ada1:  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
> > > 
> > > I'm not entirely sure what is causing the problem with your system, but
> > > hopefully we can narrow it down a bit.
> > > 
> > > 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.
> > > 
> > > Can you try out this patch:
> > > 
> > > https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt
> > > 
> > > In /boot/loader.conf, put the following:
> > > 
> > > kern.cam.ada.0.quirks="0x04"
> > > kern.cam.ada.1.quirks="0x04"
> > > 
> > > 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.
> > > 
> > > What I'm trying to figure out here is where the problem lies:
> > > 
> > > 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.
> > > 
> > > So, if you can try the patch and try to eliminate a few possibilities,
> > > we
> > > may be able to narrow it down.
> >  
> >  I was able to boot after applying the patch ;
> > 
> > kern.cam.ada.0.quirks="0x04"
> > was the quirk in effect. It is quirk for my Samsung HD200HJ KF100-06 hard
> > drive.
> 
> Okay.  Just so we can narrow it down a little more, can you try this:
> 
> First, let's try getting an ATA Log directory using the PIO version of the
> command:
> 
> camcontrol cmd ada0 -v -a "2f 0 0 0 0 0 0 0 0 0 1 0" -i 512 - |hd
> 
> If that works (you should get hexdump output), try the DMA version of the
> command:
> 
> camcontrol cmd ada0 -v -d -a "47 0 0 0 0 0 0 0 0 0 1 0" -i 512 - |hd

"Expecting a character pointer argument." error for both commands.


> 
> My hope is that we can confirm whether or not this is what is causing the
> Samsung drive to have issues.  It is certainly possible to put in a quirk,
> but I'd rather not make it unnecessarily broad.
> 
> Thanks,
> 
> Ken

___
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"

Re: ATA? related trouble with r300299

[Kenneth D. Merry]

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 update to r300299
> > > Verbose boot shows the endless cycle of
> > > 
> > > ata2: SATA reset: ports status=0x05
> > > ata2: reset tp1 mask=03 ostat0=50 ostat1=50
> > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > > messages logged to console.
> > > 
> > > Below is the relevant portion of ATA controller/devices probed/attached
> > > during the boot:
> > > 
> > > atapci0:  port
> > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0
> > > ata0:  at channel 0 on atapci0
> > > atapci1:  port 0xd080-0xd087,
> > > 0xd000-0xd003,
> > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on pci0
> > > ata2:  at channel 0 on atapci1
> > > ata3:  at channel 1 on atapci1
> > > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > > ada0:  ATA-7 SATA 2.x device
> > > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > > ada1:  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
> > 
> > I'm not entirely sure what is causing the problem with your system, but
> > hopefully we can narrow it down a bit.
> > 
> > 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.
> > 
> > Can you try out this patch:
> > 
> > https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt
> > 
> > In /boot/loader.conf, put the following:
> > 
> > kern.cam.ada.0.quirks="0x04"
> > kern.cam.ada.1.quirks="0x04"
> > 
> > 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.
> > 
> > What I'm trying to figure out here is where the problem lies:
> > 
> > 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.
> > 
> > So, if you can try the patch and try to eliminate a few possibilities, we
> > may be able to narrow it down.
> 
>  I was able to boot after applying the patch ;
> kern.cam.ada.0.quirks="0x04"
> was the quirk in effect. It is quirk for my Samsung HD200HJ KF100-06 hard 
> drive.

Okay.  Just so we can narrow it down a little more, can you try this:

First, let's try getting an ATA Log directory using the PIO version of the
command:

camcontrol cmd ada0 -v -a "2f 0 0 0 0 0 0 0 0 0 1 0" -i 512 - |hd

If that works (you should get hexdump output), try the DMA version of the
command:

camcontrol cmd ada0 -v -d -a "47 0 0 0 0 0 0 0 0 0 1 0" -i 512 - |hd

My hope is that we can confirm whether or not this is what is causing the
Samsung drive to have issues.  It is certainly possible to put in a quirk,
but I'd rather not make it unnecessarily broad.

Thanks,

Ken
-- 
Kenneth Merry
k...@freebsd.org
___
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"

Re: ATA? related trouble with r300299

[Oleg V. Nauman]

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: SATA reset: ports status=0x05
> > ata2: reset tp1 mask=03 ostat0=50 ostat1=50
> > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> > ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> > messages logged to console.
> > 
> > Below is the relevant portion of ATA controller/devices probed/attached
> > during the boot:
> > 
> > atapci0:  port
> > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0
> > ata0:  at channel 0 on atapci0
> > atapci1:  port 0xd080-0xd087,
> > 0xd000-0xd003,
> > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on pci0
> > ata2:  at channel 0 on atapci1
> > ata3:  at channel 1 on atapci1
> > ada0 at ata2 bus 0 scbus1 target 0 lun 0
> > ada0:  ATA-7 SATA 2.x device
> > ada1 at ata2 bus 0 scbus1 target 1 lun 0
> > ada1:  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
> 
> I'm not entirely sure what is causing the problem with your system, but
> hopefully we can narrow it down a bit.
> 
> 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.
> 
> Can you try out this patch:
> 
> https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt
> 
> In /boot/loader.conf, put the following:
> 
> kern.cam.ada.0.quirks="0x04"
> kern.cam.ada.1.quirks="0x04"
> 
> 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.
> 
> What I'm trying to figure out here is where the problem lies:
> 
> 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.
> 
> So, if you can try the patch and try to eliminate a few possibilities, we
> may be able to narrow it down.

 I was able to boot after applying the patch ;
kern.cam.ada.0.quirks="0x04"
was the quirk in effect. It is quirk for my Samsung HD200HJ KF100-06 hard 
drive.

> 
> Thanks,

 Thanks to you.

> 
> Ken

___
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"

Re: ATA? related trouble with r300299

[Kenneth D. Merry]

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=50
> ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
> ata2: reset tp2 stat0=50 stat1=50 devices=0x3
> messages logged to console.
> 
> Below is the relevant portion of ATA controller/devices probed/attached 
> during 
> the boot:
> 
> atapci0:  port 
> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0
> ata0:  at channel 0 on atapci0
> atapci1:  port 0xd080-0xd087, 0xd000-0xd003, 
> 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on pci0
> ata2:  at channel 0 on atapci1
> ata3:  at channel 1 on atapci1
> ada0 at ata2 bus 0 scbus1 target 0 lun 0
> ada0:  ATA-7 SATA 2.x device
> ada1 at ata2 bus 0 scbus1 target 1 lun 0
> ada1:  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

I'm not entirely sure what is causing the problem with your system, but
hopefully we can narrow it down a bit.

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.

Can you try out this patch:

https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt

In /boot/loader.conf, put the following:

kern.cam.ada.0.quirks="0x04"
kern.cam.ada.1.quirks="0x04"

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.

What I'm trying to figure out here is where the problem lies:

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.

So, if you can try the patch and try to eliminate a few possibilities, we
may be able to narrow it down.

Thanks,

Ken
-- 
Kenneth Merry
k...@freebsd.org
___
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"

ATA? related trouble with r300299

[Oleg V. Nauman]

 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=50
ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00
ata2: reset tp2 stat0=50 stat1=50 devices=0x3
messages logged to console.

Below is the relevant portion of ATA controller/devices probed/attached during 
the boot:

atapci0:  port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0
ata0:  at channel 0 on atapci0
atapci1:  port 0xd080-0xd087, 0xd000-0xd003, 
0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on pci0
ata2:  at channel 0 on atapci1
ata3:  at channel 1 on atapci1
ada0 at ata2 bus 0 scbus1 target 0 lun 0
ada0:  ATA-7 SATA 2.x device
ada1 at ata2 bus 0 scbus1 target 1 lun 0
ada1:  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


Thank you
___
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"