Re: Date formatting with en_US locale

2016-06-18 Thread Hajimu UMEMOTO 
Hi,

> On Sat, 18 Jun 2016 18:25:51 -0500
> Eric van Gyzen  said:

vangyzen> On 06/18/16 04:10 AM, Hajimu UMEMOTO wrote:
> Does the attached patch fix your issue?
> Though there are many locales it should be fixed, I've included only
> en_US one, in this time.

vangyzen> Yes, it fixes my issue with en_US.  Thank you, Umemoto-san.

You are welcome.
I've just committed into HEAD.

Sincerely,

--
Hajimu UMEMOTO
u...@mahoroba.org  u...@freebsd.org
http://www.mahoroba.org/~ume/
___
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"

Jenkins build is back to normal : FreeBSD_HEAD_sparc64 #88

2016-06-18 Thread jenkins-admin 
See 

___
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: Date formatting with en_US locale

2016-06-18 Thread Eric van Gyzen 
On 06/18/16 04:10 AM, Hajimu UMEMOTO wrote:
> Does the attached patch fix your issue?
> Though there are many locales it should be fixed, I've included only
> en_US one, in this time.

Yes, it fixes my issue with en_US.  Thank you, Umemoto-san.

Eric
___
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: New FreeBSD snapshots available: head (20160617 r301975)

2016-06-18 Thread Glen Barber 
On Sat, Jun 18, 2016 at 02:02:50PM +, Glen Barber wrote:
> On Sat, Jun 18, 2016 at 10:12:07AM +0300, fidaj wrote:
> > === Installation ISOs ===
> > 
> > Installation images are available for:
> > 
> > o 11.0-ALPHA4 amd64 GENERIC
> > o 11.0-ALPHA4 i386 GENERIC
> > o 11.0-ALPHA4 powerpc GENERIC
> > o 11.0-ALPHA4 powerpc64 GENERIC64
> > o 11.0-ALPHA4 sparc64 GENERIC
> > o 11.0-ALPHA4 armv6 BANANAPI
> > o 11.0-ALPHA4 armv6 BEAGLEBONE
> > o 11.0-ALPHA4 armv6 CUBIEBOARD
> > o 11.0-ALPHA4 armv6 CUBIEBOARD2
> > o 11.0-ALPHA4 armv6 CUBOX-HUMMINGBOARD
> > o 11.0-ALPHA4 armv6 GUMSTIX
> > o 11.0-ALPHA4 armv6 RPI-B
> > o 11.0-ALPHA4 armv6 RPI2
> > o 11.0-ALPHA4 armv6 PANDABOARD
> > o 11.0-ALPHA4 armv6 WANDBOARD
> > o 11.0-ALPHA4 aarch64 GENERIC
> >  
> > Hello. 
> > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/11.0-ALPHA4/  not have 
> > manifest file. 
> > 
> 
> Huh.  Yep, this is a problem.
> 
> Thank you for the report.  I'll investigate what happened here.
> 

This doesn't make sense.  The MANIFEST exists on the build machine, and
should have been copied as result of the distribution to the mirrors.

I don't understand how it did not make it to the mirrors.

So I know, how did you discover this?

I *do* see the MANIFEST for amd64, so something very bizarre happened
here.

Glen



signature.asc
Description: PGP signature

Re: BBB (cpsw(4)) seems to be broken in the latest 11-current

2016-06-18 Thread Jim Thompson 
There are recent changes to enable the switch and two port MAC mode. 

These were lightly tested on BBB prior to being committed. 

-- Jim

