On Sat, Aug 25, 2018 at 11:51:21PM -0400, Theron wrote:
>
> A recent change in CURRENT has sysutils/acpi_call reliably cause a
> kernel panic when run on a Dell XPS laptop system. I bisected this to
> r336876: Use SMAP on amd64. I would have thought that this is a simple
> compatibility probl
A recent change in CURRENT has sysutils/acpi_call reliably cause a
kernel panic when run on a Dell XPS laptop system. I bisected this to
r336876: Use SMAP on amd64. I would have thought that this is a simple
compatibility problem requiring only a port update, except that the same
kernel and
On Sun, Aug 26, 2018 at 10:51 AM cpghost wrote:
> On 8/25/18 5:34 PM, Dave Cottlehuber wrote:
> >> On Sat, Aug 25, 2018 at 5:09 PM Stefan Hagen <
> sh+freebsd-curr...@codevoid.de>
> On Sat, Aug 25, 2018 at 7:43 AM Kris Moore wrote:
> > I've been personally using the new DRM bits since al
On 8/25/18 5:34 PM, Dave Cottlehuber wrote:
>> On Sat, Aug 25, 2018 at 5:09 PM Stefan Hagen
On Sat, Aug 25, 2018 at 7:43 AM Kris Moore wrote:
> I've been personally using the new DRM bits since almost day one. I
> haven't found it to be unstable in the slightest. Compared to not
>
On Sat, Aug 25, 2018 at 07:22:06PM -0700, Randy Bush wrote:
> plonk
Indeed. I encourage everyone else to do the same.
I'm far too old for proof-by-repetition.
mcl
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/
Is head buildworld buildkernel supposed to work with:
WITHOUT_BINUTILS_BOOTSTRAP=
without providing an alternate binutils binding for clang to find? My attempt
failed:
--- buildworld ---
make[1]: "/usr/src/Makefile.inc1" line 341: SYSTEM_COMPILER: Determined that
CC=cc matches the source tree.
On Sun, Aug 26, 2018 at 10:05 AM Allan Jude wrote:
> On 2018-08-25 21:20, blubee blubeeme wrote:
> > On Sun, Aug 26, 2018 at 9:08 AM Paul McNary wrote:
> >
> >> I think you can pay XinuOS to support FreeBSD in a LTS situation.
> >> It is just like linux where you have to pay Red Hat, Suse, etc.
> I'll just post this again to try and keep the focus on the issue at hand.
plonk
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebs
I think you can pay XinuOS to support FreeBSD in a LTS situation.
It is just like linux where you have to pay Red Hat, Suse, etc.
They break things even with point releases. Suse majorly
screwed with video drivers back in the 9.x series. Totally
broke major release. Their answer then was pay us or
On 2018-08-25 21:20, blubee blubeeme wrote:
> On Sun, Aug 26, 2018 at 9:08 AM Paul McNary wrote:
>
>> I think you can pay XinuOS to support FreeBSD in a LTS situation.
>> It is just like linux where you have to pay Red Hat, Suse, etc.
>> They break things even with point releases. Suse majorly
>>
On Sun, Aug 26, 2018 at 9:08 AM Paul McNary wrote:
> I think you can pay XinuOS to support FreeBSD in a LTS situation.
> It is just like linux where you have to pay Red Hat, Suse, etc.
> They break things even with point releases. Suse majorly
> screwed with video drivers back in the 9.x series.
On Sun, Aug 26, 2018 at 8:16 AM Johannes Lundberg
wrote:
>
>
> On Sun, Aug 26, 2018 at 00:25 blubee blubeeme wrote:
>
>> On Sun, Aug 26, 2018 at 2:08 AM Dag-Erling Smørgrav wrote:
>>
>> > blubee blubeeme writes:
>> > > True on both points my tone is just a reflection of attitudes of the
>> > >
On Sun, Aug 26, 2018 at 00:25 blubee blubeeme wrote:
> On Sun, Aug 26, 2018 at 2:08 AM Dag-Erling Smørgrav wrote:
>
> > blubee blubeeme writes:
> > > True on both points my tone is just a reflection of attitudes of the
> > > individuals that I am currently addressing.
> >
> > Well, congratulati
On Sun, Aug 26, 2018 at 2:08 AM Dag-Erling Smørgrav wrote:
> blubee blubeeme writes:
> > True on both points my tone is just a reflection of attitudes of the
> > individuals that I am currently addressing.
>
> Well, congratulations on alienating absolutely everybody you have
> interacted with on
On 8/25/18 11:51 AM, Warner Losh wrote:
On Sat, Aug 25, 2018, 12:17 PM Pete Wright wrote:
On 8/25/18 11:10 AM, Yuri Pankov wrote:
Pete Wright wrote:
howdy - just upgraded one of my machines to 12.0-ALPHA3 and noticed
that my usb mouse is not being detected. i made sure to do a proper
merg
On 08/22/2018 10:29, Alan Cox wrote:
> On 08/22/2018 08:48, tech-lists wrote:
>> On 22/08/2018 05:29, Manfred Antar wrote:
On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev
wrote:
On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote:
> Перенаправленное сообще
On Sat, Aug 25, 2018 at 12:10 PM Kristof Provost wrote:
> You may be right about that. With memguard (on ifnet) it implicates pf:
>
> pfi_cleanup_vnet() at pfi_cleanup_vnet+0xa4/frame 0xfe084f775320
> vnet_pf_uninit() at vnet_pf_uninit+0x85f/frame 0xfe084f7757c0
> vnet_destroy() at vnet_d
You may be right about that. With memguard (on ifnet) it implicates pf:
pfi_cleanup_vnet() at pfi_cleanup_vnet+0xa4/frame 0xfe084f775320
vnet_pf_uninit() at vnet_pf_uninit+0x85f/frame 0xfe084f7757c0
vnet_destroy() at vnet_destroy+0x12c/frame 0xfe084f7757f0
prison_deref() at prison_der
___
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"
On Sat, Aug 25, 2018, 12:17 PM Pete Wright wrote:
>
>
> On 8/25/18 11:10 AM, Yuri Pankov wrote:
> > Pete Wright wrote:
> >> howdy - just upgraded one of my machines to 12.0-ALPHA3 and noticed
> >> that my usb mouse is not being detected. i made sure to do a proper
> >> mergemaster after building
On 8/25/18 11:10 AM, Yuri Pankov wrote:
Pete Wright wrote:
howdy - just upgraded one of my machines to 12.0-ALPHA3 and noticed
that my usb mouse is not being detected. i made sure to do a proper
mergemaster after building my kernel and world, and verified that
updates to devd configs were p
Pete Wright wrote:
howdy - just upgraded one of my machines to 12.0-ALPHA3 and noticed that
my usb mouse is not being detected. i made sure to do a proper
mergemaster after building my kernel and world, and verified that
updates to devd configs were picked up as per UPDATING.
i am seeing the
blubee blubeeme writes:
> True on both points my tone is just a reflection of attitudes of the
> individuals that I am currently addressing.
Well, congratulations on alienating absolutely everybody you have
interacted with on this topic.
> Some people enjoy making contributions w/o waving a bann
howdy - just upgraded one of my machines to 12.0-ALPHA3 and noticed that
my usb mouse is not being detected. i made sure to do a proper
mergemaster after building my kernel and world, and verified that
updates to devd configs were picked up as per UPDATING.
i am seeing the following in my dme
I'll take a look. But it's likely to not be the OP's issue. For future
reference memguard on the memory type in question is extremely useful in
catching use after free.
-M
On Sat, Aug 25, 2018 at 05:51 Kristof Provost wrote:
> On 25 Aug 2018, at 0:47, Kristof Provost wrote:
>
> On 25 Aug 2018,
>> On 24. Aug 2018, at 22:39, Konstantin Belousov wrote:
>>
>> On Fri, Aug 24, 2018 at 10:32:06PM +0200, Michael Gmelin wrote:
>>
>>
>>> On 24. Aug 2018, at 21:59, Konstantin Belousov wrote:
>>> Please apply the following debugging patch on top of the previous 'fix'.
>>> You need debug.late
Hi Owen
I'm truly sorry you feel this way about our work.
At first I was thinking "I'm not going to feed the troll" but after giving
what you're writing some more thought it seems maybe you have misunderstood
some things that I want to clarify to make sure there's no misunderstanding
by you or an
On 08/25, Niclas Zeising wrote:
On 08/24/18 17:20, Warner Losh wrote:
This would allow the graphics port to have a rc script that sets
this up so when X11 goes to automatically load the module, the right one
gets loaded.
I just want to point out that X11 doesn't load the graphics kernel
driv
> On Sat, Aug 25, 2018 at 5:09 PM Stefan Hagen
> > > On Sat, Aug 25, 2018 at 7:43 AM Kris Moore wrote:
> > >> I've been personally using the new DRM bits since almost day one. I
> > >> haven't found it to be unstable in the slightest. Compared to not
> > >> having it and being forced to run 5+ yea
On 25 Aug 2018, at 0:47, Kristof Provost wrote:
On 25 Aug 2018, at 0:26, Matthew Macy wrote:
On Fri, Aug 24, 2018 at 15:25 Shawn Webb
wrote:
Hey All,
Somewhere in the last month or so, a use after free was introduced.
I
don't have the time right now to bisect the commits and figure out
On Sat, Aug 25, 2018 at 5:09 PM Stefan Hagen
wrote:
> blubee blubeeme wrote:
> > On Sat, Aug 25, 2018 at 7:43 AM Kris Moore wrote:
> >> I've been personally using the new DRM bits since almost day one. I
> >> haven't found it to be unstable in the slightest. Compared to not
> >> having it and bei
On Sat, Aug 25, 2018 at 11:30:41AM +0200, O. Hartmann wrote:
>
> For some experiments on PINE64 we build packages from FreeBSD's base system.
> The
> individual package seems to comprise always from several flavours, the
> "regular/production" one, profile/profiling one and development, for insta
On 25 Aug 2018, at 9:06, O. Hartmann wrote:
I'm using ezjail-admin from ports (most recent tree, up to date as of
today, at Revision:
478001, FreeBSD is FreeBSD 12.0-ALPHA3 #455 r338309: Sat Aug 25
07:10:45 CEST 2018 amd64,
the jails sources are at revision 338309).
Updates of the jail's base
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
For some experiments on PINE64 we build packages from FreeBSD's base system. The
individual package seems to comprise always from several flavours, the
"regular/production" one, profile/profiling one and development, for instance
for package
FreeBS
blubee blubeeme wrote:
> On Sat, Aug 25, 2018 at 7:43 AM Kris Moore wrote:
>> I've been personally using the new DRM bits since almost day one. I
>> haven't found it to be unstable in the slightest. Compared to not
>> having it and being forced to run 5+ year old hardware, it's been a
>> huge bless
On Sat, Aug 25, 2018 at 4:27 PM Matthew Macy wrote:
> Hi Owen -
> I understand that you're enthusiastic and you just want what's best for
> the project. However, there's a couple of points I hope you'll take to
> heart. First, please read what you sent and think about the tone and word
> choice.
Isn't Intel supposed to be working on a native drm driver for FreeBSD?
https://bwidawsk.net/blog/index.php/2018/06/i965-compiler-architecture-from-2015/
On Sat, Aug 25, 2018 at 12:19 AM, Matthew Macy wrote:
>
>
> On Fri, Aug 24, 2018 at 14:53 Ali wrote:
>
>> On Tue, Aug 21, 2018 at 06:54:54PM
Hi Owen -
I understand that you're enthusiastic and you just want what's best for the
project. However, there's a couple of points I hope you'll take to heart.
First, please read what you sent and think about the tone and word choice.
It's extremely negative and critical - you're actively alienatin
Hi,
I get an immediate reset/reboot of the system with an enabled watchdog
on r338290. If I disable it no reset. With r336767 the enabled
watchdog doesn't cause an immediate reset.
Can someone test?
rc.conf:
---snip---
watchdogd_enable="YES"
watchdogd_flags="-e /root/bin/wd_check.sh -s 5 -
On Sat, Aug 25, 2018 at 10:04 AM Mark Linimon wrote:
> On Sat, Aug 25, 2018 at 07:07:24AM +0800, blubee blubeeme wrote:
> > Are these guys insane and please avoid the nonsense about you're doing
> this
> > in your spare time.
>
> Let us know how whatever OS you wind up using instead works for you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'm using ezjail-admin from ports (most recent tree, up to date as of today, at
Revision:
478001, FreeBSD is FreeBSD 12.0-ALPHA3 #455 r338309: Sat Aug 25 07:10:45 CEST
2018 amd64,
the jails sources are at revision 338309).
Updates of the jail's ba
41 matches
Mail list logo
