On Wednesday, March 04, 2015 10:35:34 AM Alfred Perlstein wrote:
On 3/4/15 8:21 AM, John Baldwin wrote:
I would probably want
pciconf -l in that case to dump the entire PCI header (right now the
human-readable pciconf -l only dumps a subset), and I would want it to dump
fields
previous functionality, but since I'm
not an expert on rc.d init scripts I would like some feedback on whether
this is the right approach or not.
Thanks, Roger.
If you are still looking for review, you can try freebsd-rc@ perhaps?
--
John Baldwin
} 1100046)
_yacc= lib/liby \
usr.bin/yacc
(but I won't commit it.)
Maybe just make the check always be 1100046? It doesn't really hurt to
build yacc on more recent 10 stable does it?
--
John Baldwin
___
freebsd-current
SKIPSPIN
in the GENERIC that is installed, outside of building a new
kernel?
The VFS ones are more complicated. You can add options 'WITNESS_NO_VNODE' to
your kernel config to limit the noise. (Someone should turn that into a
sysctl/tunable so it can be enabled in a stock kernel.)
--
John
in 10.1.
Can you narrow down the commit that broke it for you? I know there were some
msk(4) changes merged between 10.0 and 10.1 that fixed msk(4) for some other
folks.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http
using those labels for some controls now.) For
now I would start with Elizabeth's current patch of exposing the raw
i915 stuff via a sysctl. We can always remove this later if need be.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http
if it could
warn instead (GCC apparently has a warning, but clang does not). Having
people do a manual audit of every signed integer expression in the tree will
take a long time.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http
On Thursday, February 05, 2015 10:37:55 AM Konstantin Belousov wrote:
On Wed, Feb 04, 2015 at 10:15:04AM -0500, John Baldwin wrote:
On Tuesday, February 03, 2015 10:33:36 PM Konstantin Belousov wrote:
On Mon, Feb 02, 2015 at 09:50:22PM -0600, Eric Badger wrote:
On 02/02/2015 03:30 AM
On Thursday, February 05, 2015 04:22:23 PM Luigi Rizzo wrote:
On Thu, Feb 05, 2015 at 08:21:45AM -0500, John Baldwin wrote:
On Thursday, February 05, 2015 08:48:33 AM Luigi Rizzo wrote:
...
It is fixed (in the proper meaning of the word, not like worked
around,
covered
-specific
fields than just the path, KVME_TYPE_VNODE would be more correct.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr
a different
sized stack, so using the members in struct thread is probably what you
want to do regardless.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
device_t has a sysctl ctx you can get to hang new nodes off of the
device's node.)
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current
On Friday, January 30, 2015 04:45:45 PM Elizabeth Myers wrote:
On 01/30/15 09:17, John Baldwin wrote:
Humm. If the code is going to live in the drm driver, then I would
start with hanging a sysctl off of the drm device itself. (Each new-bus
device_t has a sysctl ctx you can get to hang
ones, etc.)
2) Shouldn't the 'newnmbclusters nmbclusters' check catch this already?
That should fail right? Might be worth figuring out why it isn't.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
idle threads created and working before APs are started as otherwise
they will have no thread to run initially. This is certainly a desired
feature, but it is not as simple as moving the sysinit up I'm afraid.
--
John Baldwin
___
freebsd-current
0x0800
#defineCPUID2_FMA 0x1000
#defineCPUID2_CX16 0x2000
#defineCPUID2_XTPR 0x4000
Yes, please include both. SDBG matches the label in the Intel SDM, so
that's the preferred name.
--
John Baldwin
+ if kldstat -qm nmdm; then
+ devargs=$devargs -l com2,/dev/nmdm${vmname}2B
+ fi
${FBSDRUN} -c ${cpus} -m ${memsize} ${apic_opt} -A -H -P\
-g ${gdbport} \
--
John Baldwin
On 1/6/15 10:55 AM, Ian Lepore wrote:
On Tue, 2015-01-06 at 09:37 -0500, John Baldwin wrote:
On 1/5/15 8:18 AM, Hans Petter Selasky wrote:
Hi,
There is a limitiation on the number of interrupt vectors available when
only a single processor is running. To have more interrupts available we
stats
output in it). I can't decide if it's worth committing... it'll have a
lot of value to someone with slow serial and netbooting, is that common?
9600 consoles are still fairly common, so if this makes a noticable difference
for NFS, by all means test it and get it in.
--
John Baldwin
, John Baldwin wrote:
On Friday, November 28, 2014 11:08:35 PM Julian Elischer wrote:
Do we need to compile all modules with witness definitions when
linking with a kernel compiled with witness?
This was true at one stage but I remember some work was done to make
them compatible.
You
always call functions in the kernel for
lock operations and this functions are what invoke WITNESS.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
have to move
the variable definitions to get the size change? I'd prefer to leave the
variable declarations where they are if possible (and just add 'int k' or
'size_t k' in the existing variable blocks).
--
John Baldwin
___
freebsd-current@freebsd.org
On Friday, November 21, 2014 08:39:17 PM Roman Divacky wrote:
Sure thing. Reload the patch from the same url.
http://rys.vlakno.cz/~rdivacky/boot2.diet.patch
Thanks. I haven't run tested it, but I'm ok with it otherwise.
--
John Baldwin
On Tuesday, November 11, 2014 4:22:05 pm Henry Hu wrote:
On Tue, Nov 11, 2014 at 1:33 PM, John Baldwin j...@freebsd.org wrote:
On Friday, October 31, 2014 4:08:06 pm Beeblebrox wrote:
First breakage in a long time. Error is:
In file included from cancelpoints_sem_new.c:47:
/usr
committed in the same commit as the changes to sys/umtx.h.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
in
the system along with counts of how many active / inactive pages each object
contains. For your case with lots of inactive memory, you probably want
something like 'vm_objects | sort -n -k 2'.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
:(
In practice, timezone changes are very rare, so rechecking the file is
quite expensive to do. I think having to restart processes is fine for this.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
On Tuesday, November 11, 2014 3:16:19 pm Charles Swiger wrote:
On Nov 11, 2014, at 10:57 AM, John Baldwin j...@freebsd.org wrote:
On Monday, November 10, 2014 7:36:19 am Lev Serebryakov wrote:
After changing timezones in Russia (with replacing /etc/localtime
with new file), I found
On Tuesday, October 28, 2014 7:07:31 pm Eitan Adler wrote:
On 28 October 2014 15:14, Baptiste Daroussin b...@freebsd.org wrote:
On Tue, Oct 28, 2014 at 09:35:26PM +0100, Marcus von Appen wrote:
Quoting John Baldwin j...@freebsd.org:
On Saturday, October 25, 2014 4:45:36 pm Mateusz
commits I've done to old were bugfixes that applied
to both old and new.
John has been the main fix the old NFS guy lately. So, John, do you
anticipate more patches to the old NFS that need to be MFC'd down?
I do not, no.
--
John Baldwin
fine.
Very strange...
Does anyone have a clue what is going on here?
So not loading the nvidia driver during boot fixed it? That seems odd indeed.
Did you recompile the driver after updating?
--
John Baldwin
___
freebsd-current@freebsd.org
to store metadata about the issue itself
(wikis are kind of poor for that).
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr
I thought you are the guy most likely to
need to do commits/MFCs to oldnfs.
I think it is fine to remove it from 11. I would do it sooner rather than
later.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
) at
subr_syscall.c:87
#24 0x80d33b0b in Xprot () at
/usr/src/sys/amd64/amd64/exception.S:324 #25 0x000806a7fe6a in ?? ()
##
The functions in this stack trace don't make sense. It is as if you are
running kgdb against the wrong kernel.
--
John
On Wednesday, October 08, 2014 8:23:54 pm Alfred Perlstein wrote:
On 10/8/14 11:53 AM, John Baldwin wrote:
This patch adds locking to scd(4) and marks it MPSAFE. It also uses bus_*()
instead of bus_space_*(). The patch is against HEAD but probably applies
to 9
and 10 as well
/si_bus_space.patch
If no one tests updates to this driver then it is not feasible to continue
maintaining it in the tree. In that case, it will be removed from HEAD one
month from today.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http
that will be removed in 11.
If no one tests updates to this driver then it is not feasible to continue
maintaining it in the tree. In that case, it will be removed from HEAD one
month from today.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http
,
- sizeof(struct timeval));
+ qstate-timeout =
+ qstate-config_entry-common_query_timeout;
} else
read_response-error_code = -1;
--
John Baldwin
___
freebsd
On Friday, October 03, 2014 12:13:28 PM Gleb Smirnoff wrote:
On Thu, Oct 02, 2014 at 11:16:27AM -0400, John Baldwin wrote:
J I haven't looked at the rest of the driver; is everything else around
J OACTIVE locked correctly and consistently?
J
J As well as OACTIVE is for any other driver
On Wednesday, October 01, 2014 2:58:38 pm Adrian Chadd wrote:
Hi,
On 1 October 2014 07:14, John Baldwin j...@freebsd.org wrote:
This small patch correctly sets OACTIVE when an(4) gets backed up. Right
now
I believe it will never set the flag. It is only an optimization, it
should
On Thursday, October 02, 2014 1:24:22 pm Adrian Chadd wrote:
On 2 October 2014 08:16, John Baldwin j...@freebsd.org wrote:
On Wednesday, October 01, 2014 2:58:38 pm Adrian Chadd wrote:
Hi,
On 1 October 2014 07:14, John Baldwin j...@freebsd.org wrote:
This small patch correctly sets
-an_rdata.an_tx_prod = idx;
+ }
- sc-an_rdata.an_tx_prod = idx;
-
return;
}
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current
On Monday, September 15, 2014 11:25:47 AM John Baldwin wrote:
On Saturday, September 13, 2014 10:57:53 AM d...@gmx.com wrote:
John Baldwin wrote on 09/12/2014 23:06:
X loaded i915kms automatically and
i915 and i915kms do not get along. i915 had already allocated the IRQ
when i915kms
On Thursday, September 25, 2014 11:15:51 am TAKAHASHI Yoshihiro wrote:
In article 2960329.sjarrui...@ralph.baldwin.cx
John Baldwin j...@freebsd.org writes:
I have three patches to convert various pc98 drivers from timeout() to
callout(). For the fdc driver I took a more drastic approach
On Wednesday, September 24, 2014 7:33:46 pm Marcel Moolenaar wrote:
On Sep 24, 2014, at 12:54 PM, John Baldwin j...@freebsd.org wrote:
On Tuesday, September 23, 2014 09:29:48 AM Marcel Moolenaar wrote:
What is going on here?
Are we still in some kind of flux and people aren't done yet
This patch adds locking to wds(4) and marks it MPSAFE. It also includes
several other cleanups such as using bus_space instead of inb/outb. The patch
is against HEAD but probably applies to 9 and 10 as well.
http://people.freebsd.org/~jhb/patches/ncr_locking.patch
--
John Baldwin
change to what I recently comitted to atkbd:
http://people.FreeBSD.org/~jhb/patches/pckbd_callout.patch
For the olpt driver, I just did a simple conversion:
http://people.FreeBSD.org/~jhb/patches/olpt_callout.patch
These patches are against HEAD but likely apply to 9 and 10 as well.
--
John
This patch converts a few timers in isp(4) from timeout(9) to callout(9). It
already used callout(9) for normal command timeouts. The patch is against
HEAD but probably applies to 9 and 10 as well.
http://people.freebsd.org/~jhb/patches/isp_callout.patch
--
John Baldwin
:/usr/obj/sparc64.sparc64/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
$ which cc
/usr/obj/sparc64.sparc64/usr/src/tmp/usr/bin/cc
$ which cat
/bin/cat
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
()
purging.)
Warner
On Sep 19, 2014, at 2:07 PM, John Baldwin j...@freebsd.org wrote:
This patch fixes various issues in wl(4) including:
- Use bus_space instead of inb/outb.
- Use device_printf() and if_printf()
- Use callout(9) instead of timeout(9)
- Don't hold the driver lock
On Sunday, September 21, 2014 09:36:25 PM Justin T. Gibbs wrote:
On Sep 20, 2014, at 11:06 AM, Konstantin Belousov kostik...@gmail.com
wrote:
On Fri, Sep 19, 2014 at 03:27:25PM -0400, John Baldwin wrote:
I suspect it was done out of reasons of being overly conservative in
interpreting
On Monday, September 22, 2014 12:42:34 PM Adrian Chadd wrote:
On 22 September 2014 12:20, John Baldwin j...@freebsd.org wrote:
On Friday, September 19, 2014 03:47:16 PM Warner Losh wrote:
I got rid of my pre-802.11 WaveLAN cards about 8 years go after not
having
them in a system at all
This patch adds locking to spic(4) and marks it MPSAFE. The patch
is against HEAD but probably applies to 9 and 10 as well.
http://people.freebsd.org/~jhb/patches/spic_locking.patch
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http
This patch adds locking to the scsi_low subsystem and the drivers that use it:
ct(4), ncv(4), nsp(4), and stg(4). The drivers are all marked MPSAFE. The
patch is against HEAD but probably applies to 9 and 10 as well.
http://people.freebsd.org/~jhb/patches/scsi_low_locking.patch
--
John
lock.
The patch is against HEAD but probably applies to 9 and 10 as well.
http://people.freebsd.org/~jhb/patches/wl_cleanup.patch
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
This patch converts the netgraph bluetooth codee from timeout(9) to
callout(9). The patch is against HEAD but probably applies to 9 and 10 as
well.
http://people.freebsd.org/~jhb/patches/bluetooth_callout.patch
--
John Baldwin
___
freebsd-current
/si_bus_space.patch
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
This patch adds locking to scd(4) and marks it MPSAFE. It also uses bus_*()
instead of bus_space_*(). The patch is against HEAD but probably applies to 9
and 10 as well.
http://people.freebsd.org/~jhb/patches/scd_locking.patch
--
John Baldwin
://people.freebsd.org/~jhb/patches/tws_callout.patch
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
global lookup
tables in the driver. The patch is against HEAD but probably applies to 9 and
10 as well.
http://people.freebsd.org/~jhb/patches/rp_callout.patch
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
This patch adds locking to wds(4) and marks it MPSAFE. It also includes
several other cleanups such as using bus_space instead of inb/outb. The patch
is against HEAD but probably applies to 9 and 10 as well.
http://people.freebsd.org/~jhb/patches/wds_locking.patch
--
John Baldwin
suspect it was done out of reasons of being overly conservative in
interpreting RLIMIT_STACK. I think it is quite surprising behavior though and
would rather we make your option the default and implement what the Open Group
says above.
--
John Baldwin
/patches/mse_locking.patch
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
On Saturday, September 13, 2014 10:57:53 AM d...@gmx.com wrote:
John Baldwin wrote on 09/12/2014 23:06:
X loaded i915kms automatically and
i915 and i915kms do not get along. i915 had already allocated the IRQ
when i915kms tried to alloc the same IRQ causing the issue.
Who is to blame
On Friday, September 12, 2014 10:03:26 PM Marcin Cieslak wrote:
On Fri, 12 Sep 2014, John Baldwin wrote:
Please note I originally loaded i915.ko, not i915kms.ko
Oh, that is probably your problem. X loaded i915kms automatically and
i915 and i915kms do not get along. i915 had already
will not include checking for driver misbehavior
in its interfacing with those subsystems, so I would generally recommend just
enabling INVARIANTS globally.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
On Friday, September 12, 2014 05:45:31 PM Marcin Cieslak wrote:
On Wed, 10 Sep 2014, John Baldwin wrote:
On Wednesday, September 10, 2014 12:45:08 PM Marcin Cieslak wrote:
On my CURRENT as of 6 Sep (r271197):
What I did was that:
- kldload i915
- startx
During X server
On Friday, September 12, 2014 08:57:55 PM Marcin Cieslak wrote:
On Fri, 12 Sep 2014, John Baldwin wrote:
at /usr/src/sys/dev/pci/vga_pci.c:318
318return (bus_alloc_resource(dev, type, rid, start, end,
count,
flags));
Current language: auto; currently
, regarding the earlier thread about this, I think instead of hacking
up the EFI headers, we should use the stock headers and adjust our code to use
whatever naming contentions (CamelCase, etc.) those use. This is what we do
with ACPICA for example.
--
John Baldwin
out, count=18446744071580876744, flags=value
optimized out) at /usr/src/sys/dev/pci/vga_pci.c:318
Can you load the core dump in kgdb and run 'f 13' and 'p *rid'?
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org
of the
more advanced ddb commands like 'show lockedvnodes' using gdb scripts against
a minidump (see 'lockedvnodes' command in www.freebsd.org/~jhb/gdb/gdb6).
In short, minidumps still provide far more information and can almost completely
replicate the functionality of textdumps.
--
John Baldwin
On Friday, September 05, 2014 5:08:07 pm Peter Wemm wrote:
On Friday 05 September 2014 13:51:24 Craig Rodrigues wrote:
On Fri, Sep 5, 2014 at 7:54 AM, John Baldwin j...@freebsd.org wrote:
Probably at least 50% of the time when I work with a user on a bug report,
I ask them to go into kgdb
that have run */
s/interpretes/interpreters/
Other than that I think this is fine, though I wonder if it will result
in some unexpected effects (you probably want to be able to use a binmisc
binary as the #! interpreter for a script, but I'm not sure the opposite
is true.
--
John Baldwin
On Tuesday, August 26, 2014 11:05:12 am Alan Somers wrote:
On Mon, Aug 25, 2014 at 1:52 PM, John Baldwin j...@freebsd.org wrote:
On Friday, August 22, 2014 01:34:28 PM Harald Schmalzbauer wrote:
Bezüglich Yuri's Nachricht vom 02.09.2013 06:54 (localtime):
Please check in this patch
On Tuesday, August 26, 2014 2:23:12 am Poul-Henning Kamp wrote:
In message 2945485.zemf81r...@ralph.baldwin.cx, John Baldwin writes:
On Saturday, August 23, 2014 10:16:42 AM Poul-Henning Kamp wrote:
In message 20140820215522.ga92...@bewilderbeast.blackhelicopters.org
not just statically create the pairs in /dev? Use some loader tunable
(kern.ptymax) to set a count on the number of pre-created device pairs to
create and then just explicitly create them in the mod_event handler? It
could default to 100 or so.
--
John Baldwin
expand on this? I.e. what should the code do if it is fixed?
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
.
The following trace points are supported:
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Hello,
I guess this fix should make it into 10.1.
Can someone check please?
A fix has to make into HEAD first. I've cc'd Alan who responded to the bug.
Alan, note that glebius@ already committed the test case to HEAD a while ago.
--
John Baldwin
On Tuesday, August 12, 2014 5:36:26 pm Adrian Chadd wrote:
On 12 August 2014 11:09, John Baldwin j...@freebsd.org wrote:
On Wednesday, July 16, 2014 1:52:45 pm Adrian Chadd wrote:
Hi!
On 16 July 2014 06:29, Konstantin Belousov kostik...@gmail.com wrote:
On Fri, Jun 27, 2014 at 03:56
On Wednesday, August 13, 2014 1:00:22 pm Alan Cox wrote:
On Tue, Aug 12, 2014 at 1:09 PM, John Baldwin j...@freebsd.org wrote:
On Wednesday, July 16, 2014 1:52:45 pm Adrian Chadd wrote:
Hi!
On 16 July 2014 06:29, Konstantin Belousov kostik...@gmail.com wrote:
On Fri, Jun 27
This patch adds locking to mcd(4) and marks it MPSAFE. This patch is against
HEAD but probably applies to 9 and 10 as well. Please enable INVARIANTS while
testing.
http://www.FreeBSD.org/~jhb/patches/mcd_locking.patch
--
John Baldwin
___
freebsd
This patch converts the ips(4) driver to the callout(9) API and adds
additional locking to remove its use of Giant. The patch is against HEAD but
probably applies to 9 and 10 as well. Please test with INVARIANTS enabled.
http://www.FreeBSD.org/~jhb/patches/ips_callout.patch
--
John Baldwin
This patch switches the ofw_console driver from timeout(9) to callout(9). The
patch is against HEAD but it probably applies to 9 and 10. Please test with
INVARIANTS enabled.
http://www.FreeBSD.org/~jhb/patches/ofw_console_callout.patch
--
John Baldwin
This patch fixes various issues in the iir(4) driver and adds locking to make
it MPSAFE. The patch is against HEAD though I expect it probably applies to
9 and 10 as well. Please test with INVARIANTS enabled.
http://www.FreeBSD.org/~jhb/patches/iir_locking.patch
--
John Baldwin
This patch adds locking to mly(4) and marks it MPSAFE. This patch is against
HEAD but probably applies to 9 and 10 as well. Please enable INVARIANTS while
testing.
http://www.FreeBSD.org/~jhb/patches/mly_locking.patch
--
John Baldwin
___
freebsd
This patch switches the pst(4) driver from timeout(9) to callout(9). It also
cleans up detach a bit. The patch is against HEAD but probably applies to 9
and 10. Please test with INVARIANTS enabled.
http://www.FreeBSD.org/~jhb/patches/pst_callout.patch
--
John Baldwin
since all pages
are dirtied. (I have a local hack that adds a new malloc option to explicitly
memset() new pages allocated via mmap() that gives the same benefit without
the junking overheadon each malloc() / free(), but it does increase physical
RAM usage.)
--
John Baldwin
by the optimisers and so the
warnings are dependent on optimisation level.
David
Hi,
Is someone working on this?
If not, at least add a PR so it is harder to drop?
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http
, it may be relevant to point out that the machine
where I see the panic is a Dell Precision M4400 laptop.
My guess is that the recent Xen changes tickled something. However, can you
capture a verbose dmesg from your working kernel?
--
John Baldwin
On Aug 5, 2014, at 2:29 PM, Michael Butler i...@protected-networks.net wrote:
On 08/05/14 16:56, Michael Butler wrote:
On 08/05/14 16:02, John Baldwin wrote:
My guess is that the recent Xen changes tickled something.
I can confirm this on a kernel which is otherwise up to date
not-booting thing that caused.
512k should be fine even if it is a bit excessive. Also, larger partitions
might actually increase boot time, but perhaps not noticably.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
, resizing the freebsd-boot to 128k solved my issue. why default
slice size making such issue?
Good question. Perhaps Nathan (cc'd) knows?
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
ignore a size of zero back from EDD).
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
;
}
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http
buildworld instead.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
.
The uncommitted patches, referenced in the article, are available as
https://kib.kiev.ua/kib/pig1.patch.txt
https://kib.kiev.ua/kib/patch-2
Did you run the same benchmark on the same hardware with any other OS's to
compare results?
--
John Baldwin
);
}
sysctl_handle_table() would use the initial value to find a suitable string
from the table for the old string, etc. Using void * for the value would
let you store arbitrary data, etc.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
submit a bug report for this and cc it to j...@freebsd.org. The
vlanhwtag stuff should work properly.
--
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
On Monday, June 23, 2014 9:06:26 pm John-Mark Gurney wrote:
John Baldwin wrote this message on Mon, Jun 23, 2014 at 10:49 -0400:
On Monday, June 23, 2014 9:44:08 am John-Mark Gurney wrote:
So, when I try to eject a ESATA card, the machine panics... I am able
to successfully eject other
401 - 500 of 2772 matches
Mail list logo
