On Wednesday, February 18, 2015 12:45:36 AM Jean-Sébastien Pédron wrote:
Hi!
An update to the DRM subsystem, not including the drivers, is ready for
wider testing!
The patch against HEAD is here:
https://people.freebsd.org/~dumbbell/graphics/drm-update-38.f.patch
I'm interested in
On 18-2-2015 1:09, Lundberg, Johannes wrote:
Hi
Good job! Will do some testing! As for the i915 driver, what versions are
supported? Up until and including HD4000 Gen7 Ivy bridge?
Correct.
--
Johannes Lundberg
BRILLIANTSERVICE CO., LTD.
On Wed, Feb 18, 2015 at 8:45 AM, Jean-Sébastien
On 18-2-2015 1:21, Shawn Webb wrote:
On Wednesday, February 18, 2015 12:45:36 AM Jean-Sébastien Pédron wrote:
Hi!
An update to the DRM subsystem, not including the drivers, is ready for
wider testing!
The patch against HEAD is here:
I just checked out head and applied the patch and all except the last hunk
applied successfully.
My sys/modules/drm2/radeonkms/Makefile looks like this at the end and
therefor fails:
#radeon_prime.c
#--radeon_trace_points.c
SRCS+=
Hi
Good job! Will do some testing! As for the i915 driver, what versions are
supported? Up until and including HD4000 Gen7 Ivy bridge?
--
Johannes Lundberg
BRILLIANTSERVICE CO., LTD.
On Wed, Feb 18, 2015 at 8:45 AM, Jean-Sébastien Pédron dumbb...@freebsd.org
wrote:
Hi!
An update to the
Oliver Pinter wrote this message on Tue, Feb 17, 2015 at 23:27 +0100:
On Tue, Feb 17, 2015 at 11:19 PM, Fabian Keil
freebsd-lis...@fabiankeil.de wrote:
John-Mark Gurney j...@funkthat.com wrote:
If you are running a current kernel r273872 or later, please upgrade
your kernel to r278907 or
Hi!
An update to the DRM subsystem, not including the drivers, is ready for
wider testing!
The patch against HEAD is here:
https://people.freebsd.org/~dumbbell/graphics/drm-update-38.f.patch
I'm interested in success/failure reports for amd64, powerpc and
powerpc64 users, for i915 and Radeon
On 17 February 2015 at 13:15, Ed Maste ema...@freebsd.org wrote:
One other point - this only applies to keys generated while running on
a kernel in that range. If you previously generated keys and then
upgraded to r273872 or later there's no concern with respect to key
randomness from this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/17/15 12:26, Konstantin Belousov wrote:
On Tue, Feb 17, 2015 at 12:00:04PM -0800, Sean Bruno wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512
On 02/17/15 00:56, Konstantin Belousov wrote:
On Mon, Feb 16, 2015 at 08:10:06PM -0800,
On 17 February 2015 at 12:37, John-Mark Gurney j...@funkthat.com wrote:
If you are running a current kernel r273872 or later, please upgrade
your kernel to r278907 or later immediately and regenerate keys.
One other point - this only applies to keys generated while running on
a kernel in that
Am Tue, 17 Feb 2015 18:32:22 +0100
Luca Pizzamiglio luca.pizzamig...@gmail.com schrieb:
Hi Ben,
thanks for the tip! tso was already disabled.
I tried anyway and unfortunately it crashes as before.
I filled a bug report
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197535) and marius@
Hi Ben,
thanks for the tip! tso was already disabled.
I tried anyway and unfortunately it crashes as before.
I filled a bug report
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197535) and marius@
is giving me a big help on it.
Best regards,
Luca
On Fri, Feb 13, 2015 at 7:34 PM, Ben
If you are running a current kernel r273872 or later, please upgrade
your kernel to r278907 or later immediately and regenerate keys.
I discovered an issue where the new framework code was not calling
randomdev_init_reader, which means that read_random(9) was not returning
good random data.
John-Mark Gurney wrote this message on Tue, Feb 17, 2015 at 09:37 -0800:
If you are running a current kernel r273872 or later, please upgrade
your kernel to r278907 or later immediately and regenerate keys.
I discovered an issue where the new framework code was not calling
On Sat, Feb 14, 2015 at 18:22:43 -0500, Dan Langille wrote:
On Feb 13, 2015, at 7:32 PM, Kenneth D. Merry k...@freebsd.org wrote:
I have a fairly large set of changes to the sa(4) driver and mt(1) driver
that I'm planning to commit in the near future.
A description of the
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
I suspect that there may be one or two more lines above this that are
relevant to this panic, but XENHVM kernel's now panic booting on Xen
server. The working kernel output looks like this:
FreeBSD clang version 3.4.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/17/15 00:56, Konstantin Belousov wrote:
On Mon, Feb 16, 2015 at 08:10:06PM -0800, Sean Bruno wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
I suspect that there may be one
On Tue, Feb 17, 2015 at 12:00:04PM -0800, Sean Bruno wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/17/15 00:56, Konstantin Belousov wrote:
On Mon, Feb 16, 2015 at 08:10:06PM -0800, Sean Bruno wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512
On Mon, Feb 16, 2015 at 08:10:06PM -0800, Sean Bruno wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
https://people.freebsd.org/~sbruno/Xen_APIC_panic.png
I suspect that there may be one or two more lines above this that are
relevant to this panic, but XENHVM kernel's now panic
John-Mark Gurney j...@funkthat.com wrote:
If you are running a current kernel r273872 or later, please upgrade
your kernel to r278907 or later immediately and regenerate keys.
I tried ...
start_init: trying /sbin/init
118[20] Setting hostuuid: [...]
118[20] Setting hostid: [...
[20]
[20]
On Tue, Feb 17, 2015 at 11:19 PM, Fabian Keil
freebsd-lis...@fabiankeil.de wrote:
John-Mark Gurney j...@funkthat.com wrote:
If you are running a current kernel r273872 or later, please upgrade
your kernel to r278907 or later immediately and regenerate keys.
I tried ...
start_init: trying
21 matches
Mail list logo