> On Jun 18, 2016, at 11:49 AM, Maxim Sobolev  wrote:
> 
> Well, I am not sure either as I don't have any issue restarting it
> afterwards.
> 
> Yes, it seems to be happening fairly reliably here. :( Happened for me
> again, I left it running overnight. I am 99% positive it was not the case
> before kernel upgrade..
> 
> 07:11:52 CPSW watchdog cpswss0: watchdog timeout
> cpswss0: Unable to cleanly shutdown transmitter
> 
> 
>> On Sat, Jun 18, 2016 at 1:09 AM, Svatopluk Kraus  wrote:
>> 
>> On Sat, Jun 18, 2016 at 8:50 AM, Maxim Sobolev 
>> wrote:
>>> Updated my BBB to the latest -current, immediately got this while trying
>> to
>>> make world over ssh console:
>>> 
>>> 06:02:17 CPSW watchdog cpswss0: watchdog timeout
>>> cpswss0: Unable to cleanly shutdown transmitter
>> 
>> My BBB stucks in cpsw0 during boot rarely, and even soft reset (reset
>> button) does not help. Only hard reset (power-off) helps. I have never
>> had time to discover where a problem is. I'm not even sure if this is
>> related to your problem as I did not remember exact dmesg in my case.
>> 
>> Svata
>> 
>> 
>>> 
>>> Interface seems to be locked after that, no traffic comes in or out.
>>> 
>>> This is:
>>> 
>>> FreeBSD 11.0-ALPHA3 #1 ba7edef(tps65217x)-dirty: Fri Jun 17 16:22:07 PDT
>>> 2016, svn revision 301898
>>> 
>>> The previous version that was rock-solid was:
>>> 
>>> FreeBSD 11.0-CURRENT #0 9d390ee(tps65217x)-dirty: Mon Jul  6 19:31:30 PDT
>>> 2015, svn revision 284878
>>> 
>>> I've been running buildworlds for literally days on that board, because
>>> it's how long it takes to build on that hardware. :)
>>> 
>>> I'll run it again and see if the issue re-appears.
>>> 
>>> If anyone seen this or if it's known issue please let me know.
>>> 
>>> Thanks!
>>> 
>>> -Max
>>> ___
>>> freebsd-...@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
>>> To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org"
> ___
> freebsd-...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-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: problem with USB disks on ALPHA3 w/ recent AMD chipset

2016-06-18 Thread Hans Petter Selasky 

On 06/18/16 21:12, Johannes Dieterich wrote:

On Sat, Jun 18, 2016 at 3:07 PM, Hans Petter Selasky  wrote:

On 06/18/16 04:15, Johannes Dieterich wrote:


Dear list,

I observe the following when I try to write to any USB drive:

Jun 17 22:02:35 manray kernel: (probe0:umass-sim0:0:0:0): INQUIRY.
CDB: 12 00 00 00 24 00
Jun 17 22:02:35 manray kernel: (probe0:umass-sim0:0:0:0): CAM status:
CCB request completed with an error
Jun 17 22:02:35 manray kernel: (probe0:umass-sim0:0:0:0): Retrying command
Jun 17 22:02:36 manray kernel: da0 at umass-sim0 bus 0 scbus2 target 0 lun
0
Jun 17 22:02:36 manray kernel: da0: 
Removable Direct Access SPC-4 SCSI device
Jun 17 22:02:36 manray kernel: da0: Serial Number 4C530001090427108375
Jun 17 22:02:36 manray kernel: da0: 40.000MB/s transfers
Jun 17 22:02:36 manray kernel: da0: 15264MB (31260672 512 byte sectors)
Jun 17 22:02:36 manray kernel: da0: quirks=0x2
Jun 17 22:04:21 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
2a 00 00 00 00 00 00 00 80 00
Jun 17 22:04:21 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
request completed with an error
Jun 17 22:04:21 manray kernel: (da0:umass-sim0:0:0:0): Retrying command
Jun 17 22:04:27 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
2a 00 00 00 00 00 00 00 80 00
Jun 17 22:04:27 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
request completed with an error
Jun 17 22:04:27 manray kernel: (da0:umass-sim0:0:0:0): Retrying command
Jun 17 22:04:32 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
2a 00 00 00 00 00 00 00 80 00
Jun 17 22:04:32 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
request completed with an error
Jun 17 22:04:32 manray kernel: (da0:umass-sim0:0:0:0): Retrying command
Jun 17 22:04:38 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
2a 00 00 00 00 00 00 00 80 00
Jun 17 22:04:38 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
request completed with an error
Jun 17 22:04:38 manray kernel: (da0:umass-sim0:0:0:0): Retrying command
Jun 17 22:04:43 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
2a 00 00 00 00 00 00 00 80 00
Jun 17 22:04:43 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
request completed with an error
Jun 17 22:04:43 manray kernel: (da0:umass-sim0:0:0:0): Error 5,
Retries exhausted
Jun 17 22:05:11 manray kernel: (da0:umass-sim0:0:0:0): got CAM status 0x44
Jun 17 22:05:11 manray kernel: (da0:umass-sim0:0:0:0): fatal error,
failed to attach to device
Jun 17 22:05:11 manray kernel: da0 at umass-sim0 bus 0 scbus2 target 0 lun
0
Jun 17 22:05:11 manray kernel: da0:  s/n
4C530001090427108375 detached
Jun 17 22:05:17 manray kernel: (da0:umass-sim0:0:0:0): Periph destroyed

I.e., when I dd, the dd exists prematurely with an error.

pciconf:

hostb0@pci0:0:0:0: class=0x06 card=0x15761022 chip=0x15761022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = HOST-PCI
none0@pci0:0:0:2: class=0x080600 card=0x15771022 chip=0x15771022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = base peripheral
subclass = IOMMU
vgapci0@pci0:0:1:0: class=0x03 card=0x807e103c chip=0x98741002
rev=0xc4 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]'
device = 'Carrizo'
class = display
subclass = VGA
hdac0@pci0:0:1:1: class=0x040300 card=0x807e103c chip=0x98401002
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]'
device = 'Kabini HDMI/DP Audio'
class = multimedia
subclass = HDA
hostb1@pci0:0:2:0: class=0x06 card=0x chip=0x157b1022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = HOST-PCI
pcib1@pci0:0:2:1: class=0x060400 card=0x12341022 chip=0x157c1022
rev=0x00 hdr=0x01
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = PCI-PCI
pcib2@pci0:0:2:3: class=0x060400 card=0x12341022 chip=0x157c1022
rev=0x00 hdr=0x01
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = PCI-PCI
pcib3@pci0:0:2:5: class=0x060400 card=0x12341022 chip=0x157c1022
rev=0x00 hdr=0x01
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = PCI-PCI
hostb2@pci0:0:3:0: class=0x06 card=0x chip=0x157b1022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = HOST-PCI
none1@pci0:0:8:0: class=0x108000 card=0x15781022 chip=0x15781022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = encrypt/decrypt
hostb3@pci0:0:9:0: class=0x06 card=0x chip=0x157d1022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = HOST-PCI
hdac1@pci0:0:9:2: class=0x040300 card=0x807e103c chip=0x157a1022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = multimedia
subclass = HDA
xhci0@pci0:0:16:0: class=0x0c0330 card=0x807e103c chip=0x79141022
rev=0x20 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'FCH USB XHCI Controller'
class = serial bus
subclass = USB

Re: BBB (cpsw(4)) seems to be broken in the latest 11-current

2016-06-18 Thread Maxim Sobolev 
Jim,

Yes, I've seen those. There were just handful of revision into the driver
between my old good kernel and now, most of them are from you guys:

r299477 | gonzo | 2016-05-11 11:20:02 -0700 (ср, 11 май 2016) | 16 lines
r298352 | pfg | 2016-04-20 08:45:55 -0700 (ср, 20 апр 2016) | 6 lines
r297132 | loos | 2016-03-20 20:16:56 -0700 (вс, 20 мар 2016) | 5 lines
r297043 | loos | 2016-03-18 13:24:31 -0700 (пт, 18 мар 2016) | 4 lines
r297042 | loos | 2016-03-18 13:09:54 -0700 (пт, 18 мар 2016) | 4 lines
r297041 | loos | 2016-03-18 13:04:34 -0700 (пт, 18 мар 2016) | 4 lines
r296993 | loos | 2016-03-17 12:35:08 -0700 (чт, 17 мар 2016) | 24 lines
r296980 | loos | 2016-03-16 23:23:48 -0700 (ср, 16 мар 2016) | 6 lines
r283287 | andrew | 2015-05-22 07:25:23 -0700 (пт, 22 май 2015) | 4 lines
(last known good one)

I've reverted the driver to the state all way down to r283287, while
keeping the rest of the kernel intact and soon will see if it works better.
If that works fine, I'll try to bi-sect it to a single troublesome revision.

-Max

On Sat, Jun 18, 2016 at 12:26 PM, Jim Thompson  wrote:

