Re: Intel NVMe troubles?

2016-09-13 Thread Borja Marcos 

> On 12 Sep 2016, at 17:23, Jim Harris  wrote:
> 
> There is an updated DCT 3.0.2 at:  https://downloadcenter.intel.
> com/download/26221/Intel-SSD-Data-Center-Tool which has a fix for this
> issue.
> 
> Borja has already downloaded this update and confirmed it looks good so
> far.  Posting the update and results here so it is archived on the STABLE
> mailing list.

Is it just my imagination or has trim performance improved dramatically? I’m 
being unable to replicate
the I/O stalls that I observed after running some simultaneous Bonnie++ 
benchmarks with large files.

Thanks,



Borja.


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problems with item delivery, n.00846960

2016-09-13 Thread Matthias Wolf 
How about you go fuck youself spammer-scum.


On Tue, 13 Sep 2016 00:12:14 -0600
"FedEx International MailService"
 wrote:

> Dear Customer,
> 
> Your parcel has arrived at September 10. Courier was unable to
> deliver the parcel to you. You can review complete details of your
> order in the find attached.
> 
> Sincerely,
> Perry Michael,
> Sr. Station Manager.
> 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to
> "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: X2APIC support

2016-09-13 Thread Andriy Gapon 
On 12/09/2016 20:53, Slawa Olhovchenkov wrote:
> boot_cpu_id = 255

I think that this points towards the BIOS not configuring the BSP LAPIC
correctly when you select that combination of BIOS options.
That's weird, but I fail to find any other explanation.

If wonder what would happen if you disable X2APIC_OPT_OUT and set
hw.x2apic_enable=0 in loader.conf or at the loader prompt.

-- 
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: X2APIC support

2016-09-13 Thread Slawa Olhovchenkov 
On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote:

> On 12/09/2016 20:53, Slawa Olhovchenkov wrote:
> > boot_cpu_id = 255
> 
> I think that this points towards the BIOS not configuring the BSP LAPIC
> correctly when you select that combination of BIOS options.
> That's weird, but I fail to find any other explanation.
> 
> If wonder what would happen if you disable X2APIC_OPT_OUT and set
> hw.x2apic_enable=0 in loader.conf or at the loader prompt.

Boot OK w/o hw.x2apic_enable=0, only with disable X2APIC_OPT_OUT.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: X2APIC support

2016-09-13 Thread Andriy Gapon 
On 13/09/2016 15:11, Slawa Olhovchenkov wrote:
> On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote:
> 
>> On 12/09/2016 20:53, Slawa Olhovchenkov wrote:
>>> boot_cpu_id = 255
>>
>> I think that this points towards the BIOS not configuring the BSP LAPIC
>> correctly when you select that combination of BIOS options.
>> That's weird, but I fail to find any other explanation.
>>
>> If wonder what would happen if you disable X2APIC_OPT_OUT and set
>> hw.x2apic_enable=0 in loader.conf or at the loader prompt.
> 
> Boot OK w/o hw.x2apic_enable=0, only with disable X2APIC_OPT_OUT.
> 

This doesn't answer my question and doesn't add any new information, correct?

-- 
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: X2APIC support

2016-09-13 Thread Slawa Olhovchenkov 
On Tue, Sep 13, 2016 at 03:38:17PM +0300, Andriy Gapon wrote:

> On 13/09/2016 15:11, Slawa Olhovchenkov wrote:
> > On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote:
> > 
> >> On 12/09/2016 20:53, Slawa Olhovchenkov wrote:
> >>> boot_cpu_id = 255
> >>
> >> I think that this points towards the BIOS not configuring the BSP LAPIC
> >> correctly when you select that combination of BIOS options.
> >> That's weird, but I fail to find any other explanation.
> >>
> >> If wonder what would happen if you disable X2APIC_OPT_OUT and set
> >> hw.x2apic_enable=0 in loader.conf or at the loader prompt.
> > 
> > Boot OK w/o hw.x2apic_enable=0, only with disable X2APIC_OPT_OUT.
> > 
> 
> This doesn't answer my question and doesn't add any new information, correct?

