On 4/08/2016 1:18 AM, Lundberg, Johannes wrote:
Hi Alan
Thanks for the reply.
Can I still use the same receiving function for sendmsg/send and tell what
kind of message is coming?
How would I tell if there is an fd attached or not?
Even if I set cmsg_level and cmsg_type it won't let me send i
2016-08-03 19:18 GMT+02:00 Lundberg, Johannes :
> Even if I set cmsg_level and cmsg_type it won't let me send it. The problem
> is having a zero length attachment on freebsd
> I can't send -1 as fd because that errors to invalid file descriptor.
Well, it makes sense. If you're attaching a mess
I get this panic periodically at iwm load time:
(kgdb) p ic->ic_tq
value has been optimized out
(kgdb) down
#12 taskqueue_drain (queue=0x0, task=0xfe004fc17150) at
/usr/home/mmacy/drm-next-4.6/sys/kern/subr_taskqueue.c:554
554 TQ_LOCK(queue);
(kgdb) bt
#0 __curthread () at ./machi
On 08/04/16 09:56, K. Macy wrote:
#12 taskqueue_drain (queue=0x0, task=0xfe004fc17150) at
Hi,
Looks like a NULL pointer, queue=NULL
--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To
Uhm, yes. I can read that too. I'm suggesting that someone working on
the iwm driver can fix it.
On the boot immediately prior to this my system panicked with an
assert in idr - which is much more my bailiwick.
-M
On Thu, Aug 4, 2016 at 1:04 AM, Hans Petter Selasky wrote:
> On 08/04/16 09:56,
Any idea which revision/commit introduced this regression?
(I want to test iwm + freebsd-base-graphics on my laptop tonight and
hence avoid crashers like this one in advance.)
@mmacy: is the revision in the current drm-next-4.6 branch of
https://github.com/FreeBSDDesktop/freebsd-base-gra
On Thursday, August 04, 2016 08:59:06 AM Gary Jennejohn wrote:
> On Tue, 02 Aug 2016 10:41:23 -0700
> John Baldwin wrote:
>
> > On Tuesday, August 02, 2016 09:03:10 AM Gary Jennejohn wrote:
> > > On Mon, 01 Aug 2016 13:19:16 -0700
> > > John Baldwin wrote:
> > >
> > > > On Monday, August 01,
As those of you tracking our PR system are probably aware, re@ is aware
of an issue related to ZFS and VFS that we feel is urgent enough to have
fixed for 11.0-RELEASE.
https://lists.freebsd.org/pipermail/freebsd-current/2016-August/062829.html
As such, instead of branching releng/11.0 today and
On Thursday, August 4, 2016, Christian Schwarz wrote:
> Any idea which revision/commit introduced this regression?
>
> (I want to test iwm + freebsd-base-graphics on my laptop tonight and
> hence avoid crashers like this one in advance.)
>
> @mmacy: is the revision in the current drm-next-4.6 br
Should I open a bug report, or has the problem been noted?
Mark
On 2016-08-04 04:32, Julian Elischer wrote:
On 4/08/2016 7:24 AM, Mark Martinec wrote:
Is it normal/expected/documented that the date(1) command in 11.0
now produces a timestamp in substantially different format
in an "en_US.UT
Reposted to -current to get some more eyes on this ...
I just got a kernel panic when I started up a CentOS 7 VM in virtualbox.
The host is:
FreeBSD 12.0-CURRENT #17 r302500 GENERIC amd64
The virtualbox version is:
virtualbox-ose-5.0.26
virtualbox-ose-kmod-5.0.26_1
The pan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This is a heads-up that OpenSSH keys are deprecated upstream by OpenSSH,
and will be deprecated effective 11.0-RELEASE (and preceeding RCs).
Please see r303716 for details on the relevant commit, but upstream no
longer considers them secure. Please
On Fri, Aug 05, 2016 at 01:59:18AM +, Glen Barber wrote:
> This is a heads-up that OpenSSH keys are deprecated upstream by OpenSSH,
> and will be deprecated effective 11.0-RELEASE (and preceeding RCs).
>
Stupid editor mistake. OpenSSH DSA keys are deprecated upstream. Sorry
for any confusio
On 5/08/2016 5:44 AM, Mark Martinec wrote:
Should I open a bug report, or has the problem been noted?
it's not clear without reading the standard whether the bug is in the
old or new version.
have you tried other systems? In particular I'd check OSX
sh-3.2$ export LC_CTYPE="en_US.UTF-8"
sh-3.2
On 03/08/2016 17:25, Andriy Gapon wrote:
> Another change that was not strictly required and which is probably too
> intrusive is killing the support for case insensitive operations. My
> thinking was that FreeBSD VFS does not provide support for those anyway.
> But I'll probably restore the cod
15 matches
Mail list logo