> There are recent changes to enable the switch and two port MAC mode.
>
> These were lightly tested on BBB prior to being committed.
>
> -- Jim
>
> > On Jun 18, 2016, at 11:49 AM, Maxim Sobolev  wrote:
> >
> > Well, I am not sure either as I don't have any issue restarting it
> > afterwards.
> >
> > Yes, it seems to be happening fairly reliably here. :( Happened for me
> > again, I left it running overnight. I am 99% positive it was not the case
> > before kernel upgrade..
> >
> > 07:11:52 CPSW watchdog cpswss0: watchdog timeout
> > cpswss0: Unable to cleanly shutdown transmitter
> >
> >
> >> On Sat, Jun 18, 2016 at 1:09 AM, Svatopluk Kraus 
> wrote:
> >>
> >> On Sat, Jun 18, 2016 at 8:50 AM, Maxim Sobolev 
> >> wrote:
> >>> Updated my BBB to the latest -current, immediately got this while
> trying
> >> to
> >>> make world over ssh console:
> >>>
> >>> 06:02:17 CPSW watchdog cpswss0: watchdog timeout
> >>> cpswss0: Unable to cleanly shutdown transmitter
> >>
> >> My BBB stucks in cpsw0 during boot rarely, and even soft reset (reset
> >> button) does not help. Only hard reset (power-off) helps. I have never
> >> had time to discover where a problem is. I'm not even sure if this is
> >> related to your problem as I did not remember exact dmesg in my case.
> >>
> >> Svata
> >>
> >>
> >>>
> >>> Interface seems to be locked after that, no traffic comes in or out.
> >>>
> >>> This is:
> >>>
> >>> FreeBSD 11.0-ALPHA3 #1 ba7edef(tps65217x)-dirty: Fri Jun 17 16:22:07
> PDT
> >>> 2016, svn revision 301898
> >>>
> >>> The previous version that was rock-solid was:
> >>>
> >>> FreeBSD 11.0-CURRENT #0 9d390ee(tps65217x)-dirty: Mon Jul  6 19:31:30
> PDT
> >>> 2015, svn revision 284878
> >>>
> >>> I've been running buildworlds for literally days on that board, because
> >>> it's how long it takes to build on that hardware. :)
> >>>
> >>> I'll run it again and see if the issue re-appears.
> >>>
> >>> If anyone seen this or if it's known issue please let me know.
> >>>
> >>> Thanks!
> >>>
> >>> -Max
> >>> ___
> >>> freebsd-...@freebsd.org mailing list
> >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> >>> To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org"
> > ___
> > freebsd-...@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > To unsubscribe, send any mail to "freebsd-arm-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: problem with USB disks on ALPHA3 w/ recent AMD chipset

2016-06-18 Thread Johannes Dieterich 
On Sat, Jun 18, 2016 at 3:07 PM, Hans Petter Selasky  wrote:
> On 06/18/16 04:15, Johannes Dieterich wrote:
>>
>> Dear list,
>>
>> I observe the following when I try to write to any USB drive:
>>
>> Jun 17 22:02:35 manray kernel: (probe0:umass-sim0:0:0:0): INQUIRY.
>> CDB: 12 00 00 00 24 00
>> Jun 17 22:02:35 manray kernel: (probe0:umass-sim0:0:0:0): CAM status:
>> CCB request completed with an error
>> Jun 17 22:02:35 manray kernel: (probe0:umass-sim0:0:0:0): Retrying command
>> Jun 17 22:02:36 manray kernel: da0 at umass-sim0 bus 0 scbus2 target 0 lun
>> 0
>> Jun 17 22:02:36 manray kernel: da0: 
>> Removable Direct Access SPC-4 SCSI device
>> Jun 17 22:02:36 manray kernel: da0: Serial Number 4C530001090427108375
>> Jun 17 22:02:36 manray kernel: da0: 40.000MB/s transfers
>> Jun 17 22:02:36 manray kernel: da0: 15264MB (31260672 512 byte sectors)
>> Jun 17 22:02:36 manray kernel: da0: quirks=0x2
>> Jun 17 22:04:21 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
>> 2a 00 00 00 00 00 00 00 80 00
>> Jun 17 22:04:21 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
>> request completed with an error
>> Jun 17 22:04:21 manray kernel: (da0:umass-sim0:0:0:0): Retrying command
>> Jun 17 22:04:27 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
>> 2a 00 00 00 00 00 00 00 80 00
>> Jun 17 22:04:27 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
>> request completed with an error
>> Jun 17 22:04:27 manray kernel: (da0:umass-sim0:0:0:0): Retrying command
>> Jun 17 22:04:32 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
>> 2a 00 00 00 00 00 00 00 80 00
>> Jun 17 22:04:32 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
>> request completed with an error
>> Jun 17 22:04:32 manray kernel: (da0:umass-sim0:0:0:0): Retrying command
>> Jun 17 22:04:38 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
>> 2a 00 00 00 00 00 00 00 80 00
>> Jun 17 22:04:38 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
>> request completed with an error
>> Jun 17 22:04:38 manray kernel: (da0:umass-sim0:0:0:0): Retrying command
>> Jun 17 22:04:43 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
>> 2a 00 00 00 00 00 00 00 80 00
>> Jun 17 22:04:43 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
>> request completed with an error
>> Jun 17 22:04:43 manray kernel: (da0:umass-sim0:0:0:0): Error 5,
>> Retries exhausted
>> Jun 17 22:05:11 manray kernel: (da0:umass-sim0:0:0:0): got CAM status 0x44
>> Jun 17 22:05:11 manray kernel: (da0:umass-sim0:0:0:0): fatal error,
>> failed to attach to device
>> Jun 17 22:05:11 manray kernel: da0 at umass-sim0 bus 0 scbus2 target 0 lun
>> 0
>> Jun 17 22:05:11 manray kernel: da0:  s/n
>> 4C530001090427108375 detached
>> Jun 17 22:05:17 manray kernel: (da0:umass-sim0:0:0:0): Periph destroyed
>>
>> I.e., when I dd, the dd exists prematurely with an error.
>>
>> pciconf:
>>
>> hostb0@pci0:0:0:0: class=0x06 card=0x15761022 chip=0x15761022
>> rev=0x00 hdr=0x00
>> vendor = 'Advanced Micro Devices, Inc. [AMD]'
>> class = bridge
>> subclass = HOST-PCI
>> none0@pci0:0:0:2: class=0x080600 card=0x15771022 chip=0x15771022
>> rev=0x00 hdr=0x00
>> vendor = 'Advanced Micro Devices, Inc. [AMD]'
>> class = base peripheral
>> subclass = IOMMU
>> vgapci0@pci0:0:1:0: class=0x03 card=0x807e103c chip=0x98741002
>> rev=0xc4 hdr=0x00
>> vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]'
>> device = 'Carrizo'
>> class = display
>> subclass = VGA
>> hdac0@pci0:0:1:1: class=0x040300 card=0x807e103c chip=0x98401002
>> rev=0x00 hdr=0x00
>> vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]'
>> device = 'Kabini HDMI/DP Audio'
>> class = multimedia
>> subclass = HDA
>> hostb1@pci0:0:2:0: class=0x06 card=0x chip=0x157b1022
>> rev=0x00 hdr=0x00
>> vendor = 'Advanced Micro Devices, Inc. [AMD]'
>> class = bridge
>> subclass = HOST-PCI
>> pcib1@pci0:0:2:1: class=0x060400 card=0x12341022 chip=0x157c1022
>> rev=0x00 hdr=0x01
>> vendor = 'Advanced Micro Devices, Inc. [AMD]'
>> class = bridge
>> subclass = PCI-PCI
>> pcib2@pci0:0:2:3: class=0x060400 card=0x12341022 chip=0x157c1022
>> rev=0x00 hdr=0x01
>> vendor = 'Advanced Micro Devices, Inc. [AMD]'
>> class = bridge
>> subclass = PCI-PCI
>> pcib3@pci0:0:2:5: class=0x060400 card=0x12341022 chip=0x157c1022
>> rev=0x00 hdr=0x01
>> vendor = 'Advanced Micro Devices, Inc. [AMD]'
>> class = bridge
>> subclass = PCI-PCI
>> hostb2@pci0:0:3:0: class=0x06 card=0x chip=0x157b1022
>> rev=0x00 hdr=0x00
>> vendor = 'Advanced Micro Devices, Inc. [AMD]'
>> class = bridge
>> subclass = HOST-PCI
>> none1@pci0:0:8:0: class=0x108000 card=0x15781022 chip=0x15781022
>> rev=0x00 hdr=0x00
>> vendor = 'Advanced Micro Devices, Inc. [AMD]'
>> class = encrypt/decrypt
>> hostb3@pci0:0:9:0: class=0x06 card=0x chip=0x157d1022
>> rev=0x00 hdr=0x00
>> vendor = 'Advanced Micro Devices, Inc. [AMD]'
>> class = bridge
>> subclass = HOST-PCI
>> hdac1@pci0:0:9:2: class=0x040300 card=0x807e103c chip=0x157a1022
>> rev=0x00

