on 20/12/2012 00:34 Kimmo Paasiala said the following:
What is the status of the MFC process to 9-STABLE? I'm on 9-STABLE
r244407, should I be able to boot from this ZFS pool without
zpool.cache?
I haven't MFC-ed the change as of now.
After I eventually MFC it you should be able to boot from
On 23 December 2012 10:22, Ian Smith smi...@nimnet.asn.au wrote:
On Sun, 23 Dec 2012 03:45:39 +0300, Sergey Kandaurov wrote:
This (i.e. the kmem_map too small message seen with kernel memory
shortage) could be due to CAM CTL ('device ctl' added in 9.1), which is
quite a big kernel memory
I have MFCed the following change, so please double-check if you might be
affected. Preferably before upgrading :-)
on 28/11/2012 20:35 Andriy Gapon said the following:
Recently some changes were made to how a root pool is opened for root
filesystem
mounting. Previously the root pool had
On Sun, Dec 23, 2012 at 2:28 PM, Andriy Gapon a...@freebsd.org wrote:
I have MFCed the following change, so please double-check if you might be
affected. Preferably before upgrading :-)
on 28/11/2012 20:35 Andriy Gapon said the following:
Recently some changes were made to how a root pool
On 23 Dec 2012 06:40, Adrian Chadd adr...@freebsd.org wrote:
Hi guys,
Would someone please file a PR for this? This is a huge unused
allocation of memory for something that honestly likely shouldn't have
been included by default in GENERIC.
I've cc'ed ken on a reply to this. Hopefully
on 23/12/2012 14:34 Kimmo Paasiala said the following:
On Sun, Dec 23, 2012 at 2:28 PM, Andriy Gapon a...@freebsd.org wrote:
I have MFCed the following change, so please double-check if you might be
affected. Preferably before upgrading :-)
on 28/11/2012 20:35 Andriy Gapon said the
On 12/23/2012 01:35 PM, Chris Rees wrote:
On 23 Dec 2012 06:40, Adrian Chadd adr...@freebsd.org
mailto:adr...@freebsd.org wrote:
Hi guys,
Would someone please file a PR for this? This is a huge unused
allocation of memory for something that honestly likely shouldn't have
been
TB --- 2012-12-23 14:31:53 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2012-12-23 14:31:53 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE
FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-12-23
TB --- 2012-12-23 14:31:53 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2012-12-23 14:31:53 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE
FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-12-23
TB --- 2012-12-23 14:31:53 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2012-12-23 14:31:53 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE
FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-12-23
TB --- 2012-12-23 14:31:53 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2012-12-23 14:31:53 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE
FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-12-23
On 23.12.2012 03:05, Charlie Root wrote:
Checking negative group permissions:
8903027 -rw--w-r-- 1 miwww794277 Oct 23 07:47:45 2007
/home/mi/public_html/syb/order/download.log
Hello!
The above started to appear in the daily security run output after I
upgraded to 9.1. I don't
TB --- 2012-12-23 15:35:42 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2012-12-23 15:35:42 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE
FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-12-23
The r for other means that you have not accomplished your goal. It makes
no sense to have group with less permission that other, so the script is
warning of a misconfiguration.
On Sun, Dec 23, 2012 at 10:51:24AM -0500, Mikhail T. wrote:
On 23.12.2012 03:05, Charlie Root wrote:
Checking
On 23 December 2012 16:23, Barney Wolff bar...@databus.com wrote:
[moving Barney's top post down]
On Sun, Dec 23, 2012 at 10:51:24AM -0500, Mikhail T. wrote:
On 23.12.2012 03:05, Charlie Root wrote:
Checking negative group permissions:
8903027 -rw--w-r-- 1 miwww794277 Oct 23
On Sun, 23 Dec 2012 15:21:23 +0300, Sergey Kandaurov wrote:
On 23 December 2012 10:22, Ian Smith smi...@nimnet.asn.au wrote:
On Sun, 23 Dec 2012 03:45:39 +0300, Sergey Kandaurov wrote:
This (i.e. the kmem_map too small message seen with kernel memory
shortage) could be due to CAM
Greetings.
All I have to do to panic it is boot it. As you can see from the dump, it died
after about 30 seconds without me doing anything. I can't provide those sysctl
values easily, as it panics too quickly. I suppose I can convince it to drop to
DDB and pick them out if that would be
TB --- 2012-12-23 18:07:42 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2012-12-23 18:07:42 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE
FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-12-23
TB --- 2012-12-23 18:07:42 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2012-12-23 18:07:42 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE
FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-12-23
TB --- 2012-12-23 18:07:42 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2012-12-23 18:07:42 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE
FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-12-23
TB --- 2012-12-23 19:14:34 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2012-12-23 19:14:34 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE
FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-12-23
Hey,
The GNATS database can now be mirrored using rsync from:
rsync://bit0.us-west.freebsd.org/FreeBSD-bit/gnats/
I expect that URL to be permanent, at least while GNATS is still
alive. At a later point there will be more mirrors (a us-east will be
the first) and I will find a place to
Please help, I reported this issue on
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/174372 but the crashes
are unbearable since they happen regularly at night, most of the time
when periodic.daily is called (3am) but there are exceptions. It seems
like it can be triggered by any heavy disk
On Sat, Dec 22, 2012 at 7:49 PM, Łukasz Wąsikowski
luk...@wasikowski.net wrote:
W dniu 2012-12-22 18:14, Ben Morrow pisze:
Quoth =?UTF-8?B?xYF1a2FzeiBXxIVzaWtvd3NraQ==?= luk...@wasikowski.net:
W dniu 2012-12-22 04:41, Kimmo Paasiala pisze:
Yeah, this is problem in network.subr. An interface
Ok, I'll see about disabling it in GENERIC and STABLE/9 for now, at
least until Ken has some idea of what's going on.
Thanks,
Adrian
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe,
.. has someone filed a PR for it?
Adrian
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
The reason it grabs RAM up front is that it was written for an embedded
platform where memory allocations might fail later on after things had been
running and memory got fragmented.
At this point, no, it doesn't need to allocate all of its memory up front.
I actually need to put some effort
27 matches
Mail list logo