I am don't see any question. I am see only suggestion of workaround.
Sorry if missunderstund.
You need some additional debug print?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: X2APIC support

2016-09-13 Thread Andriy Gapon 
On 13/09/2016 15:42, Slawa Olhovchenkov wrote:
> On Tue, Sep 13, 2016 at 03:38:17PM +0300, Andriy Gapon wrote:
> 
>> On 13/09/2016 15:11, Slawa Olhovchenkov wrote:
>>> On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote:
>>>
 On 12/09/2016 20:53, Slawa Olhovchenkov wrote:
> boot_cpu_id = 255

 I think that this points towards the BIOS not configuring the BSP LAPIC
 correctly when you select that combination of BIOS options.
 That's weird, but I fail to find any other explanation.

 If wonder what would happen if you disable X2APIC_OPT_OUT and set
 hw.x2apic_enable=0 in loader.conf or at the loader prompt.
>>>
>>> Boot OK w/o hw.x2apic_enable=0, only with disable X2APIC_OPT_OUT.
>>>
>>
>> This doesn't answer my question and doesn't add any new information, correct?
> 
> I am don't see any question. I am see only suggestion of workaround.
> Sorry if missunderstund.
> You need some additional debug print?
> 

I already knew from you that not enabling X2APIC_OPT_OUT fixed the problem.
"If wonder what would happen if you disable X2APIC_OPT_OUT and set
hw.x2apic_enable=0 in loader.conf or at the loader prompt."
This was a question even though there is no question mark.


-- 
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

11.0-RELEASE status update

2016-09-13 Thread Glen Barber 
There is one issue that was brought to our attention, which we are
waiting for feedback before classifying as an EN candidate.  Once we
receive feedback, the 11.0-RELEASE schedule should be updated to reflect
reality.

At present, I am hopeful 11.0-RC3 builds should start 9/14/2016 at 00:00
UTC (about 11 hours from now).

Thank you for your patience, and apologies for the delay.

Glen
On behalf of:   re@



signature.asc
Description: PGP signature

Jenkins build became unstable: FreeBSD_stable_10 #397

2016-09-13 Thread jenkins-admin 
See 

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: X2APIC support

2016-09-13 Thread Slawa Olhovchenkov 
On Tue, Sep 13, 2016 at 03:57:39PM +0300, Andriy Gapon wrote:

> On 13/09/2016 15:42, Slawa Olhovchenkov wrote:
> > On Tue, Sep 13, 2016 at 03:38:17PM +0300, Andriy Gapon wrote:
> > 
> >> On 13/09/2016 15:11, Slawa Olhovchenkov wrote:
> >>> On Tue, Sep 13, 2016 at 03:04:13PM +0300, Andriy Gapon wrote:
> >>>
>  On 12/09/2016 20:53, Slawa Olhovchenkov wrote:
> > boot_cpu_id = 255
> 
>  I think that this points towards the BIOS not configuring the BSP LAPIC
>  correctly when you select that combination of BIOS options.
>  That's weird, but I fail to find any other explanation.
> 
>  If wonder what would happen if you disable X2APIC_OPT_OUT and set
>  hw.x2apic_enable=0 in loader.conf or at the loader prompt.
> >>>
> >>> Boot OK w/o hw.x2apic_enable=0, only with disable X2APIC_OPT_OUT.
> >>>
> >>
> >> This doesn't answer my question and doesn't add any new information, 
> >> correct?
> > 
> > I am don't see any question. I am see only suggestion of workaround.
> > Sorry if missunderstund.
> > You need some additional debug print?
> > 
> 
> I already knew from you that not enabling X2APIC_OPT_OUT fixed the problem.
> "If wonder what would happen if you disable X2APIC_OPT_OUT and set
> hw.x2apic_enable=0 in loader.conf or at the loader prompt."
> This was a question even though there is no question mark.

boot failed:

