Hi all,
After my e-mail, some fixes for sys/amd64/amd64/pmapc. are commited.
I try to update newest current (r238163) and I hove no trouble.
My problem is fixed.
Thanks,
---
YAMAMOTO Shigeru
shig...@iij.ad.jp
___
freebsd-current@freebsd.org
On Thursday, July 05, 2012 11:04:07 pm Kaho Toshikazu wrote:
Hello John Baldwin, and all,
John Baldwin j...@freebsd.org wrote:
The system in general in 9.0 and later is more strict about honoring what
the
BIOS says in terms of allocating resources, so we have to be more correct
Hi,
On Fri, Jul 6, 2012 at 1:04 AM, Warner Losh i...@bsdimp.com wrote:
On Jul 5, 2012, at 5:14 PM, Arnaud Lacombe wrote:
Hi folks,
The problem has been raised in the last BSDCan during a talk, but no
clear answer has been given. Some (pseudo-)devices might require
resources from multiple
Hi,
On Fri, Jul 6, 2012 at 11:33 AM, Arnaud Lacombe lacom...@gmail.com wrote:
That's neither correct nor robust in a couple of way:
1) you have no guarantee a device unit will always give you the same
resource.
this raises the following question: how can a device, today, figure
out which
On Jul 6, 2012, at 12:46 PM, Arnaud Lacombe wrote:
Hi,
On Fri, Jul 6, 2012 at 11:33 AM, Arnaud Lacombe lacom...@gmail.com wrote:
That's neither correct nor robust in a couple of way:
1) you have no guarantee a device unit will always give you the same
resource.
this raises the following
On Fri, 2012-07-06 at 14:46 -0400, Arnaud Lacombe wrote:
Hi,
On Fri, Jul 6, 2012 at 11:33 AM, Arnaud Lacombe lacom...@gmail.com wrote:
That's neither correct nor robust in a couple of way:
1) you have no guarantee a device unit will always give you the same
resource.
this raises the
Hi,
On Fri, Jul 6, 2012 at 3:09 PM, Ian Lepore
free...@damnhippie.dyndns.org wrote:
On Fri, 2012-07-06 at 14:46 -0400, Arnaud Lacombe wrote:
Hi,
On Fri, Jul 6, 2012 at 11:33 AM, Arnaud Lacombe lacom...@gmail.com wrote:
That's neither correct nor robust in a couple of way:
1) you have no
Hello,
John Baldwin j...@freebsd.org wrote:
Almost all systems use one of the IDs we do support as a _CID if not a _HID.
In fact, in this case it likely seems to be a BIOS bug as it used the same
value for the _CID and _HID. I suspect it is supposed to be using 0303 as its
_CID.
I
On 07/06/12 00:21, O. Hartmann wrote:
On 07/05/12 23:27, John Baldwin wrote:
On Tuesday, July 03, 2012 1:43:30 am O. Hartmann wrote:
The most recent build of FreeBSD 10.0-CURRENT crashes on one of our
boxes with recent Intel hardware, see dmesg extract below. FreeBSD does
obviously only crash