Re: problem with USB disks on ALPHA3 w/ recent AMD chipset

2016-06-18 Thread Hans Petter Selasky 

On 06/18/16 04:15, Johannes Dieterich wrote:

Dear list,

I observe the following when I try to write to any USB drive:

Jun 17 22:02:35 manray kernel: (probe0:umass-sim0:0:0:0): INQUIRY.
CDB: 12 00 00 00 24 00
Jun 17 22:02:35 manray kernel: (probe0:umass-sim0:0:0:0): CAM status:
CCB request completed with an error
Jun 17 22:02:35 manray kernel: (probe0:umass-sim0:0:0:0): Retrying command
Jun 17 22:02:36 manray kernel: da0 at umass-sim0 bus 0 scbus2 target 0 lun 0
Jun 17 22:02:36 manray kernel: da0: 
Removable Direct Access SPC-4 SCSI device
Jun 17 22:02:36 manray kernel: da0: Serial Number 4C530001090427108375
Jun 17 22:02:36 manray kernel: da0: 40.000MB/s transfers
Jun 17 22:02:36 manray kernel: da0: 15264MB (31260672 512 byte sectors)
Jun 17 22:02:36 manray kernel: da0: quirks=0x2
Jun 17 22:04:21 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
2a 00 00 00 00 00 00 00 80 00
Jun 17 22:04:21 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
request completed with an error
Jun 17 22:04:21 manray kernel: (da0:umass-sim0:0:0:0): Retrying command
Jun 17 22:04:27 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
2a 00 00 00 00 00 00 00 80 00
Jun 17 22:04:27 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
request completed with an error
Jun 17 22:04:27 manray kernel: (da0:umass-sim0:0:0:0): Retrying command
Jun 17 22:04:32 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
2a 00 00 00 00 00 00 00 80 00
Jun 17 22:04:32 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
request completed with an error
Jun 17 22:04:32 manray kernel: (da0:umass-sim0:0:0:0): Retrying command
Jun 17 22:04:38 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
2a 00 00 00 00 00 00 00 80 00
Jun 17 22:04:38 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
request completed with an error
Jun 17 22:04:38 manray kernel: (da0:umass-sim0:0:0:0): Retrying command
Jun 17 22:04:43 manray kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB:
2a 00 00 00 00 00 00 00 80 00
Jun 17 22:04:43 manray kernel: (da0:umass-sim0:0:0:0): CAM status: CCB
request completed with an error
Jun 17 22:04:43 manray kernel: (da0:umass-sim0:0:0:0): Error 5,
Retries exhausted
Jun 17 22:05:11 manray kernel: (da0:umass-sim0:0:0:0): got CAM status 0x44
Jun 17 22:05:11 manray kernel: (da0:umass-sim0:0:0:0): fatal error,
failed to attach to device
Jun 17 22:05:11 manray kernel: da0 at umass-sim0 bus 0 scbus2 target 0 lun 0
Jun 17 22:05:11 manray kernel: da0:  s/n
4C530001090427108375 detached
Jun 17 22:05:17 manray kernel: (da0:umass-sim0:0:0:0): Periph destroyed

I.e., when I dd, the dd exists prematurely with an error.

pciconf:

hostb0@pci0:0:0:0: class=0x06 card=0x15761022 chip=0x15761022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = HOST-PCI
none0@pci0:0:0:2: class=0x080600 card=0x15771022 chip=0x15771022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = base peripheral
subclass = IOMMU
vgapci0@pci0:0:1:0: class=0x03 card=0x807e103c chip=0x98741002
rev=0xc4 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]'
device = 'Carrizo'
class = display
subclass = VGA
hdac0@pci0:0:1:1: class=0x040300 card=0x807e103c chip=0x98401002
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]'
device = 'Kabini HDMI/DP Audio'
class = multimedia
subclass = HDA
hostb1@pci0:0:2:0: class=0x06 card=0x chip=0x157b1022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = HOST-PCI
pcib1@pci0:0:2:1: class=0x060400 card=0x12341022 chip=0x157c1022
rev=0x00 hdr=0x01
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = PCI-PCI
pcib2@pci0:0:2:3: class=0x060400 card=0x12341022 chip=0x157c1022
rev=0x00 hdr=0x01
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = PCI-PCI
pcib3@pci0:0:2:5: class=0x060400 card=0x12341022 chip=0x157c1022
rev=0x00 hdr=0x01
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = PCI-PCI
hostb2@pci0:0:3:0: class=0x06 card=0x chip=0x157b1022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = HOST-PCI
none1@pci0:0:8:0: class=0x108000 card=0x15781022 chip=0x15781022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = encrypt/decrypt
hostb3@pci0:0:9:0: class=0x06 card=0x chip=0x157d1022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = bridge
subclass = HOST-PCI
hdac1@pci0:0:9:2: class=0x040300 card=0x807e103c chip=0x157a1022
rev=0x00 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
class = multimedia
subclass = HDA
xhci0@pci0:0:16:0: class=0x0c0330 card=0x807e103c chip=0x79141022
rev=0x20 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'FCH USB XHCI Controller'
class = serial bus
subclass = USB
ahci0@pci0:0:17:0: class=0x010601 card=0x807e103c chip=0x79011022
rev=0x49 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'

Re: BBB (cpsw(4)) seems to be broken in the latest 11-current

2016-06-18 Thread Maxim Sobolev 
Well, I am not sure either as I don't have any issue restarting it
afterwards.

