Hi,
On Sat, Oct 25, 2014 at 3:50 PM, Zaphod Beeblebrox wrote:
> I tried to integrate this patch into 10.1_RC3 and I failed. Is there a
> timeframe to MFC this to 10.1 or 10-STABLE?
>
It will be MFCed to 10-STABLE but I don't have a specific time frame in mind.
I'll guess that it'll be towards
I tried to integrate this patch into 10.1_RC3 and I failed. Is there a
timeframe to MFC this to 10.1 or 10-STABLE?
On Sun, Oct 19, 2014 at 4:04 PM, Benjamin Perrault
wrote:
> After a few days of extensive testing and abuse, i’ve run into no new
> issues or unknowns what so ever. Everything that
Russell L. Carter wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 10/25/14 09:58, Beeblebrox wrote:
> > Hi Russ,
> >
> >>> PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs
> >>> ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0
> >>
> >> Possibly
I'm trying to build the current FreeBSD kernel, and that's what I get:
% sudo make buildkernel
--
>>> Kernel build for GENERIC started on Sun Oct 26 01:39:13 MSK 2014
--
===> GE
Kostik wrote:
> On Fri, Oct 24, 2014 at 04:43:28PM +0100, Robert Watson wrote:
> > On Thu, 23 Oct 2014, Rick Macklem wrote:
> >
> > > Someone just pinged me on this and I figured I should bring it
> > > up.
> > >
> > > 1 - Is anyone out there still using oldnfs due to unresolved
> > >problems
Russell L. Carter wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 10/25/14 09:58, Beeblebrox wrote:
> > Hi Russ,
> >
> >>> PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs
> >>> ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0
> >>
> >> Possibly
Russell L. Carter wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 10/25/14 03:07, Beeblebrox wrote:
> > * I can't get the NFS server to run V4 only. I have: sysctl
> > vfs.nfsd.server_min_nfsvers=4
> >
>
> [...]
>
> > PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 /
Beeblebrox wrote:
> * I can't get the NFS server to run V4 only. I have:
> sysctl vfs.nfsd.server_min_nfsvers=4
>
Hmm. With this set the NFS server shouldn't accept V2, 3
RPCs. The mount will work, since that is done by the Mount
protocol (mountd), but the client should be saying "server
not respo
Hi,
I can confirm v6 of the patch works for me with a r273559 kernel on a
i5-3320M notebook as well.
Only interesting new output to messages:
Oct 25 23:11:19 kernel: error: [drm:pid1159:gen6_sanitize_pm] *ERROR* Power
management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 0007, was
180700
Hello,
In short, nice kernel tasks people with C language skills can do in few
evenings.
https://wiki.freebsd.org/JuniorJobs
It is assumed you know how to obtain sources and build the kernel.
What you can get in return:
- your own code in FreeBSD tree
- eternal glory [1]
- fun [2]
If you are n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/14 09:58, Beeblebrox wrote:
> Hi Russ,
>
>>> PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs
>>> ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0
>>
>> Possibly need to arrange for mount_nfs to see -o nfsv4 (I
Hi Russ,
> > PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs
> > ro 0 0 192.168.2.1:/usr/local /usr/local nfs ro 0
>
> Possibly need to arrange for mount_nfs to see -o nfsv4
> (I use mount_nfs -o nfsv4,minorversion=1)
Yeah, that would work very likely and thanks.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/14 03:07, Beeblebrox wrote:
> * I can't get the NFS server to run V4 only. I have: sysctl
> vfs.nfsd.server_min_nfsvers=4
>
[...]
> PXE client's /etc/fstab is: 92.168.2.1:/data/amd64 / nfs
> ro 0 0 192.168.2.1:/usr/local
On Fri, 2014-10-24 at 21:06 -0400, owner-freebsd-curr...@freebsd.org
wrote:
> roberth...@rcn.com writes:
>
> > I am now doing "make buildkernel" with TARGET/TARGET_ARCH on
> > the command line. For installkernel, do I need to use them also,
> > or will it magically know where to look?
>
>
Garrett Cooper writes:
> The message is telling you (indirectly) that you need to run make
> buildworld successfully first?
Recapping:
Current system:
FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386
Source tree at CURRENT/r273626.
No make.c
* I can't get the NFS server to run V4 only. I have:
sysctl vfs.nfsd.server_min_nfsvers=4
I start all NFS-related services manually (from script)
#!/bin/sh
rpcbind -s -h 192.168.2.1
mountd -rnl -h 192.168.2.1
nfsd -ut -n 4 -h 192.168.2.1
nfsuserd
/etc/exports has:
V4: / -network 192.168.2.0/
On Fri, Oct 24, 2014 at 3:03 AM, Konstantin Belousov
wrote:
> Due to my mistake during the patch generation, i915.5.patch is just
> a garbage.
>
> Use https://www.kib.kiev.ua/kib/drm/i915.6.patch. I already have one
> private report of the patch worked from person who got the same panic
> in iicb
17 matches
Mail list logo