On 29 January 2010 09:16, pluknet wrote:
> On 29 January 2010 01:24, Andrew Thompson wrote:
>> Author: thompsa
>> Date: Thu Jan 28 22:24:54 2010
>> New Revision: 203134
>> URL: http://svn.freebsd.org/changeset/base/203134
>>
>> Log:
>> Add run(4), a
MAXCPU 32
(almost 2y ago for x86)
--
wbr,
pluknet
___
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"
race
> /usr/sbin/lockstat
>
> What did I do wrong that resulted in these 2
> programs still linked against the old version
> of libz?
>
Hi, Anton.
After r210693, these utilities are built for i386 and amd64 only.
Thereby you have stale binaries installed f
SD/SMP: Multiprocessor System Detected: 3 CPUs
FreeBSD/SMP: 1 package(s) x 3 core(s)
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 2
cpu2 (AP): APIC ID: 4
--
wbr,
pluknet
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailma
On 27 August 2010 00:09, Doug Barton wrote:
> On 08/26/2010 12:53 PM, pluknet wrote:
>>
>> [cc'ing current@ as rc@ looks too quite]
>>
>> Hi.
>>
>> Since ifconfig has grown to label interfaces with
>> ifconfig $ifname description "fooba
On 27 August 2010 01:09, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 2010/08/26 13:09, Doug Barton wrote:
>> On 08/26/2010 12:53 PM, pluknet wrote:
>>> [cc'ing current@ as rc@ looks too quite]
>>>
>>> Hi.
>>
2" # Label fxp0 interface
#vlans_fxp0="101 vlan0"# vlan(4) interfaces for fxp0 device
#create_arg_vlan0="vlan 102" # vlan tag for vlan0 device
#wlans_ath0="wlan0"# wlan(4) interfaces for ath0 device
%%%
--
wbr,
pluknet
Index: etc
On 19 August 2010 17:34, John Baldwin wrote:
> On Thursday, August 19, 2010 5:29:25 am pluknet wrote:
>> On 19 August 2010 00:07, John Baldwin wrote:
>> > On Wednesday, August 18, 2010 3:17:56 pm pluknet wrote:
>> >> On 18 August 2010 23:11, pluknet wrote:
&
On 19 August 2010 04:04, Rick Macklem wrote:
>> On 18 August 2010 12:07, pluknet wrote:
>> > On 17 August 2010 20:04, Kostik Belousov wrote:
>> >
>> >>
>> >> Also please take a note of the John' suggestion to use the taskqueue.
>> >
On 19 August 2010 00:07, John Baldwin wrote:
> On Wednesday, August 18, 2010 3:17:56 pm pluknet wrote:
>> On 18 August 2010 23:11, pluknet wrote:
>> > On 18 August 2010 17:46, Kostik Belousov wrote:
>> >> On Wed, Aug 18, 2010 at 02:43:19PM +0400, pluknet wrote:
On 18 August 2010 23:11, pluknet wrote:
> On 18 August 2010 17:46, Kostik Belousov wrote:
>> On Wed, Aug 18, 2010 at 02:43:19PM +0400, pluknet wrote:
>>> On 18 August 2010 12:07, pluknet wrote:
>>> > On 17 August 2010 20:04, Kostik Belousov wrote:
>>> >
On 18 August 2010 17:46, Kostik Belousov wrote:
> On Wed, Aug 18, 2010 at 02:43:19PM +0400, pluknet wrote:
>> On 18 August 2010 12:07, pluknet wrote:
>> > On 17 August 2010 20:04, Kostik Belousov wrote:
>> >
>> >>
>> >> Also please take
On 18 August 2010 12:07, pluknet wrote:
> On 17 August 2010 20:04, Kostik Belousov wrote:
>
>>
>> Also please take a note of the John' suggestion to use the taskqueue.
>
> I decided to go this road. Thank you both.
> Now I do nfs buildkernel survive and prepare
On 17 August 2010 20:04, Kostik Belousov wrote:
> On Tue, Aug 17, 2010 at 07:42:41PM +0400, pluknet wrote:
>> 2010/8/16 Kostik Belousov :
>> > On Mon, Aug 16, 2010 at 09:07:24PM +0400, pluknet wrote:
>> >> On 16 August 2010 21:05, pluknet wrote:
>> >> &
2010/8/16 Kostik Belousov :
> On Mon, Aug 16, 2010 at 09:07:24PM +0400, pluknet wrote:
>> On 16 August 2010 21:05, pluknet wrote:
>> > Hi.
>> >
>> > Seeing on mostly idle, recently updated current, while closing a file.
>> > Presumably never report
On 16 August 2010 21:05, pluknet wrote:
> Hi.
>
> Seeing on mostly idle, recently updated current, while closing a file.
> Presumably never reported on ML.
>
> lock order reversal:
> 1st 0xff00198199f8 nfs (nfs) @ /usr/src/sys/kern/vfs_vnops.c:301
> 2nd 0xff00023
---
--
wbr,
pluknet
___
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"
, won't
>> > you? And then BSD grep will process the input and print out matches. I
>> > don't think it's bad behaviour in itself but if you can explain why you
>> > think it's bad I'm willing to change it.
>> >
>> I am not sure
re is a diff I'd like someone look into and check in if there will
no objections.
--
wbr,
pluknet
ws_kern.diff
Description: Binary data
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To u
}
The precondition idea to reproduce it is to lock a subject thread
in some deadlkres callout, handle re-wrap condition, then try
to lock a process to witch the thread belongs in (n+m)'th deadlkres
callout, or in different context.
--
wbr,
pluknet
___
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"
ther_demux+0x17d
ether_input() at ether_input+0x175
em_rxeof() at em_rxeof+0x193
em_handle_que() at em_handle_que+0x4a
taskqueue_run() at taskqueue_run+0x91
taskqueue_thread_loop() at taskqueue_thread_loop+0x3f
fork_exit() at fork_exit+0x12a
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp
(Only if having a USV of course)
>
> Dunno if there is a mfiutil equivalent though.
Hi.
That would be:
mfiutil cache mfid0 enable
mfiutil cache mfid0 read-ahead none
mfiutil cache mfid0 write-back
mfiutil cache mfid0 write-cache enable
--
wbr,
pluknet
_
fix some problems.
>
> DragonFlyBSD and NetBSD use newer GCC?
> This is the first time I hear about that.
> No doubt about major Linux distributions, though.
>
AFAIK, NetBSD does it for quite a while since they have a different pov on this.
http://www.thejemreport.com/content/view/317
> -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow
> -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror vers.c
> linking kernel.debug
> mca.o(.text+0x1627): In function `mca_init':
> /src/sys/i386/i386/mca.c:786: undefined reference to `lapic_enable_cmc'
> *** Error code 1
>
> Stop in /obj/pc98/src/sys/GENERIC.
Just wonder why apic is still commented out in pc98's GENERIC.
Is there a reason to keep things intact?
It was inherited from i386 port in time when it was commented out.
--
wbr,
pluknet
___
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"
nd executed test.c as below on amd64.
>
[...]
>
> % gcc -m32 -B/usr/lib32 test.c
> % ./a.out
> mmap: Invalid argument
AFAIK, it still doesn't work on FreeBSD. You need something like 32bit
chroot environment.
There's also about:
http://www.freebsd.org/proje
On 1 May 2010 19:03, Marius Strobl wrote:
> On Fri, Apr 30, 2010 at 06:50:26PM +0400, pluknet wrote:
>> On 30 April 2010 18:22, Matthew Jacob wrote:
>> > pluknet wrote:
>> > Seems good to me- why not trhow it freebsd-scsi? if nobody says no, I'll
>> >
On 30 April 2010 18:22, Matthew Jacob wrote:
> pluknet wrote:
> Seems good to me- why not trhow it freebsd-scsi? if nobody says no, I'll put
> it in
Err.. I thought that list is dedicated for cam related stuff.
[cc'ing scsi@ for better coverage. Sorry for cross-posting :/ ]
et a coredump or minidump.
>
> Thanks,
> Jeff
--
wbr,
pluknet
___
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"
MPI_EVENT_SAS_DEVICE_STATUS_CHANGE:
Another way - just hide such event since mptutil displays rebuild progress.
--
wbr,
pluknet
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send an
On 27 April 2010 10:01, Jeff Roberson wrote:
> On Mon, 26 Apr 2010, pluknet wrote:
>
>> On 26 April 2010 17:42, dikshie wrote:
>>>
>>> Hi Jeff,
>>> thanks for SUJ.
>>> btw, why there is nan% utilization? and what does it mean?
>>> ---
jblocks are not updated.
/* Next ensure that segments are ordered properly. */
seg = TAILQ_FIRST(&allsegs);
if (seg == NULL) {
if (debug)
printf("Empty journal\n");
return;
}
--
wbr,
pluknet
___
but this didn't help.
> Can you explain what you did to boot FreeBSD faster?
>
Hmm.. That's strange to hear.
We have in production a number of x3650m2: 7.2-R, 7.3-R (all amd64).
All runs flawlessly.
I'll try to boot it from head today if that matters.
--
wbr,
plukn
431:be rebuilt or panics may be experienced.
432:Bump __FreeBSD_version to 800081.
If you have 3th-party modules from FreeBSD 7, it's time to rebuild them.
--
wbr,
pluknet
___
freebsd-current@freebsd.org maili
On 15 April 2010 17:41, Nathan Whitehorn wrote:
> On 04/15/10 08:13, John Baldwin wrote:
>>
>> On Thursday 15 April 2010 6:06:24 am pluknet wrote:
>>
>>>
>>> On 7 April 2010 23:49, John Baldwin wrote:
>>>
>>>>
>
On 7 April 2010 23:49, John Baldwin wrote:
> On Tuesday 06 April 2010 11:24:21 am Nathan Whitehorn wrote:
>> pluknet wrote:
>> > Hi,
>> >
>> > the interesting part for me is how to properly assert now a value of e.g.
>> > KINFO_PROC_SIZE varyi
ING
and/or errata as (as far as I know) that brakes "newer kernel usually works with
older world" users expectation.
20100119:
PIE support has been improved. Kernel maps PIE binaries at non-zero
base address. Users need to rebuild rtld(1) to hook up with a new
kernel.
Hi,
the interesting part for me is how to properly assert now a value of e.g.
KINFO_PROC_SIZE varying on err.. different COMPAT_FREEBSD32 arches
(say, FreeBSD would have _kern_proc FreeBSD32 compat layer for top/ps/).
--
wbr,
pluknet
___
freebsd
-
>
> actually "samba-3.4.5.tar.gz" does exist under /usr/ports/distfiles
>
Looks like you have partially fetched distfile. Try to make distclean,
then restart again.
--
wbr,
pluknet
___
oll_handler_t em_poll;
+static poll_handler_t lem_poll;
#endif /* POLLING */
/*****
--
wbr,
pluknet
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/
39 matches
Mail list logo