Yes, it seems to be happening fairly reliably here. :( Happened for me
again, I left it running overnight. I am 99% positive it was not the case
before kernel upgrade..

07:11:52 CPSW watchdog cpswss0: watchdog timeout
cpswss0: Unable to cleanly shutdown transmitter


On Sat, Jun 18, 2016 at 1:09 AM, Svatopluk Kraus  wrote:

> On Sat, Jun 18, 2016 at 8:50 AM, Maxim Sobolev 
> wrote:
> > Updated my BBB to the latest -current, immediately got this while trying
> to
> > make world over ssh console:
> >
> > 06:02:17 CPSW watchdog cpswss0: watchdog timeout
> > cpswss0: Unable to cleanly shutdown transmitter
>
> My BBB stucks in cpsw0 during boot rarely, and even soft reset (reset
> button) does not help. Only hard reset (power-off) helps. I have never
> had time to discover where a problem is. I'm not even sure if this is
> related to your problem as I did not remember exact dmesg in my case.
>
> Svata
>
>
> >
> > Interface seems to be locked after that, no traffic comes in or out.
> >
> > This is:
> >
> > FreeBSD 11.0-ALPHA3 #1 ba7edef(tps65217x)-dirty: Fri Jun 17 16:22:07 PDT
> > 2016, svn revision 301898
> >
> > The previous version that was rock-solid was:
> >
> > FreeBSD 11.0-CURRENT #0 9d390ee(tps65217x)-dirty: Mon Jul  6 19:31:30 PDT
> > 2015, svn revision 284878
> >
> > I've been running buildworlds for literally days on that board, because
> > it's how long it takes to build on that hardware. :)
> >
> > I'll run it again and see if the issue re-appears.
> >
> > If anyone seen this or if it's known issue please let me know.
> >
> > Thanks!
> >
> > -Max
> > ___
> > freebsd-...@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > To unsubscribe, send any mail to "freebsd-arm-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: [CFT] ypldap testing against OpenLDAP and Microsoft Active Directory

2016-06-18 Thread Alan Somers 
On Thu, Jun 16, 2016 at 7:20 AM, Chris H  wrote:
> On Wed, 15 Jun 2016 08:03:55 -0400 Nikolai Lifanov 
> wrote
>
>> On 06/14/2016 21:05, Marcelo Araujo wrote:
>> > 2016-06-15 8:17 GMT+08:00 Chris H :
>> >
>> >> On Thu, 9 Jun 2016 17:55:58 +0800 Marcelo Araujo 
>> >> wrote
>> >>
>> >>> Hey,
>> >>>
>> >>> Thanks for the CFT Craig.
>> >>>
>> >>> 2016-06-09 14:41 GMT+08:00 Xin Li :
>> >>>
>> 
>> 
>>  On 6/8/16 23:10, Craig Rodrigues wrote:
>> > Hi,
>> >
>> > I have worked with Marcelo Araujo to port OpenBSD's ypldap to FreeBSD
>> > current.
>> >
>> > In latest current, it should be possible to put in /etc/rc.conf:
>> >
>> > nis_ypldap_enable="YES"
>> > to activate the ypldap daemon.
>> >
>> > When set up properly, it should be possible to log into FreeBSD, and
>> >> have
>> > the backend password database come from an LDAP database such
>> > as OpenLDAP
>> >
>> > There is some documentation for setting this up, but it is OpenBSD
>>  specific:
>> >
>> > http://obfuscurity.com/2009/08/OpenBSD-as-an-LDAP-Client
>> > http://puffysecurity.com/wiki/ypldap.html#2
>> >
>> > I did not bother porting the OpenBSD LDAP server to FreeBSD, so that
>> > information
>> > does not apply.  I figure that openldap from ports should work fine.
>> >
>> > I was wondering if there is someone out there familiar enough with
>> >> LDAP
>> > and has a setup they can test this stuff out with, provide feedback,
>> >> and
>> > help
>> > improve the documentation for FreeBSD?
>> 
>>  Looks like it would be a fun weekend project.  I've cc'ed a potential
>>  person who may be interested in this as well.
>> 
>>  But will this worth the effort? (I think the current implementation
>>  would do everything with plaintext protocol over wire, so while it
>>  extends life for legacy applications that are still using NIS/YP, it
>>  doesn't seem to be something that we should recommend end user to use?)
>> 
>> >>>
>> >>> I can see two good point to use ypldap that would be basically for users
>> >>> that needs to migrate from NIS to LDAP or need to make some integration
>> >>> between legacy(NIS) and LDAP during a transition period to LDAP.
>> >>>
>> >>> As mentioned, NIS is 'plain text' not safe by its nature, however there
>> >> are
>> >>> still lots of people out there using NIS, and ypldap(8) is a good tool to
>> >>> help these people migrate to a more safe tool like LDAP.
>> >>>
>> >>>
>> 
>> > I would also be interested in hearing from someone who can see if
>> > ypldap can work against a Microsoft Active Directory setup?
>> 
>>  Cheers,
>> 
>> 
>> >>> All my tests were using OpenLDAP, I used the OpenBSD documentation to
>> >> setup
>> >>> everything, and the file share/examples/ypldap/ypldap.conf can be a good
>> >>> start to anybody that wants to start to work with ypldap(8).
>> >>>
>> >>> Would be nice hear from other users how was their experience using ypldap
>> >>> with MS Active Directory and perhaps some HOWTO how they made all the
>> >> setup
>> >>> would be amazing to have.
>> >>>
>> >>> Also, would be useful to know who are still using NIS and what kind of
>> >>> setup(user case), maybe even the reason why they are still using it.
>> >>
>> >> Honestly, I think the best way to motivate people to do the right
>> >> thing(tm) Would be to remove Yellow Pages from the tree, entirely. :-)
>> >> It's been dead for *years*, and as you say, isn't safe, anyway..
>> >>
>> >
>> > Yes, I have a plan for that, but I don't believe it will happens before
>> > FreeBSD 12-RELEASE.
>> >
>>
>> Please don't, at least for now. NIS is fast, simple, reliable, and works
>> on first boot without additional software. I have passwords in
>> Kerberos, so the usual cons doesn't apply. This is very valuable to me.
>>
>> It's not hurting anyone. What's the motivation behind removing it?
>
> In all honesty, my comment was somewhat tongue-in-cheek. But from
> a purely maintenance POV, at this point in time. I think the Yellow
> Pages are better suited for the ports tree, than in $BASE.
>

It will be hard to wean people off of NIS as long as KGSSAPI is
disabled in GENERIC.  Does anybody know why it isn't enabled by
default?

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

Build failed in Jenkins: FreeBSD_HEAD_sparc64 #87

2016-06-18 Thread jenkins-admin 
See 

--
[...truncated 176799 lines...]
--- machine ---
machine -> /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/sparc64/include
--- opt_bus.h ---
ln -sf 
/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/GENERIC/opt_bus.h
 opt_bus.h
--- opt_usb.h ---
ln -sf 
/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/GENERIC/opt_usb.h
 opt_usb.h
--- opt_gdb.h ---
ln -sf 
/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/GENERIC/opt_gdb.h
 opt_gdb.h
--- device_if.h ---
awk -f /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/tools/makeobjops.awk 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/kern/device_if.m -h
--- bus_if.h ---
awk -f /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/tools/makeobjops.awk 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/kern/bus_if.m -h
--- all_subdir_usb/uled ---
--- uled.o ---
cc  -O2 -pipe  -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc   
-DHAVE_KERNEL_OPTION_HEADERS -include 
/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/GENERIC/opt_global.h
 -I. -I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys -fno-common -g 
-I/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/GENERIC
  -MD  -MF.depend.uled.o -MTuled.o -ffreestanding -fwrapv -fstack-protector 
-gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef 
-Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option  -Wno-unknown-pragmas  -Wno-uninitialized  
-finline-limit=15000 -fms-extensions --param inline-unit-growth=100 --param 
large-function-growth=1000 -mcmodel=medany -msoft-float  -std=iso9899:1999 -c 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/modules/usb/uled/../../../
 dev/usb/misc/uled.c -o uled.o
--- all_subdir_usb/ucom ---
--- usb_if.h ---
awk -f /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/tools/makeobjops.awk 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/dev/usb/usb_if.m -h
--- usbdevs.h ---
awk -f /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/tools/usbdevs2h.awk 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/dev/usb/usbdevs -h
--- all_subdir_zfs ---
--- opensolaris_uio.o ---
cc  -O2 -pipe -DFREEBSD_NAMECACHE -DBUILDING_ZFS  -fno-strict-aliasing -Werror 
-D_KERNEL -DKLD_MODULE -nostdinc  
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/compat/opensolaris 
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs
 
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common/zmod
 
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common
 -I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys 
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/common/zfs
 
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/common
 -DHAVE_KERNEL_OPTION_HEADERS -include 
/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/GENERIC/opt_global.h
 -I. -I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys -fno-common -g 
-I/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64
 /src/sys/GENERIC  -MD  -MF.depend.opensolaris_uio.o -MTopensolaris_uio.o 
-ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions  
-Wmissing-include-dirs -fdiagnostics-show-option  -Wno-unknown-pragmas  
-Wno-uninitialized -Wno-missing-prototypes -Wno-undef -Wno-strict-prototypes 
-Wno-cast-qual -Wno-parentheses -Wno-redundant-decls -Wno-missing-braces 
-Wno-uninitialized -Wno-unused -Wno-inline -Wno-switch -Wno-pointer-arith  
-finline-limit=15000 -fms-extensions --param inline-unit-growth=100 --param 
large-function-growth=1000 -mcmodel=medany -msoft-float  -std=iso9899:1999 
-include 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/compat/opensolaris/sys/debug_compat.h
 -c 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/compat/opensolaris/kern/opensolaris_uio.c
 -o opensolaris_uio.o
--- opensolaris_vfs.o ---
cc  -O2 -pipe -DFREEBSD_NAMECACHE -DBUILDING_ZFS  -fno-strict-aliasing -Werror 
-D_KERNEL -DKLD_MODULE -nostdinc  
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/compat/opensolaris 
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs
 
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common/zmod
 
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common

Re: New FreeBSD snapshots available: head (20160617 r301975)

2016-06-18 Thread Glen Barber 
On Sat, Jun 18, 2016 at 10:12:07AM +0300, fidaj wrote:
> === Installation ISOs ===
> 
> Installation images are available for:
> 
> o 11.0-ALPHA4 amd64 GENERIC
> o 11.0-ALPHA4 i386 GENERIC
> o 11.0-ALPHA4 powerpc GENERIC
> o 11.0-ALPHA4 powerpc64 GENERIC64
> o 11.0-ALPHA4 sparc64 GENERIC
> o 11.0-ALPHA4 armv6 BANANAPI
> o 11.0-ALPHA4 armv6 BEAGLEBONE
> o 11.0-ALPHA4 armv6 CUBIEBOARD
> o 11.0-ALPHA4 armv6 CUBIEBOARD2
> o 11.0-ALPHA4 armv6 CUBOX-HUMMINGBOARD
> o 11.0-ALPHA4 armv6 GUMSTIX
> o 11.0-ALPHA4 armv6 RPI-B
> o 11.0-ALPHA4 armv6 RPI2
> o 11.0-ALPHA4 armv6 PANDABOARD
> o 11.0-ALPHA4 armv6 WANDBOARD
> o 11.0-ALPHA4 aarch64 GENERIC
>  
> Hello. 
> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/11.0-ALPHA4/  not have 
> manifest file. 
> 

Huh.  Yep, this is a problem.

Thank you for the report.  I'll investigate what happened here.

Glen



signature.asc
Description: PGP signature

Re: Build failed in Jenkins: FreeBSD_HEAD_sparc64 #86

2016-06-18 Thread Bjoern A. Zeeb 



On 18 Jun 2016, at 13:29, Konstantin Belousov wrote:

On Sat, Jun 18, 2016 at 12:05:26PM +, jenkins-ad...@freebsd.org 
wrote:

cc1: warnings being treated as errors
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c: 
In function 'dnlc_reduce_cache':
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:3798: 
warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]

