[Bug 207940] [patch] sys/boot/efi/boot1 select boot partition

2016-03-12 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207940

Bug ID: 207940
   Summary: [patch] sys/boot/efi/boot1 select boot partition
   Product: Base System
   Version: 11.0-CURRENT
  Hardware: amd64
OS: Any
Status: New
  Keywords: patch
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: freebsd-b...@freebsd.org
  Reporter: n...@enuenu.org
CC: freebsd-amd64@FreeBSD.org
  Keywords: patch
CC: freebsd-amd64@FreeBSD.org

Created attachment 168070
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=168070=edit
patch for efi boot1 partition selection

Current efi boo1 allows boot from auto-selected (first match) partition only.
I write patch to allow boot-time partiton selection for boot1.efi.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-amd64@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"

[Bug 206758] [PATCH] Uninitalized variable in atrun

2016-03-12 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206758

Ngie Cooper  changed:

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |FIXED
  Flags|mfc-stable9?, mfc-stable10? |mfc-stable9+, mfc-stable10+

--- Comment #7 from Ngie Cooper  ---
(In reply to op from comment #4)

I just MFCed it to stable/10.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-amd64@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"

[Bug 206758] [PATCH] Uninitalized variable in atrun

2016-03-12 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206758

--- Comment #6 from commit-h...@freebsd.org ---
A commit references this bug:

Author: ngie
Date: Sat Mar 12 19:11:45 UTC 2016
New revision: 296757
URL: https://svnweb.freebsd.org/changeset/base/296757

Log:
  MFstable/10 r296756:

  MFC r295079:

  Fix the type for hw.ncpu, so sysctlbyname doesn't consistently fail on
  64-bit architectures where sizeof(int) != sizeof(size_t).

  PR: 206758

Changes:
_U  stable/9/
_U  stable/9/libexec/atrun/
  stable/9/libexec/atrun/atrun.c

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-amd64@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"

[Bug 206758] [PATCH] Uninitalized variable in atrun

2016-03-12 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206758

--- Comment #5 from commit-h...@freebsd.org ---
A commit references this bug:

Author: ngie
Date: Sat Mar 12 19:09:52 UTC 2016
New revision: 296756
URL: https://svnweb.freebsd.org/changeset/base/296756

Log:
  MFC r295079:

  Fix the type for hw.ncpu, so sysctlbyname doesn't consistently fail on
  64-bit architectures where sizeof(int) != sizeof(size_t).

  PR: 206758

Changes:
_U  stable/10/
  stable/10/libexec/atrun/atrun.c

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-amd64@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"

Failure to probe Intel Cougar Point in ESX?

2016-03-12 Thread Darren Reed 
At long last a VT-d capable replacement CPU arrived for my HP MicroServer
Gen8and I thought "cool, now I can pass through the hard drives!". Life
is so simple when you're just a spectator. To pass through only the four
hard drive bays on a Gen8 Mircoserver requires either having a dedicated
SAS/SATA/RAID card that connects only to them or changing the BIOS config
to do "SATA Legacy". In SATA Legacy the HP Microserver Gen8 presents two
SATA controllers to ESXi: 1*4 Port, 1*2 Port. At this point it looks to
be simple: just tick the box for the 4 port controller to be in pass-
through mode and you're done. Not quite. Yes, putting the 4 port SATA
controller into pass-through mode allows it to be passed into FreeBSD
as a PCI device but when FreeBSD gets it, well, it comes in the diet
version - without any hard drives attached. This can be seen in the
extract from /var/log/messages below - disks are found and attached
that are presented as regular VMDK files but nothing is discovered
underatapci1 beyond ata3 and ata4. If this were NetBSD I'd suspect that
there was a missing "wd* at ata*" or similar but FreeBSD doesn't work
like that so I'm a bit mystified.

Darren

Mar 13 06:46:18 freebsd kernel: FreeBSD 9.3-RELEASE #0 r268512: Thu Jul
10 23:44:39 UTC 2014
Mar 13 06:46:18 freebsd kernel:
r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
Mar 13 06:46:18 freebsd kernel: gcc version 4.2.1 20070831 patched [FreeBSD]
Mar 13 06:46:18 freebsd kernel: CPU: Intel(R) Xeon(R) CPU E3-1265L V2 @
2.50GHz (2494.33-MHz K8-class CPU)
Mar 13 06:46:18 freebsd kernel: Origin = "GenuineIntel"  Id = 0x306a9 
Family = 0x6  Model = 0x3a  Stepping = 9
Mar 13 06:46:18 freebsd kernel:
Features=0xfa3fbff
Mar 13 06:46:18 freebsd kernel:
Features2=0x9e982203
Mar 13 06:46:18 freebsd kernel: AMD
Features=0x28100800
Mar 13 06:46:18 freebsd kernel: AMD Features2=0x1
...
Mar 13 06:46:18 freebsd kernel: atapci0: 
port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1060-0x106f at device 7.1 on pci0
Mar 13 06:46:18 freebsd kernel: ata0:  at channel 0 on atapci0
Mar 13 06:46:18 freebsd kernel: ata1:  at channel 1 on atapci0
Mar 13 06:46:18 freebsd kernel: pci0:  at device 7.3 (no driver
attached)
Mar 13 06:46:18 freebsd kernel: vgapci0:  port
0x1070-0x1
07f mem 0xec00-0xefff,0xfe00-0xfe7f irq 16 at device
15.0 on pci0
Mar 13 06:46:18 freebsd kernel: vgapci0: Boot video device
Mar 13 06:46:18 freebsd kernel: mpt0: 
port 0x1400-0x14ff mem 0xfeba-0xfebb,0xfebc-0xfebd irq
17 at device 16.0 on pci0
Mar 13 06:46:18 freebsd kernel: mpt0: MPI Version=1.2.0.0
Mar 13 06:46:18 freebsd kernel: pcib2:  at device
17.0 on pci0
Mar 13 06:46:18 freebsd kernel: pci2:  on pcib2
Mar 13 06:46:18 freebsd kernel: pcib3:  at device
21.0 on pci0
Mar 13 06:46:18 freebsd kernel: pci3:  on pcib3
Mar 13 06:46:18 freebsd kernel: atapci1: 
port
0x4038-0x403f,0x4030-0x4033,0x4028-0x402f,0x4024-0x4027,0x4010-0x401f,0x4000-0x400f
irq 19 at device 0.0 on pci3
Mar 13 06:46:18 freebsd kernel: ata2:  at channel 0 on atapci1
Mar 13 06:46:18 freebsd kernel: ata3:  at channel 1 on atapci1
Mar 13 06:46:18 freebsd kernel: da0 at mpt0 bus 0 scbus2 target 0 lun 0
Mar 13 06:46:18 freebsd kernel: da0:  Fixed
Direct Access SCSI-2 device
Mar 13 06:46:18 freebsd kernel: da0: 320.000MB/s transfers (160.000MHz,
offset 127, 16bit)
Mar 13 06:46:18 freebsd kernel: da0: Command Queueing enabled
Mar 13 06:46:18 freebsd kernel: da0: 30720MB (62914560 512 byte sectors:
255H 63S/T 3916C)
Mar 13 06:46:18 freebsd kernel: da1 at mpt0 bus 0 scbus2 target 1 lun 0
Mar 13 06:46:18 freebsd kernel: da1:  Fixed
Direct Access SCSI-2 device
Mar 13 06:46:18 freebsd kernel: da1: 320.000MB/s transfers (160.000MHz,
offset 127, 16bit)
Mar 13 06:46:18 freebsd kernel: da1: Command Queueing enabled
Mar 13 06:46:18 freebsd kernel: da1: 61440MB (125829120 512 byte
sectors: 255H 63S/T 7832C)
Mar 13 06:46:18 freebsd kernel: da2 at mpt0 bus 0 scbus2 target 2 lun 0
Mar 13 06:46:18 freebsd kernel: da2:  Fixed
Direct Access SCSI-2 device
Mar 13 06:46:18 freebsd kernel: da2: 320.000MB/s transfers (160.000MHz,
offset 127, 16bit)
Mar 13 06:46:18 freebsd kernel: da2: Command Queueing enabled
Mar 13 06:46:18 freebsd kernel: da2: 30720MB (62914560 512 byte sectors:
255H 63S/T 3916C)
Mar 13 06:46:18 freebsd kernel: cd0 at ata1 bus 0 scbus1 target 0 lun 0
Mar 13 06:46:18 freebsd kernel: cd0: 
Removable CD-ROM SCSI-0 device
Mar 13 06:46:18 freebsd kernel: cd0: Serial Number 1001
Mar 13 06:46:18 freebsd kernel: cd0: 33.300MB/s transfers (UDMA2, ATAPI
12bytes,PIO 65534bytes)
Mar 13 06:46:18 freebsd kernel: cd0: Attempt to query device size
failed: NOT READY, Medium not present
Mar 13 06:46:18 freebsd kernel: Timecounter "TSC-low" frequency
1247167000 Hz quality 1000

[Bug 207918] C++ ostream operator << broken for unsigned long long when using showbase with octal format

2016-03-12 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207918

Mahdi Mokhtari  changed:

   What|Removed |Added

 Status|New |In Progress
 CC||mokh...@gmail.com

--- Comment #1 from Mahdi Mokhtari  ---
I've checked this.
I figured out it happens for all ::max() ones, seems because of 
"this->fill()".

This could be changed easily, though i think we should see which is the better
(standard) behavior (use fill in all cases or exclude showbase case) ?

this is the code i talking based on(contrib/libc++/include/ostream):



template 
basic_ostream<_CharT, _Traits>&
basic_ostream<_CharT, _Traits>::operator<<(unsigned long long __n)
{
#ifndef _LIBCPP_NO_EXCEPTIONS
try
{
#endif  // _LIBCPP_NO_EXCEPTIONS
sentry __s(*this);
if (__s)
{
typedef num_put > _Fp;
const _Fp& __f = use_facet<_Fp>(this->getloc());
if (__f.put(*this, *this, this->fill(), __n).failed())
this->setstate(ios_base::badbit | ios_base::failbit);
}
#ifndef _LIBCPP_NO_EXCEPTIONS
}
catch (...)
{
this->__set_badbit_and_consider_rethrow();
}
#endif  // _LIBCPP_NO_EXCEPTIONS
return *this;
}




regards, Mokhi.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-amd64@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"

[Bug 207899] i915kms kernel module build failed

2016-03-12 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207899

Alexandr Krivulya  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

--- Comment #1 from Alexandr Krivulya  ---
Fixed:

rm -rf /usr/src/sys
svnlite update /usr/src

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-amd64@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"

[Bug 207918] C++ ostream operator << broken for unsigned long long when using showbase with octal format

2016-03-12 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207918

Bug ID: 207918
   Summary: C++ ostream operator << broken for unsigned long long
when using showbase with octal format
   Product: Base System
   Version: 10.3-BETA2
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: standards
  Assignee: freebsd-standa...@freebsd.org
  Reporter: dwmcr...@me.com
CC: freebsd-amd64@FreeBSD.org
CC: freebsd-amd64@FreeBSD.org

C++ library issue.

Using showbase with ostreams causes truncation of unsigned long long when
output format is octal.

#include 
#include 

int main(int argc, char *argv[])
{
  std::cout << std::oct;

  std::cout << std::numeric_limits::max()
<< '\n';
  std::cout << std::showbase
<< std::numeric_limits::max()
<< '\n';
  return 0;
}

Outputs:

17
01

Problem exists for 10.3-PRERELEASE r296556 for amd64 as well as 11.0-CURRENT
r292991 for arm.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-amd64@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"