set hw.x2apic_enable=0
loading required module 'krpc'
/boot/kernel.VSTREAM/krpc.ko size 0x2a210 at 0x134e000
loading required module 'opensolaris'
 ^@/boot/kernel.VSTREAM/opensolaris.ko size 0xadb8 at 0x1379000
/boot/kernel.VSTREAM/if_igb.ko size 0x69f10 at 0x1384000
can't find 'if_ixgbe'
/boot/kernel.VSTREAM/if_lagg.ko size 0x150c0 at 0x13ee000^M ^@
+/boot/kernel.VSTREAM/ukbd.ko size 0xe128 at 0x1404000
loading required module 'usb'
/boot/kernel.VSTREAM/usb.ko size 0x458b0 at 0x1413000^M|
 
/boot/kernel.VSTREAM/umass.ko size 0xaa10 at 0x1459000
/boot/kernel.VSTREAM/accf_http.ko size 0x2710 at 0x1464000
/boot/kernel.VSTREAM/uhci.ko size 0xd508 at 0x1467000
/boot/kernel.VSTREAM/ohci.ko size 0xc9d0 at 0x1475000^M
/boot/kernel.VSTREAM/ehci.ko size 0xfc40 at 0x1482000
/boot/kernel.VSTREAM/xhci.ko size 0x11068 at 0x1492000
/boot/kernel.VSTREAM/cc_htcp.ko size 0x3a70 at 0x14a4000
Booting...
Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.0-RELEASE-p305117 #0: Mon Sep 12 20:38:53 MSK 2016
s...@edge21.int.integros.com:/usr/obj/usr/src/sys/VSTREAM amd64
FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 
3.8.0)
VT(vga): text 80x25
CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz (2200.04-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x406f1  Family=0x6  Model=0x4f  Stepping=1
  
Features=0xbfebfbff
  
Features2=0x7ffefbff
  AMD Features=0x2c100800
  AMD Features2=0x121
  Structured Extended 
Features=0x21cbfbb
  XSAVE Features=0x1
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
  TSC: P-state invariant, performance statistics
real memory  = 137438953472 (131072 MB)
avail memory = 133407973376 (127227 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: 
boot_cpu_id = 255
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = ff
fault virtual address   = 0x0
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x80537e74
stack pointer   = 0x28:0x814b3a60
frame pointer   = 0x28:0x814b3a70
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= resume, IOPL = 0
current process = 0 ()
trap number = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0x805272e7 at kdb_backtrace+0x67
#1 0x804dd662 at vpanic+0x182
#2 0x804dd4d3 at panic+0x43
#3 0x807a37a1 at trap_fatal+0x351
#4 0x807a3993 at trap_pfault+0x1e3
#5 0x807a2f1c at trap+0x26c
#6 0x80787ca1 at calltrap+0x8
#7 0x8083b53a at topo_probe+0x61a
#8 0x8078fe93 at cpu_mp_start+0x1c3
#9 0x805382ca at mp_start+0x3a
#10 0x80465cd8 at mi_startup+0x118
#11 0x8028dfac at btext+0x2c
Uptime: 1s
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: X2APIC support

2016-09-13 Thread Andriy Gapon 
On 13/09/2016 17:21, Slawa Olhovchenkov wrote:
> boot failed:
> 
> set hw.x2apic_enable=0
> loading required module 'krpc'
> /boot/kernel.VSTREAM/krpc.ko size 0x2a210 at 0x134e000
> loading required module 'opensolaris'
>  ^@/boot/kernel.VSTREAM/opensolaris.ko size 0xadb8 at 0x1379000
> /boot/kernel.VSTREAM/if_igb.ko size 0x69f10 at 0x1384000
> can't find 'if_ixgbe'
> /boot/kernel.VSTREAM/if_lagg.ko size 0x150c0 at 0x13ee000^M ^@
> +/boot/kernel.VSTREAM/ukbd.ko size 0xe128 at 0x1404000
> loading required module 'usb'
> /boot/kernel.VSTREAM/usb.ko size 0x458b0 at 0x1413000^M|
>  
> /boot/kernel.VSTREAM/umass.ko size 0xaa10 at 0x1459000
> /boot/kernel.VSTREAM/accf_http.ko size 0x2710 at 0x1464000
> /boot/kernel.VSTREAM/uhci.ko size 0xd508 at 0x1467000
> /boot/kernel.VSTREAM/ohci.ko size 0xc9d0 at 0x1475000^M
> /boot/kernel.VSTREAM/ehci.ko size 0xfc40 at 0x1482000
> /boot/kernel.VSTREAM/xhci.ko size 0x11068 at 0x1492000
> /boot/kernel.VSTREAM/cc_htcp.ko size 0x3a70 at 0x14a4000
> Booting...
> Copyright (c) 1992-2016 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 11.0-RELEASE-p305117 #0: Mon Sep 12 20:38:53 MSK 2016
> s...@edge21.int.integros.com:/usr/obj/usr/src/sys/VSTREAM amd64
> FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 
> 3.8.0)
> VT(vga): text 80x25
> CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz (2200.04-MHz K8-class CPU)
>   Origin="GenuineIntel"  Id=0x406f1  Family=0x6  Model=0x4f  Stepping=1
>   
> Features=0xbfebfbff
>   
> Features2=0x7ffefbff
>   AMD Features=0x2c100800
>   AMD Features2=0x121
>   Structured Extended 
> Features=0x21cbfbb
>   XSAVE Features=0x1
>   VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
>   TSC: P-state invariant, performance statistics
> real memory  = 137438953472 (131072 MB)
> avail memory = 133407973376 (127227 MB)
> Event timer "LAPIC" quality 600
> ACPI APIC Table: 
> boot_cpu_id = 255
> kernel trap 12 with interrupts disabled
> 
> 
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = ff
> fault virtual address   = 0x0
> fault code  = supervisor read data, page not present
> instruction pointer = 0x20:0x80537e74
> stack pointer   = 0x28:0x814b3a60
> frame pointer   = 0x28:0x814b3a70
> code segment= base 0x0, limit 0xf, type 0x1b
> = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags= resume, IOPL = 0
> current process = 0 ()
> trap number = 12
> panic: page fault
> cpuid = 0
> KDB: stack backtrace:
> #0 0x805272e7 at kdb_backtrace+0x67
> #1 0x804dd662 at vpanic+0x182
> #2 0x804dd4d3 at panic+0x43
> #3 0x807a37a1 at trap_fatal+0x351
> #4 0x807a3993 at trap_pfault+0x1e3
> #5 0x807a2f1c at trap+0x26c
> #6 0x80787ca1 at calltrap+0x8
> #7 0x8083b53a at topo_probe+0x61a
> #8 0x8078fe93 at cpu_mp_start+0x1c3
> #9 0x805382ca at mp_start+0x3a
> #10 0x80465cd8 at mi_startup+0x118
> #11 0x8028dfac at btext+0x2c
> Uptime: 1s

Thank you!
It seems like exactly the same behavior that happens when you toggle that BIOS
option.

My theory is that in both cases, hw.x2apic_enable=0 and X2APIC_OPT_OUT is on,
the BIOS turns on x2APIC mode and transitions to OS in that mode.
In the case when X2APIC_OPT_OUT is on it's clearly a BIOS bug.
But maybe we could do a little bit better in both cases.  At the very least we
could detect the situation and panic with a helpful message (e.g. "x2APIC mode
is disabled but turn on by BIOS").  Perhaps we could even try to downgrade to
xAPIC mode.

-- 
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: X2APIC support

2016-09-13 Thread Slawa Olhovchenkov 
On Tue, Sep 13, 2016 at 05:54:26PM +0300, Andriy Gapon wrote:

> On 13/09/2016 17:21, Slawa Olhovchenkov wrote:
> > boot failed:
> > 
> > set hw.x2apic_enable=0
> > loading required module 'krpc'
> > /boot/kernel.VSTREAM/krpc.ko size 0x2a210 at 0x134e000
> > loading required module 'opensolaris'
> >  ^@/boot/kernel.VSTREAM/opensolaris.ko size 0xadb8 at 0x1379000
> > /boot/kernel.VSTREAM/if_igb.ko size 0x69f10 at 0x1384000
> > can't find 'if_ixgbe'
> > /boot/kernel.VSTREAM/if_lagg.ko size 0x150c0 at 0x13ee000^M ^@
> > +/boot/kernel.VSTREAM/ukbd.ko size 0xe128 at 0x1404000
> > loading required module 'usb'
> > /boot/kernel.VSTREAM/usb.ko size 0x458b0 at 0x1413000^M|
> >  
> > /boot/kernel.VSTREAM/umass.ko size 0xaa10 at 0x1459000
> > /boot/kernel.VSTREAM/accf_http.ko size 0x2710 at 0x1464000
> > /boot/kernel.VSTREAM/uhci.ko size 0xd508 at 0x1467000
> > /boot/kernel.VSTREAM/ohci.ko size 0xc9d0 at 0x1475000^M
> > /boot/kernel.VSTREAM/ehci.ko size 0xfc40 at 0x1482000
> > /boot/kernel.VSTREAM/xhci.ko size 0x11068 at 0x1492000
> > /boot/kernel.VSTREAM/cc_htcp.ko size 0x3a70 at 0x14a4000
> > Booting...
> > Copyright (c) 1992-2016 The FreeBSD Project.
> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> > The Regents of the University of California. All rights reserved.
> > FreeBSD is a registered trademark of The FreeBSD Foundation.
> > FreeBSD 11.0-RELEASE-p305117 #0: Mon Sep 12 20:38:53 MSK 2016
> > s...@edge21.int.integros.com:/usr/obj/usr/src/sys/VSTREAM amd64
> > FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 
> > 3.8.0)
> > VT(vga): text 80x25
> > CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz (2200.04-MHz K8-class CPU)
> >   Origin="GenuineIntel"  Id=0x406f1  Family=0x6  Model=0x4f  Stepping=1
> >   
> > Features=0xbfebfbff
> >   
> > Features2=0x7ffefbff
> >   AMD Features=0x2c100800
> >   AMD Features2=0x121
> >   Structured Extended 
> > Features=0x21cbfbb
> >   XSAVE Features=0x1
> >   VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
> >   TSC: P-state invariant, performance statistics
> > real memory  = 137438953472 (131072 MB)
> > avail memory = 133407973376 (127227 MB)
> > Event timer "LAPIC" quality 600
> > ACPI APIC Table: 
> > boot_cpu_id = 255
> > kernel trap 12 with interrupts disabled
> > 
> > 
> > Fatal trap 12: page fault while in kernel mode
> > cpuid = 0; apic id = ff
> > fault virtual address   = 0x0
> > fault code  = supervisor read data, page not present
> > instruction pointer = 0x20:0x80537e74
> > stack pointer   = 0x28:0x814b3a60
> > frame pointer   = 0x28:0x814b3a70
> > code segment= base 0x0, limit 0xf, type 0x1b
> > = DPL 0, pres 1, long 1, def32 0, gran 1
> > processor eflags= resume, IOPL = 0
> > current process = 0 ()
> > trap number = 12
> > panic: page fault
> > cpuid = 0
> > KDB: stack backtrace:
> > #0 0x805272e7 at kdb_backtrace+0x67
> > #1 0x804dd662 at vpanic+0x182
> > #2 0x804dd4d3 at panic+0x43
> > #3 0x807a37a1 at trap_fatal+0x351
> > #4 0x807a3993 at trap_pfault+0x1e3
> > #5 0x807a2f1c at trap+0x26c
> > #6 0x80787ca1 at calltrap+0x8
> > #7 0x8083b53a at topo_probe+0x61a
> > #8 0x8078fe93 at cpu_mp_start+0x1c3
> > #9 0x805382ca at mp_start+0x3a
> > #10 0x80465cd8 at mi_startup+0x118
> > #11 0x8028dfac at btext+0x2c
> > Uptime: 1s
> 
> Thank you!
> It seems like exactly the same behavior that happens when you toggle that BIOS
> option.
> 
> My theory is that in both cases, hw.x2apic_enable=0 and X2APIC_OPT_OUT is on,
> the BIOS turns on x2APIC mode and transitions to OS in that mode.
> In the case when X2APIC_OPT_OUT is on it's clearly a BIOS bug.
> But maybe we could do a little bit better in both cases.  At the very least we
> could detect the situation and panic with a helpful message (e.g. "x2APIC mode
> is disabled but turn on by BIOS").  Perhaps we could even try to downgrade to
> xAPIC mode.

Goggling on X2APIC_OPT_OUT take same result: other OS in this case
downgrade to xAPIC mode.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: X2APIC support

2016-09-13 Thread Konstantin Belousov 
On Tue, Sep 13, 2016 at 05:54:26PM +0300, Andriy Gapon wrote:
> On 13/09/2016 17:21, Slawa Olhovchenkov wrote:
> > boot failed:
> > 
> > set hw.x2apic_enable=0
> > loading required module 'krpc'
> > /boot/kernel.VSTREAM/krpc.ko size 0x2a210 at 0x134e000
> > loading required module 'opensolaris'
> >  ^@/boot/kernel.VSTREAM/opensolaris.ko size 0xadb8 at 0x1379000
> > /boot/kernel.VSTREAM/if_igb.ko size 0x69f10 at 0x1384000
> > can't find 'if_ixgbe'
> > /boot/kernel.VSTREAM/if_lagg.ko size 0x150c0 at 0x13ee000^M ^@
> > +/boot/kernel.VSTREAM/ukbd.ko size 0xe128 at 0x1404000
> > loading required module 'usb'
> > /boot/kernel.VSTREAM/usb.ko size 0x458b0 at 0x1413000^M|
> >  
> > /boot/kernel.VSTREAM/umass.ko size 0xaa10 at 0x1459000
> > /boot/kernel.VSTREAM/accf_http.ko size 0x2710 at 0x1464000
> > /boot/kernel.VSTREAM/uhci.ko size 0xd508 at 0x1467000
> > /boot/kernel.VSTREAM/ohci.ko size 0xc9d0 at 0x1475000^M
> > /boot/kernel.VSTREAM/ehci.ko size 0xfc40 at 0x1482000
> > /boot/kernel.VSTREAM/xhci.ko size 0x11068 at 0x1492000
> > /boot/kernel.VSTREAM/cc_htcp.ko size 0x3a70 at 0x14a4000
> > Booting...
> > Copyright (c) 1992-2016 The FreeBSD Project.
> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> > The Regents of the University of California. All rights reserved.
> > FreeBSD is a registered trademark of The FreeBSD Foundation.
> > FreeBSD 11.0-RELEASE-p305117 #0: Mon Sep 12 20:38:53 MSK 2016
> > s...@edge21.int.integros.com:/usr/obj/usr/src/sys/VSTREAM amd64
> > FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 
> > 3.8.0)
> > VT(vga): text 80x25
> > CPU: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz (2200.04-MHz K8-class CPU)
> >   Origin="GenuineIntel"  Id=0x406f1  Family=0x6  Model=0x4f  Stepping=1
> >   
> > Features=0xbfebfbff
> >   
> > Features2=0x7ffefbff
> >   AMD Features=0x2c100800
> >   AMD Features2=0x121
> >   Structured Extended 
> > Features=0x21cbfbb
> >   XSAVE Features=0x1
> >   VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
> >   TSC: P-state invariant, performance statistics
> > real memory  = 137438953472 (131072 MB)
> > avail memory = 133407973376 (127227 MB)
> > Event timer "LAPIC" quality 600
> > ACPI APIC Table: 
> > boot_cpu_id = 255
> > kernel trap 12 with interrupts disabled
> > 
> > 
> > Fatal trap 12: page fault while in kernel mode
> > cpuid = 0; apic id = ff
> > fault virtual address   = 0x0
> > fault code  = supervisor read data, page not present
> > instruction pointer = 0x20:0x80537e74
> > stack pointer   = 0x28:0x814b3a60
> > frame pointer   = 0x28:0x814b3a70
> > code segment= base 0x0, limit 0xf, type 0x1b
> > = DPL 0, pres 1, long 1, def32 0, gran 1
> > processor eflags= resume, IOPL = 0
> > current process = 0 ()
> > trap number = 12
> > panic: page fault
> > cpuid = 0
> > KDB: stack backtrace:
> > #0 0x805272e7 at kdb_backtrace+0x67
> > #1 0x804dd662 at vpanic+0x182
> > #2 0x804dd4d3 at panic+0x43
> > #3 0x807a37a1 at trap_fatal+0x351
> > #4 0x807a3993 at trap_pfault+0x1e3
> > #5 0x807a2f1c at trap+0x26c
> > #6 0x80787ca1 at calltrap+0x8
> > #7 0x8083b53a at topo_probe+0x61a
> > #8 0x8078fe93 at cpu_mp_start+0x1c3
> > #9 0x805382ca at mp_start+0x3a
> > #10 0x80465cd8 at mi_startup+0x118
> > #11 0x8028dfac at btext+0x2c
> > Uptime: 1s
> 
> Thank you!
> It seems like exactly the same behavior that happens when you toggle that BIOS
> option.
> 
> My theory is that in both cases, hw.x2apic_enable=0 and X2APIC_OPT_OUT is on,
> the BIOS turns on x2APIC mode and transitions to OS in that mode.
> In the case when X2APIC_OPT_OUT is on it's clearly a BIOS bug.
> But maybe we could do a little bit better in both cases.  At the very least we
> could detect the situation and panic with a helpful message (e.g. "x2APIC mode
> is disabled but turn on by BIOS").  Perhaps we could even try to downgrade to
> xAPIC mode.

If hw.x2apic_enable=0 and machine booted to the stage of topo probe,
BIOS definitely did not made hand-off with x2APIC enabled.  Any access
to the LAPIC registers page in x2APIC mode faults.

And X2APIC_OPT_OUT also does not result in x2APIC mode hand-off, for the
same reason.  System would panic much earlier, while dmesg indicates that
LAPIC ICR calibration was succesful.

It is invalid LAPIC Id or a bug in topo code or combination of issues.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: X2APIC support

2016-09-13 Thread Andriy Gapon 
On 13/09/2016 18:22, Konstantin Belousov wrote:
> Any access
> to the LAPIC registers page in x2APIC mode faults.

Is this a fact?
I read the following in the specification:

  In x2APIC mode, the memory mapped interface is not available and any
  access to the MMIO interface will behave similar to that of a legacy xAPIC
  in globally disabled state.

But I couldn't find what actually happens for the legacy xAPIC in globally
disabled state.  For AMD processors it is documented that if xAPIC is disabled
then accessing the APIC memory range works the same as accessing the regular
memory.  That can be different for Intel processors, of course.

-- 
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Intel NVMe troubles?

2016-09-13 Thread Jim Harris 
On Monday, September 12, 2016, Borja Marcos  wrote:

>
> > On 12 Sep 2016, at 17:23, Jim Harris  > wrote:
> >
> > There is an updated DCT 3.0.2 at:  https://downloadcenter.intel.
> > com/download/26221/Intel-SSD-Data-Center-Tool which has a fix for this
> > issue.
> >
> > Borja has already downloaded this update and confirmed it looks good so
> > far.  Posting the update and results here so it is archived on the STABLE
> > mailing list.
>
> Is it just my imagination or has trim performance improved dramatically?
> I’m being unable to replicate
> the I/O stalls that I observed after running some simultaneous Bonnie++
> benchmarks with large files.


Yes - Trim performance should be significantly faster with the FW included
in the 3.0.2 DCT release.

Jim


>
> Thanks,
>
>
>
> Borja.
>
>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"