*** [arc.o] Error code 1


The fix is waiting for re approval.


In the past we handled build fixes with re (implicit) as there’s no 
point on leaving something broken.


Not sure how re@ thinks about it these days but I’d rather have a 
building tree than waiting for approval for as long as there was no 
announcement to hold off approved but not yet done commits due to repo 
work.


Just my 0.0005 cts

/bz
___
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: Build failed in Jenkins: FreeBSD_HEAD_sparc64 #86

2016-06-18 Thread Konstantin Belousov 
On Sat, Jun 18, 2016 at 12:05:26PM +, jenkins-ad...@freebsd.org wrote:
> cc1: warnings being treated as errors
> /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:
>  In function 'dnlc_reduce_cache':
> /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/arc.c:3798:
>  warning: cast from pointer to integer of different size 
> [-Wpointer-to-int-cast]
> *** [arc.o] Error code 1

The fix is waiting for re approval.
___
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: New FreeBSD snapshots available: head (20160617 r301975)

2016-06-18 Thread fidaj 
Please add the MANIFEST file to 
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/11.0-ALPHA4/ 

Thanks! 

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

Build failed in Jenkins: FreeBSD_HEAD_sparc64 #86

2016-06-18 Thread jenkins-admin 
See 

--
[...truncated 190406 lines...]
--- all_subdir_usb/rue ---
===> usb/rue (all)
--- machine ---
machine -> /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/sparc64/include
--- opt_bus.h ---
ln -sf 
/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/GENERIC/opt_bus.h
 opt_bus.h
--- opt_inet.h ---
ln -sf 
/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/GENERIC/opt_inet.h
 opt_inet.h
--- opt_usb.h ---
ln -sf 
/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/GENERIC/opt_usb.h
 opt_usb.h
--- bus_if.h ---
awk -f /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/tools/makeobjops.awk 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/kern/bus_if.m -h
--- device_if.h ---
awk -f /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/tools/makeobjops.awk 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/kern/device_if.m -h
--- miibus_if.h ---
awk -f /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/tools/makeobjops.awk 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/dev/mii/miibus_if.m -h
--- all_subdir_zfs ---
--- inftrees.o ---
cc  -O2 -pipe -DFREEBSD_NAMECACHE -DBUILDING_ZFS  -fno-strict-aliasing -Werror 
-D_KERNEL -DKLD_MODULE -nostdinc  
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/compat/opensolaris 
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs
 
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common/zmod
 
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common
 -I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys 
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/common/zfs
 
-I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/common
 -DHAVE_KERNEL_OPTION_HEADERS -include 
/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/GENERIC/opt_global.h
 -I. -I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys -fno-common -g 
-I/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64
 /src/sys/GENERIC  -MD  -MF.depend.inftrees.o -MTinftrees.o -ffreestanding 
-fwrapv -fstack-protector -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option  -Wno-unknown-pragmas  -Wno-uninitialized 
-Wno-missing-prototypes -Wno-undef -Wno-strict-prototypes -Wno-cast-qual 
-Wno-parentheses -Wno-redundant-decls -Wno-missing-braces -Wno-uninitialized 
-Wno-unused -Wno-inline -Wno-switch -Wno-pointer-arith  -finline-limit=15000 
-fms-extensions --param inline-unit-growth=100 --param 
large-function-growth=1000 -mcmodel=medany -msoft-float  -std=iso9899:1999 
-include 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/compat/opensolaris/sys/debug_compat.h
 -c 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/cddl/contrib/opensolaris/uts/common/zmod/inftrees.c
 -o inftrees.o
--- all_subdir_usb ---
--- miidevs.h ---
awk -f /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/tools/miidevs2h.awk 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/dev/mii/miidevs
--- usb_if.h ---
awk -f /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/tools/makeobjops.awk 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/dev/usb/usb_if.m -h
--- usbdevs.h ---
awk -f /builds/workspace/FreeBSD_HEAD_sparc64/src/sys/tools/usbdevs2h.awk 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/dev/usb/usbdevs -h
--- all_subdir_wlan ---
--- ieee80211_tdma.o ---
cc  -O2 -pipe  -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc   
-DHAVE_KERNEL_OPTION_HEADERS -include 
/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/GENERIC/opt_global.h
 -I. -I/builds/workspace/FreeBSD_HEAD_sparc64/src/sys -fno-common -g 
-I/builds/workspace/FreeBSD_HEAD_sparc64/obj/sparc64.sparc64/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/GENERIC
  -MD  -MF.depend.ieee80211_tdma.o -MTieee80211_tdma.o -ffreestanding -fwrapv 
-fstack-protector -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option  -Wno-unknown-pragmas  -Wno-uninitialized  
-finline-limit=15000 -fms-extensions --param inline-unit-growth=100 --param 
large-function-growth=1000 -mcmodel=medany -msoft-float  -std=iso9899:1999 -c 
/builds/workspace/FreeBSD_HEAD_sparc64/src/sys/module
 s/wlan/../../net80211/ieee80211_tdma.c -o ieee80211_tdma.o
--- all_subdir_usb ---
--- all_subdir_usb/smsc ---
===> usb/smsc (all)
--- all_subdir_zfs ---
--- trees.o ---
cc  -O2 -pipe

Re: Date formatting with en_US locale

