carry less than a 10% risk of a panic.
>
> Unless somebody fixes the fdc driver to work in -current, I intend
> to dust of my axe and cut it from the tree later this spring.
Is this an overreaction or just a wrong kind of reaction? :-)
--
Andriy Gapon
_
on 10/02/2013 17:44 Pawel Jakub Dawidek said the following:
> On Sun, Feb 10, 2013 at 09:50:58AM +0200, Andriy Gapon wrote:
>> on 10/02/2013 01:35 Pawel Jakub Dawidek said the following:
>>> geli(8) almost exclusively deals with sensitive data. Even mlocking
>>> MAXP
than 128kB, so there shouldn't be any
> issue with this.
I think that PAGE_SIZE (or at most a small multiple of it) should be sufficient.
I don't think that we currently have (or expect to see in the near future)
algorithms where keys with more than 4096 size provide any additional security
r from malloc(), print
> some useful message and prevent segfault.
I'd rather do what Kostik suggested and Fabian mentioned: instead of
mlockall(MCL_FUTURE) the code should mlock only the (explicitly designated)
buffers that can contain sensitive data.
--
Andriy Gapon
___
ess of
memorylocked. OTOH, we have kern.maxprocperuid.
--
Andriy Gapon
___
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"
geli a bit painful, this should work
> out of the box.
I have some, IMO, better suggestions:
- use -c option with sudo
- tune your system for your needs
- [major] abolish the silliness of tying resource limits to login class and
apply
resource limits based on user and group
nough with the patch to commit it, you are more than welcome to do so.
>
> Thanks everyone for your help in resolving this, rick
Committed. Thank you very much!
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.
cpuset_t map)
{
+ mtx_assert(&smp_ipi_mtx, MA_OWNED);
return (generic_stop_cpus(map, IPI_SUSPEND));
}
#endif
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubs
ze=4096 st_blocks=3
> st_flags=0
Hmm, this looks more consistent with the earlier patch.
Are you sure that you really tested the new kernel (on the server)?
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailma
ET is mostly used by filesystem drivers internally.
And ZFS doesn't seem to do that.
The only external user appears to be NFS.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-cu
on 07/02/2013 04:13 Rick Macklem said the following:
> Andriy Gapon wrote:
>> on 06/02/2013 17:15 Rick Macklem said the following:
>>> Well, zfs_vget() returns EOPNOTSUPP for .zfs, so the NFS server
>>> knows to
>>> switch over to using VOP_LOOKUP(). If the .zf
, right, but again this is done only for .zfs and .zfs/snapshot.
.zfs/shares is not special-cased and thus is problematic here too in the same
fashion as zfs_fhtovp.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd
shares vnode in that case
(instead of a regular zfs vnode).
Additionally, I am not sure, but perhaps zfs_vget() should do the same kind of
tricks as zfs_fhtovp.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/
vc_program() at nfssvc_program+0x482/frame 0xff848e6c0a00
> svc_run_internal() at svc_run_internal+0x1e9/frame 0xff848e6c0ba0
> svc_thread_start() at svc_thread_start+0xb/frame 0xff848e6c0bb0
> fork_exit() at fork_exit+0x84/frame 0xff848e6c0bf0
> fork_trampoline()
efinecpu_setstack(td, ap)((td)->td_frame->tf_rsp = (ap))
#definecpu_spinwait() ia32_pause()
--
Andriy Gapon
___
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"
n't seem likely, but???
>
> Maybe Sergey could try the change to line#1451 and see if the panic
> still happens. If not, that would suggest possibility #1, I think.
If the kernel is configured with witness, then it should be easy to check where
the exclusive lock was taken (file a
on 02/02/2013 16:50 Konstantin Belousov said the following:
> On Sat, Feb 02, 2013 at 01:50:40PM +0200, Andriy Gapon wrote:
>>
>> I would like to propose the following mostly cosmetic change:
>> http://people.freebsd.org/~avg/scheduler-swapper.diff
>>
>> This is
SI_SUB_RUN_SCHEDULER:SI_ORDER_LAST is a "hidden gem".
--
Andriy Gapon
___
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"
I plan to write a larger response to your complete followup.
Thank you.
--
Andriy Gapon
___
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"
= 0x7fffd488, rbp = 0x7fffd730
> ---
>
> db> show lockedvnods
> Locked vnodes
>
> 0xfe02e21b11d8: tag zfs, type VDIR
> usecount 4, writecount 0, refcount 4 mountedhere 0
> flags (VI_ACTIVE)
> v_object 0xfe02d9f2eb40 ref 0 pages 0
>
on 28/01/2013 15:24 Pawel Jakub Dawidek said the following:
> On Mon, Jan 28, 2013 at 03:07:59PM +0200, Andriy Gapon wrote:
>> on 28/01/2013 14:45 Pawel Jakub Dawidek said the following:
>>> FYI, it doesn't change anything for me. Resume seems to work, but
>>&
on 28/01/2013 14:45 Pawel Jakub Dawidek said the following:
> FYI, it doesn't change anything for me. Resume seems to work, but
> suspend just reset my laptop.
Sorry, I am a little confused by this description.
How can you know that resume works if suspend resets the machine?
--
A
on 28/01/2013 04:52 Glen Barber said the following:
> On Fri, Jan 25, 2013 at 10:43:33AM +0200, Andriy Gapon wrote:
>>
>> If you have ACPI suspend/resume working, if it used to work but stopped
>> working
>> at some time, if it never worked, but you are still hoping, c
on 25/01/2013 18:08 Andriy Gapon said the following:
> on 25/01/2013 15:51 John Baldwin said the following:
>> On Friday, January 25, 2013 3:43:33 am Andriy Gapon wrote:
>>>
>>> If you have ACPI suspend/resume working, if it used to work but stopped
>>> w
this issue.
I've just tried a plug the ZFS hole for now.
commit ed8b18f2d6c4d1be915bff94cdec0c51a479529f
Author: Andriy Gapon
Date: Wed Dec 19 23:29:23 2012 +0200
[bugfix] zfs: add MODULE_VERSION for zfsctrl
This should allow the kernel linker to easily detect a situation
whe
on 25/01/2013 15:51 John Baldwin said the following:
> On Friday, January 25, 2013 3:43:33 am Andriy Gapon wrote:
>>
>> If you have ACPI suspend/resume working, if it used to work but stopped
>> working
>> at some time, if it never worked, but you are still hoping, c
>
> I've added freebsd-fs to the cc list.
>
> I have vmcore's from them all.
Can you try to reproduce the issue using the same VM image but in a different VM
implementation? E.g. qemu...
--
Andriy Gapon
___
freebsd-current@f
If you have ACPI suspend/resume working, if it used to work but stopped working
at some time, if it never worked, but you are still hoping, could you please
test the following patch and report back?
http://svn.freebsd.by/files/acpi-apic-wakeup-final.patch
--
Andriy Gapon
ems :-)
http://people.freebsd.org/~avg/acpi-uma-cache.diff
What do you think?
--
Andriy Gapon
___
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"
ually never
used / touched at all (few hours after reboot and completely idle system).
--
Andriy Gapon
___
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"
174567 ?
It should be applied to src/recompiler/target-i386/translate.c, make sure that
it
goes to a section marked as 'case 0x1b8: /* SSE4.2 popcnt */'.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.f
on 17/01/2013 19:52 Sergey V. Dyatko said the following:
> On Thu, 17 Jan 2013 19:46:06 +0200
> Andriy Gapon wrote:
>
>> on 17/01/2013 19:02 Sergey V. Dyatko said the following:
>>> Hi,
>>>
>>> today I got panic on my laptop, running head, amd64 r245462.
; http://svn.freebsd.by/files/core20130117.txt
Do you have a real core file (vmcore*)?
> Konstantin, I added you to CC because you was last touched
> zfs_vfsops.c, I'm sorry if I was wrong :)
>
--
Andriy Gapon
___
freebsd-current@freebsd.org ma
e are any plan for implement it?
Please see the following thread which includes a patch:
http://thread.gmane.org/gmane.os.freebsd.current/145897/focus=145899
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/
on 15/11/2012 22:43 Andriy Gapon said the following:
> on 14/11/2012 01:43 Mateusz Guzik said the following:
>> Hello,
>>
>> avg@ suggested to include compiler version in the kernel so that it's
>> present in uname (and one can easly tell what was used to compi
uld be able to boot from any pool from which
you can boot now unless you have the condition described in the original
message.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubsc
I am glad that you could resolve this.
One of those things that look obvious only after discovered.
--
Andriy Gapon
___
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"
fault before the
KASSERT is reached (modulo reordering)?
--
Andriy Gapon
___
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"
ain full debug information to answer your question.
--
Andriy Gapon
___
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"
0xff8496fff4d0
> cngrab() at cngrab+0x35/frame 0xff8496fff4f0
> kdb_trap() at kdb_trap+0x124/frame 0xff8496fff550
> trap_fatal() at trap_fatal+0x345/frame 0xff8496fff5b0
> trap() at trap+0x836/frame 0xff8496fff7c0
> calltrap() at calltrap+0x8/frame 0xff8496fff7c0
>
on 17/12/2012 14:57 Volodymyr Kostyrko said the following:
> 13.12.2012 12:25, Andriy Gapon:
>> on 12/12/2012 21:35 Dimitry Andric said the following:
>>> Especially the recursive spa_load and traverse_visitbp calls are scary,
>>> because that can grow out of hand ve
f the cluster peeps and seeing if
> they'll run this up on the ref10* boxes and VMs, just to get some
> further exposure?
--
Andriy Gapon
___
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"
s not always work.
compat6x does not affect internal kernel interfaces.
So I suggest that you stick to some stable branch and use modules compiled for
that branch if you want to keep using the binary modules.
--
Andriy Gapon
___
freebsd-current@freebsd
ules/freebsd/vmmemctl/os.c of /usr/ports/emulators/open-vm-tools port), the
object lock is correctly acquired there. I suspect some binary incompatibility
between the module and your kernel. Try to recompile the module again using the
same source tree tree and the option.
> 2012/12/13 Andriy
of
> resembling it not being set properly.
bootfs property should not better. Multi-pool configurations has been tested
before the commit.
--
Andriy Gapon
___
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"
y git branch is a lightly modified version of FreeBSD, but
> doesn't contain any ZFS specific changes (I can point you to it if you
> like to look at it).
> Would appreciate some pointers on what to do next.
Try to get a working environment (using livecd, another disk, backups, etc), try
to follow the original instructions.
--
Andriy Gapon
___
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"
trace) if required.
>>
>>
>
>
> If someone didn't get attachment - here's link to screenshot
>
> https://www.box.com/s/fir8ntjc4rjq5xv0vbyl
Looks like either a bug or an "out-of-sync" issue in whatever
expected.
traverse_visitbp is also expected to recurse depending on data layout.
So yeah, it's probably even trickier than teaching clang to allocate smaller
stack
frames ;-)
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freeb
uld be automatically
> imported and file systems mounted. You can have disks in your system with
> ZFS pools that should not be auto-imported and zpool.cache is the way to
> tell the difference.
--
Andriy Gapon
___
freebsd-current@freebsd.org
s
>> warning is false-positive or not.
>
> I'm seeing the same warnings trying to build HEAD r242903 with
> clang on amd64. Andriy CCed.
I believe that there is no actual problem there.
--
Andriy Gapon
___
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"
ys/kern/sched_ule.c:2665
> #21 0x808524d4 in fork_exit (
> callout=0x808a5e20 , arg=0x0,
> frame=0xff800025eac0)
> at /home/emaste/src/head-ro/sys/kern/kern_fork.c:995
> #22 0x80be76de in fork_trampoline () at /tmp
on 16/11/2012 16:42 Andriy Gapon said the following:
> on 15/11/2012 23:44 Attilio Rao said the following:
>> Do you think you can test this patch?:
>> http://www.freebsd.org/~attilio/lockmgr_forcerec.patch
>
> I will use this patch in my tree, but I think that it is effecti
partitions). If
this command reports at least one valid ZFS label for a disk or a partition that
do not belong to any current pool, then the problem may affect you.
The best course is to remove the offending labels.
If you are affected, please follow up to this email.
--
An
by e.g. going to frame 13 and examining *td and *td->td_proc.
--
Andriy Gapon
___
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"
ointer will take
> it's time responding. Didn't do that a few weeks back. Wondering if it's
> just me?
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-curren
INE 0 0 0
>
> errors: No known data errors
>
> # uname -a
> FreeBSD opensolaris.technica-03.local 10.0-CURRENT FreeBSD
> 10.0-CURRENT #6 r243278M: Wed Nov 21 09:28:51 EET 2012
> root@opensolaris.technica-03.local:/usr/obj/usr/src/sys/SMP64
on 20/11/2012 17:06 Andriy Gapon said the following:
> on 20/11/2012 16:59 Andrei Lavreniyuk said the following:
>>>> Sorry to make you jump through so many hoops.
>>>> Now that I see that the probed config is entirely correct, the problem
>>>> appears to
&
iff
>
>
> At mount system trap and reboot.
>
Unexpected. Can you catch the backtrace of the panic?
If you have it on the screen.
--
Andriy Gapon
___
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 20/11/2012 15:56 Andriy Gapon said the following:
> on 20/11/2012 15:34 Andrei Lavreniyuk said the following:
>>> What about the " "un-ifdef" the DEBUG sections of it" part?
>>
>>
>> http://tor.reactor-xg.kiev.ua/files/zfs/20121120_0
roperly use spa_version in this
context because spa_ubsync is not initialized yet.
Let me think about how to fix this.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscr
>> it
>> and try again?
>> http://people.freebsd.org/~avg/spa_generate_rootconf.debug.diff
>
>
> I use spa_generate_rootconf.debug.diff.
What about the " "un-ifdef" the DEBUG sections of it" part?
> make kernel && reboot
>
> No new
why...
Could you please apply the following patch, "un-ifdef" the DEBUG sections of it
and try again?
http://people.freebsd.org/~avg/spa_generate_rootconf.debug.diff
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lis
om zfs:zsolar failed with error 45
Are there any other unusual messages before this line?
Could you please try adding vfs.zfs.debug=1 to loader.conf and check again?
Could you also provide 'zdb -CC zsolar' output and 'zdb -l /dev/gpt/diskX' for
each of the disks. These could
on 19/11/2012 17:07 Guido Falsi said the following:
> On 11/19/12 14:00, Andriy Gapon wrote:
>> on 18/11/2012 13:48 Andriy Gapon said the following:
>>> on 18/11/2012 02:26 Bartosz Stec said the following:
>>>
>>> Thank you both very much for testing!
>>
on 18/11/2012 13:48 Andriy Gapon said the following:
> on 18/11/2012 02:26 Bartosz Stec said the following:
>> W dniu 2012-11-16 17:17, Guido Falsi pisze:
>>> On 11/16/12 16:45, Andriy Gapon wrote:
>>>> Guido, Bartosz,
>>>> could you please test the patc
on 18/11/2012 02:26 Bartosz Stec said the following:
> W dniu 2012-11-16 17:17, Guido Falsi pisze:
>> On 11/16/12 16:45, Andriy Gapon wrote:
>>> Guido, Bartosz,
>>> could you please test the patch?
>>
>> I have just compiler an r242910 kernel with th
ct, and therefore ok to update?
Yes.
The problem occurs only if your pool has multiple vdevs _immediately_ under
root.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubs
t the patch?
Apologies for the breakage.
--
Andriy Gapon
___
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 15/11/2012 23:44 Attilio Rao said the following:
> Do you think you can test this patch?:
> http://www.freebsd.org/~attilio/lockmgr_forcerec.patch
I will use this patch in my tree, but I think that it is effectively already
quite
well tested by using INVARIANTS+WITNESS.
--
Andriy
t
>> compiler was used there.
> today it's clang vs. gcc -- transition time --, but again it's only part of
> the story,
> and soon it will only be noise.
Different kernel toolchains are here to stay.
And it's not just clang vs gcc, but also different toolchains for embedded
world, etc.
--
Andriy Gapon
___
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"
[cc list trimmed]
on 16/11/2012 12:43 Erik Cederstrand said the following:
> Den 16/11/2012 kl. 11.18 skrev Andriy Gapon :
>
>> This is starting to turn into a bikeshed, but anyway...
>>
>> on 16/11/2012 12:00 Daniel Braniss said the following:
>>> the questio
ediately know what
compiler was used there.
> IMHO, the only meaningfull information added to uname was the svn/git(and
> hopefully hg) rev. version.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/
on 16/11/2012 11:20 Erik Cederstrand said the following:
> Den 16/11/2012 kl. 08.34 skrev Andriy Gapon :
>
>> on 16/11/2012 01:09 Dimitry Andric said the following:
>>> And as I remarked in another reply, now that I have thought about it a
>>> bit, I would much rat
ers would be confused!
I would still like to have at least compiler's "base name" or type or something
in uname.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To un
pt should definitely make use of $CC.
Thank you for pointing this out.
--
Andriy Gapon
___
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"
no strong opinions on format, I just want this information easly
> accessible.
--
Andriy Gapon
___
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 15/11/2012 20:46 Attilio Rao said the following:
> On 11/15/12, Andriy Gapon wrote:
>>
>> To people knowing the code,
>>
>> do the following documentation changes look correct?
>
> The latter chunk is not correct.
> It will panic only if assertions are
this call fails, the shared lock is lost.
--
Andriy Gapon
___
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"
-strict-aliasing
>BUILD_OPTIMIZED=YES
>WITH_OPENSSL=YES
>WITH_XCHARSET=all
>WITH_CHARSET=utf8
>WITH_COLLATION=utf8_general_ci
>.endif
>
>.if ${.CURDIR:M*/usr/src/*} || ${.CURDIR:M*/usr/obj/*}
>
>CFLAGS=-O2 -pipe -fno-strict-aliasing
&
; What is really would like to find out is which drivers do not shutdown
> their chips correctly and thus cause stray interrupts on the kload boot.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
pad[64];
> };
Navdeep,
I've committed a different antidote for this BIOS bug as r243025.
Could you please that it works for you too?
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-c
Guys,
if you still have the hardware and use FreeBSD, could you please try r243025?
http://svnweb.freebsd.org/base?view=revision&revision=243025
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
on 11/11/2012 14:09 Garrett Cooper said the following:
> On Sun, Nov 11, 2012 at 4:07 AM, Andriy Gapon <mailto:a...@freebsd.org>> wrote:
>
> on 11/11/2012 12:26 Garrett Cooper said the following:
> > On Sun, Nov 11, 2012 at 1:59 AM, Alie Tan <mailto:a.
6
AS= /usr/local/bin/as
LD= /usr/local/bin/ld
NO_WERROR=yes
WERROR=
CWARNFLAGS= -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes \
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual \
-Wno-pointer-sign -D__FreeBSD_cc_ver
ve been done before the switch to make the transition
smoother.
--
Andriy Gapon
___
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 08/11/2012 16:26 Chuck Burns said the following:
> Honestly, if you do not like the way lsof does things,
I am indifferent, just noticed the discussion.
> I'm sure patches are welcome..
They are welcome all over the place. And beyond.
--
A
/sockstat/etc use?
Those base utilities do not seem to experience as much trouble as lsof.
BTW, it is still beyond me why VOP_WRITE could be of any interest to userland
code
even for such a utility as lsof.
--
Andriy Gapon
___
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"
.se/upload/head-reboots.mov
>
> Any ideas? Any specific revision I should try to back out?
>
Rather wild guess - try to back out the recent SMEP commit.
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/m
* priority.
@@ -2001,6 +2016,7 @@ sched_wakeup(struct thread *td)
sched_interact_update(td);
sched_pctcpu_update(ts, 0);
}
+#endif
/* Reset the slice value after we sleep. */
ts->ts_slice = sched_slice;
sched_add(td, SRQ_BORING);
--
Andriy Gapon
NFS_ROOT
>
> options BOOTP
> options BOOTP_NFSROOT
> options BOOTP_NFSV3
> options BOOTP_WIRED_TO=arge0
> options BOOTP_COMPAT
> options ROOTDEVNAME=\"nfs:172.16.1.101:/usr/ob
on 20/10/2012 20:39 Garrett Cooper said the following:
> On Sat, Oct 20, 2012 at 3:26 AM, Andriy Gapon wrote:
[snip]
>> main.o: In function `usage':
>> main.c:(.text+0x17): undefined reference to `arg_printusage'
>> main.o: In function `main':
>> m
on 23/10/2012 23:08 Andriy Gapon said the following:
> on 23/10/2012 20:56 Michael Schmiedgen said the following:
>> FreeBSD 10.0-CURRENT #0: Tue Oct 23 00:14:32 CEST 2012
>> root@gizeh.smoke:/usr/obj/usr/src/sys/GIZEH amd64
> ...
>> vdev_geom_open_by_path:519[1]: gu
you for this valuable information.
Do you have a rough estimate of when you started to experience this issue?
Could you please also provide output of the following command captured right
after a reboot and then after you re-add the cache disks?
$ zdb -lll /dev/ada0p
--
part of another pool. Maybe it's related to something giving up after
> assigning one partition from the drive to zpool somewhere? Though in
> your case it's p2 that's working and p1 that's wandered off, so maybe
> that's not it...
): undefined reference to `getarg'
Ruuning nm on libroken.a gives:
nm: getarg.o: File format not recognized
Any ideas?
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscr
on 18/10/2012 18:33 Andriy Gapon said the following:
> on 18/10/2012 18:20 Andriy Gapon said the following:
>> My guess is that the easiest way to avoid this ambiguity and the confusion
>> that it
>> causes (like the problem you described above) is to prepend "/dev/"
on 18/10/2012 18:20 Andriy Gapon said the following:
> My guess is that the easiest way to avoid this ambiguity and the confusion
> that it
> causes (like the problem you described above) is to prepend "/dev/", if it's
> missing, right in vfs_mountroot.c before calli
on 18/10/2012 16:50 Alexander Yerenkow said the following:
>
>
> 2012/10/18 Andriy Gapon mailto:a...@freebsd.org>>
>
> on 18/10/2012 12:11 Alexander Yerenkow said the following:
> > 2012/10/18 Andriy Gapon mailto:a...@freebsd.org>
> <mailto:a...@
on 18/10/2012 12:11 Alexander Yerenkow said the following:
> 2012/10/18 Andriy Gapon mailto:a...@freebsd.org>>
>
>
> First, I see "safe mode" mentioned in the subject, but nowhere in the
> body of
> the message? So, what's up with the safe mode
on 18/10/2012 12:11 Alexander Yerenkow said the following:
>
>
> 2012/10/18 Andriy Gapon mailto:a...@freebsd.org>>
>
>
> First, I see "safe mode" mentioned in the subject, but nowhere in the
> body of
> the message? So, what's up with
501 - 600 of 1235 matches
Mail list logo