2016-06-18 Thread Hajimu UMEMOTO 
Hi,

vangyzen> Above, I mentioned two issues.  The other one is, the date format for
vangyzen> en_US pads the month with a zero, but the day with a space.  So, June 
7 is:

vangyzen> 06/ 7/16

vangyzen> That looks weird.  It should pad both with zeros.  I'd be happy to fix
vangyzen> it, but I don't see how:  There isn't an "xformat" callback in the
vangyzen> cldr2def.pl script, and it's not clear how to add one.  If you can
vangyzen> explain, I'll do it.  If you can fix it, I'll be grateful.  ;)

Does the attached patch fix your issue?
Though there are many locales it should be fixed, I've included only
en_US one, in this time.

Sincerely,

Index: share/timedef/en_US.UTF-8.src
===
--- share/timedef/en_US.UTF-8.src	(revision 302002)
+++ share/timedef/en_US.UTF-8.src	(working copy)
@@ -53,7 +53,7 @@
 %I:%M:%S %p
 #
 # x_fmt
-%m/%e/%y
+%m/%d/%y
 #
 # c_fmt
 %A, %B %e, %Y at %I:%M:%S %p
@@ -80,7 +80,7 @@
 December
 #
 # md_order
-m
+md
 #
 # ampm_fmt
 %I:%M:%S %p
Index: tools/tools/locale/tools/cldr2def.pl
===
--- tools/tools/locale/tools/cldr2def.pl	(revision 302002)
+++ tools/tools/locale/tools/cldr2def.pl	(working copy)
@@ -68,6 +68,7 @@
 	mdorder => \_mdorder,
 	altmon => \_altmon,
 	cformat => \_cformat,
+	dformat => \_dformat,
 	dtformat => \_dtformat,
 	cbabmon => \_abmon,
 	cbampm => \_ampm,
@@ -183,10 +184,9 @@
 	"abday"		=> "as",
 	"day"		=> "as",
 	"t_fmt"		=> "s",
-	"d_fmt"		=> "s",
+	"d_fmt"		=> " " " "s",
 	"d_t_fmt"		=> " " "

Re: BBB (cpsw(4)) seems to be broken in the latest 11-current

2016-06-18 Thread Svatopluk Kraus 
On Sat, Jun 18, 2016 at 8:50 AM, Maxim Sobolev  wrote:
> Updated my BBB to the latest -current, immediately got this while trying to
> make world over ssh console:
>
> 06:02:17 CPSW watchdog cpswss0: watchdog timeout
> cpswss0: Unable to cleanly shutdown transmitter

My BBB stucks in cpsw0 during boot rarely, and even soft reset (reset
button) does not help. Only hard reset (power-off) helps. I have never
had time to discover where a problem is. I'm not even sure if this is
related to your problem as I did not remember exact dmesg in my case.

Svata


>
> Interface seems to be locked after that, no traffic comes in or out.
>
> This is:
>
> FreeBSD 11.0-ALPHA3 #1 ba7edef(tps65217x)-dirty: Fri Jun 17 16:22:07 PDT
> 2016, svn revision 301898
>
> The previous version that was rock-solid was:
>
> FreeBSD 11.0-CURRENT #0 9d390ee(tps65217x)-dirty: Mon Jul  6 19:31:30 PDT
> 2015, svn revision 284878
>
> I've been running buildworlds for literally days on that board, because
> it's how long it takes to build on that hardware. :)
>
> I'll run it again and see if the issue re-appears.
>
> If anyone seen this or if it's known issue please let me know.
>
> Thanks!
>
> -Max
> ___
> freebsd-...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-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: New FreeBSD snapshots available: head (20160617 r301975)

2016-06-18 Thread fidaj 


--- Оригінальне повідомлення --- 
Від кого: "Glen Barber"  
Дата: 18 червня 2016, 08:58:23 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

New FreeBSD development branch installation ISOs and virtual machine
disk images have been uploaded to the FTP mirrors.

As with any development branch, the installation snapshots are not
intended for use on production systems.  We do, however, encourage
testing on non-production systems as much as possible.

Please also consider installing the sysutils/panicmail port, which can
help in providing FreeBSD developers the necessary information regarding
system crashes.

Checksums for the installation ISOs and the VM disk images follow at
the end of this email.

=== Installation ISOs ===

Installation images are available for:

o 11.0-ALPHA4 amd64 GENERIC
o 11.0-ALPHA4 i386 GENERIC
o 11.0-ALPHA4 powerpc GENERIC
o 11.0-ALPHA4 powerpc64 GENERIC64
o 11.0-ALPHA4 sparc64 GENERIC
o 11.0-ALPHA4 armv6 BANANAPI
o 11.0-ALPHA4 armv6 BEAGLEBONE
o 11.0-ALPHA4 armv6 CUBIEBOARD
o 11.0-ALPHA4 armv6 CUBIEBOARD2
o 11.0-ALPHA4 armv6 CUBOX-HUMMINGBOARD
o 11.0-ALPHA4 armv6 GUMSTIX
o 11.0-ALPHA4 armv6 RPI-B
o 11.0-ALPHA4 armv6 RPI2
o 11.0-ALPHA4 armv6 PANDABOARD
o 11.0-ALPHA4 armv6 WANDBOARD
o 11.0-ALPHA4 aarch64 GENERIC
 
Hello. 
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/11.0-ALPHA4/  not have 
manifest file. 


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

BBB (cpsw(4)) seems to be broken in the latest 11-current

2016-06-18 Thread Maxim Sobolev 
Updated my BBB to the latest -current, immediately got this while trying to
make world over ssh console:

06:02:17 CPSW watchdog cpswss0: watchdog timeout
cpswss0: Unable to cleanly shutdown transmitter

Interface seems to be locked after that, no traffic comes in or out.

This is:

FreeBSD 11.0-ALPHA3 #1 ba7edef(tps65217x)-dirty: Fri Jun 17 16:22:07 PDT
2016, svn revision 301898

The previous version that was rock-solid was:

FreeBSD 11.0-CURRENT #0 9d390ee(tps65217x)-dirty: Mon Jul  6 19:31:30 PDT
2015, svn revision 284878

I've been running buildworlds for literally days on that board, because
it's how long it takes to build on that hardware. :)

I'll run it again and see if the issue re-appears.

If anyone seen this or if it's known issue please let me know.

Thanks!

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