Hi,
I've submitted a change proposal to fix this (and potentially other problems):
https://reviews.freebsd.org/D49084
Please feel free to comment/review there.
For olivier@:
I'd be interested in seeing the full output of (minus serial numbers of course):
kenv | grep -F smbios
in all
cOS
> ) . . . ?
>
Hi,
UTM on Apple M3 running aarch64 FreeBSD VM (main branch):
olivier@vm:~ $ kenv smbios.system.product
QEMU Virtual Machine
olivier@vm:~ $ sysctl kern.vm_guest
kern.vm_guest: generic
olivier@vm:~ $ sysctl kern.hz
kern.hz: 100
UTM on Apple Intel running amd64 FreeBSD 14.2
On Wed, Oct 30, 2024 at 12:21 AM void wrote:
>
> this is interesting
>
> How do you use 'buildworld-jobs' ?
> make buildworld buildworld-jobs?
> make buildworld-jobs buildworld?
>
>
make buildworld-jobs buildkernel-jobs
removing most direct accesses in the process,
and add checks to some critical pieces of code where there is enough context to
know that groups must have been filled correctly (e.g., proc_set_cred()), to
counter the effect of increased conflation. I have started to explore this
route: It doesn&#
.33 x nproc).
And building the latest head from the stable-week (n272449-6e414739fc95)
using build[world|kernel]-jobs is working.
Regards,
Olivier
- Not enforcing privilege dropping in '/usr/libexec/locate.updatedb', or at the
very least provide an "escape hatch".
- Possibly moving it into '/usr/bin', along with 'locate', in which case, it
should not do any privilege dropping by default.
Thanks and regards.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
cts is really handy, and I don't want to have to give
permissions to 'nobody' for these.
Thanks and regards.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
On Thu, Aug 29, 2024 at 3:09 PM Olivier Cochard-Labbé
wrote:
>
> Everyone is advised to update their FreeBSD to 15.0-CURRENT
> n271832-04262ed78d23 :-)
>
>
I forgot to include an important clarification in my previous message:
I am only aware of the two failing regression tests,
-CURRENT
n271832-04262ed78d23 :-)
Regards,
Olivier
On Tue, Jan 30, 2024 at 3:50 PM David Wolfskill
wrote:
> The machines where I track head (& stable/14) daily get powered off once
> they have finished their work for the day; this is done via "poweroff".
>
> I noticed (this morning) that one of them never actually powered off
> yesterday. After
Typo, '/usr/local/etc/fstab' should read '/etc/defaults/fstab'.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
7;ve never
proposed anything not in these lines. Can you really argue that the sysctl
proposal goes against that?
> Anyway, I've said my piece. I agree with Mike that there's consensus for
> this from the installer, and after that consensus falls away. Mike's idea
> is one that I can get behind since it elegantly solves the general problem.
In the current situation, I can back using '/etc/fstab', or probably better,
'/usr/local/etc/fstab' to hold default mount options, but I'm strongly opposing
a pure userland implementation as long as my objections above are not addressed
properly.
Thanks and regards.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
ly? For consistency and simplicity, I think
it should.
- A device and a mount point, in which case I don't see why the default
shouldn't apply.
If the default is controlled by a sysctl, it's an administrator setting, and
only an opt-in one as long as we don't change the
ver happens
> overall. That is something I know I can do for my
> usage context.
With a sysctl knob defaulting to 'atime', you won't have to change anything.
Thanks for your participation.
Regards.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
dding.
About bike shedding, see my recent response to Mark, it applies to "folly" as
well.
> Apologies for the "attitude".
Yeah. Most prompts imagined by Poul-Henning Kamp in his bikeshed email would
have applied perfectly to your message.
Thanks for the thought.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
ne
defaults that match contemporary uses: It reduces the need for tweaks, which
serves both beginners but *also* seasoned administrators. This is in isolation
a very small step in this direction, but there have been others and more will
come. Collectively, they can build up to significant additional value for the
project.
Regards.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
me', to KISS. Once the sysctl is there, there
will be two possibilites: Either the installer changes the default, via
'loader.conf' ('sysctl.conf' is most probably handled too late during boot), or
it makes completely explicit in '/etc/fstab' what was
at! Please see the
"OPERATIONAL FLAGS" section in gpart(8).
In between your tentative modifications, just use 'gpart show' to see where you
stand.
Thanks and regards.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
Hi Mark,
> I seriously care about having a lack of access times.
Then, I think elaborating on your use cases would be valuable to the
discussion, if by chance you want to and can share about them.
Thanks and regards.
--
Olivier Certner
signature.asc
Description: This is a digitally sig
time' or 'atime') for all filesystems. This default would be used at
mount time if neither 'atime' nor 'noatime' is explicitly specified. That way,
people wanting 'noatime' by default everywhere could just set it to that. It
may also convince reticent people to have the default (i.e., this sysctl's
default value) changed to 'noatime', by providing a very simple way to revert
to the old behavior.
Thanks and regards.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
t used).
One of the perhaps unappreciated point and advantage of having 'noatime' as the
default is to avoid the complexity of both special casing based on media type
and having to configure the different applications that can mount partitions
(depending on your uses, there isn't only '
you, and for
reasons that seem to be unrelated with the topic, what can I say? Nothing
forces you to participate.
Thanks at least for admitting that you're using 'noatime', as well as most of
the other backers of the status quo in this discussion. Perhaps that should
tell you some
ple, which logically should be
those that care about 'atime', to accept 'noatime' as the default, since it
would become easier for them to override it back.
> Unless openzfs manges to decide to change that default across OSs,
> in my view FreeBSD should have it be left
r.t. atime.
I completely support the view that, if a copy realized through VOP_READ()
updates the access time, so should a copy realized through copy_file_range().
That is arguably also an application of POLA, but in fact here is much more: A
matter of correctness.
However I fail to see how that th
have backup perimeters
coinciding with file systems partitions and use snapshots to get the smoothest
possible experience. But snapshots alone do not guarantee the "correctness" of
a backup (the ability to restart smoothly from it).
Cheers.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
ss some ourselves; irrespective of whether they
validate or not the current evaluation).
And, as reported by others, even /var/mail should not need it in most uses
given that all prominent MUAs have long departed from using the access time
comparison alone. (I won't pronounce myself on this since I'm not personally
using them, but I'm not seeing any reason not to trust the reports. If some
people have contradictory facts, I hope that they will present them.)
Thanks and regards.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
at notion to have everywhere. I think your
> analysis needs more inputs.
May be, but to me the case for the default value debate at least seems quite
strong already.
Regards.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
> This is an interesting type of argument.
Except this is not an argument to the main discussion, as apparently you
haven't understood?
This kind of response is disingenuous. Either you said too much, or you didn't
say enough.
--
Olivier Certner
signature.asc
Descripti
nce for most users (IOW, I think that
developing "relatime" is a bad idea *in general*). And I think this is a
sufficiently reasonable conclusion that anyone with the same inputs would
conclude the same. So, if it's not the case, I would be interested in knowing
why, ideally.
Regards.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
his is what i use, except for some noatime mount points
> (/x/doc, /x/music, /x/pub, to be exact).
It seems that the other answers (mostly those of Robert IIRC) have shown that
this manpage text isn't up-to-date with current practices.
Which need(s) of yours are you trying to address exactly by using "relatime"?
Thanks and regards.
--
Olivier Certner
signature.asc
Description: This is a digitally signed message part.
On Fri, Nov 17, 2023 at 2:31 PM Herbert J. Skuhra wrote:
>
> 1. It even fails with a simple pf.conf:
>pass in all
>pass out all
>
> 2. Fetching port distfiles also failed.
>
> 3. If I disable rxcsum on the ethernet adapter (igb0) it works.
>
>
> I can't reproduce it with pfctl too (same i
kindly point them to it. I hope this can
contribute to at least attenuating the drain you're experiencing.
Regards.
--
Olivier Certner
On Thu, Nov 16, 2023 at 5:10 PM Herbert J. Skuhra wrote:
>
> OK, I am now running GENERIC-NODEBUG + "options TCPHPTS".
>
> After setting "sysctl net.inet.tcp.functions_default=rack" git no
> longer works:
>
>
Are you using a fresh 15 head or a specific network setup ?
Because I'm not able to rep
Hi Matthias,
Some ZFS dataset with zstd compression on jet, and no compression on
c720-1400094?
--
Olivier Certner
r local env after all, nor to CURRENT.
Regards.
--
Olivier Certner
> To enforce it for cases where mountd/nfsd is not being run would
> definitely be a POLA violation.
I could not agree more.
Thanks for the clarification.
--
Olivier Certner
enforcing it in general is. It would generally degrade the multiple
jails management experience on UFS (in the absence of a volume manager), where
all jails have roots in the same filesystem (to avoid allocating/deallocating
space as jails come and go or must be resized).
Regards.
--
Olivier Certner
Hi Andriy,
> if you escape to prompt directly loader didn't loaded all it's config
> so there is no modulepath defined, you need to 'boot-conf' to load the
> configuration files.
You might prefer to use 'read-conf' instead of interrupting 'boot-conf''s
countdown.
Regards.
--
Olivier Certner
Same problem here:
- I'm building FreeBSD head on a builder machine, and NFS mounting its
/usr/src and /usr/obj to 4 others
Results:
- 2 of them, UEFI+ZFS machines works great ((Thinkpad T420 and AMD Epyc
with Tyan motherboard)
- 2 of them, BIOS+UFS machines meet this "can't find /boot/ua/loader.l
s enough to reproduce this
problem.
Regards,
Olivier
On Fri, Apr 23, 2021 at 1:10 PM David Wolfskill
wrote:
> After the set of updates to etcupdate (main-n246232-0611aec3cf3a ..
> main-n246235-ba30215ae0ef), I find that "etcupdate -B -p" is working as
> expected, but after the following "make installworld", a subsequent
> "etcupdate -B" chugs along
t in various
> programs, summarized as (from the lldb bt outputs):
>
FREEBSD_COMPAT32 was indeed broken on arm64, and the process would crash
when receiving a signal. I believe I fixed it in -CURRENT with commit
c328f64d81079bad5064c8a387883df50ab5aaed
Regards,
Olivier
ansfer. The final reported bandwidth was
991KiB/s (same transfer size).
--
Olivier Certner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre
#x27;t know if this can have an influence on
these numbers (didn't test with pristine checkouts).
Important tip: When using `du`, don't forget to pass the '-A' option,
especially if using ZFS + compression.
--
Olivier Certner
___
ssion (in the sense of -current, so older than 6 months).
My idea was to generate very light UEFI VM images (because the snapshot VM
images are BIOS based) and scripting a bisector tool, but I never took the
time to do it.
Regards,
Olivier
___
freebs
On Wed, Apr 15, 2020 at 4:10 PM Kristof Provost wrote:
>
> The problem appears to be that
> /usr/local/lib/python3.7/site-packages/scapy/arch/unix.py is misparsing
> the `netstat -rnW` output.
>
Shouldn't scapy use the libxo output of netstat to mitigate this regression
?
___
On Thu, Oct 24, 2019 at 8:02 PM Franco Fichtner
wrote:
>
> > On 24. Oct 2019, at 7:56 PM, Gleb Smirnoff wrote:
> >
> > What's the reason to keep these outside of the tree drivers?
>
> Unmodified and newer drivers for older FreeBSD versions.
>
> In particular, 11.x had unfortunate and latent regr
ng boot partiton, I've no objection to remove
boot.config support.
Regards,
Olivier
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Wed, Aug 22, 2018 at 10:38 PM Olivier Cochard-Labbé
wrote:
> On Tue, Aug 21, 2018 at 3:15 PM Bjoern A. Zeeb <
> bzeeb-li...@lists.zabbadoz.net> wrote:
>
>> On 21 Aug 2018, at 12:31, Olivier Cochard-Labbé wrote:
>>
>>
>> Do you have a last-good revisi
On Tue, Aug 21, 2018 at 3:15 PM Bjoern A. Zeeb <
bzeeb-li...@lists.zabbadoz.net> wrote:
> On 21 Aug 2018, at 12:31, Olivier Cochard-Labbé wrote:
>
>
> Do you have a last-good revision?
>
>
> Hi,
Since VIMAGE was enabled by default on GENERIC
(r327969).
So perhaps
On Tue, Aug 21, 2018 at 11:29 AM Marko Zec wrote:
> On Mon, 20 Aug 2018 16:26:29 +0200
> Olivier Cochard-Labbé wrote:
>
> > Just loading carp kernel module is enough to panic it:
> >
> > [root@router]~# uname -a
> > FreeBSD router.bsdrp.net 12.0-ALPHA2 FreeB
BSD/src/sys/net/vnet.c:500
500 vs->func(vs->arg);
Regards,
Olivier
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Sun, Jun 17, 2018 at 10:01 AM O. Hartmann wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Running CURRENT as routing and firewalling appliance on a PCengines APU
> 2C4 with the
> latest (official) SEABios available for this product, NanoBSD (FreeBSD
> CURRENT FreeBSD
> 12.0-CURR
failure attached,
> >
> > Ok, it seems ConcurrencyKit was not tested with Pintium3.
> > Can you show the output from kgdb:
> >
> > disassemble *0xc0991ff0
>
> That'd do it .. :-(
[...]
Sorry about this.
It should be fixed with r329388.
Can you update and let
ea:
Can you check that all epairs have different MAC address each ?
I hit this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671
Regards,
Olivier
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-cu
On Wed, Mar 8, 2017 at 9:11 AM, Rozhuk Ivan wrote:
>
> sysctl hw.model
> please.
>
[root@APU]~# sysctl hw.model
hw.model: AMD G-T40E Processor
[root@apu2]~# sysctl hw.model
hw.model: AMD GX-412TC SOC
___
freebsd-current@freebsd.org mailing list
htt
On Wed, Mar 8, 2017 at 7:29 AM, Rozhuk Ivan wrote:
>
> Try now with last version of patch.
>
> Compile now and works on PC Engine APU1 and APU2:
[root@APU]~# kenv smbios.planar.product
APU
[root@APU]~# kldload amdtemp
amdtemp0: on hostb4
[root@APU]~# sysctl dev.amdtemp
dev.amdtemp.0.rtc.sensor
On Mon, Mar 6, 2017 at 3:04 AM, Rozhuk Ivan wrote:
> Hi!
>
>
> New amdtemp driver needs more testers!
>
>
> https://reviews.freebsd.org/D9759
>
>
This patch apply correctly (on 12-head r314770), but a "make buildkernel"
failed with
--- all_subdir_amdtemp ---
/usr/src/sys/modules/amdtemp/../..
On Tue, Jan 24, 2017 at 3:17 PM, Sean Bruno wrote:
>
>
> Did you increase the number of rx/tx rings to 8 and the number of
> descriptors to 4k in your tests or just the defaults?
>
Tuning are same as described in my previous email (rxd|txd=2048, rx|tx
process_limit=-1, max_interrupt_rate=16000).
On Tue, Jan 24, 2017 at 2:40 AM, Sean Bruno wrote:
>
>
> Which set of configs from your test suite are you using for this?
> Specifically, what packet size are you slamming across?
>
> https://github.com/ocochard/netbenches/tree/master/pktgen.configs
>
Because I'm in the point of view of a Telc
On Thu, Jan 12, 2017 at 1:54 AM, Matthew Macy wrote:
> > A flame graph for the core cycle count and a flame graph with cache
> miss stats from pmc would be a great start.
> >
> >
> > I didn't know the exact event name to use for cache miss stats, but
> here are the flame graphs for CPU_CLK_
On Wed, Jan 11, 2017 at 9:40 PM, Matthew Macy wrote:
>
> > > I can generate profiling data for you: what kind of data do you want
> ?
> > >
> >
>
> A flame graph for the core cycle count and a flame graph with cache miss
> stats from pmc would be a great start.
>
>
I didn't know the exact e
On Wed, Jan 11, 2017 at 9:13 PM, Matthew Macy wrote:
>
> > Hmmm ... did your old tests do 4 or 8 queues on this hardware?
> >
> > Did the old tests run 1024 tx/rx slots or the max 4096?
>
> That's a great point, only having one thread per core could easily account
> for this. I'm hoping Sean c
On Wed, Jan 11, 2017 at 4:17 PM, Sean Bruno wrote:
>
>
> Olivier:
>
> Give this a quick try. This isn't the correct way to do this, but I
> want to see if I'm on the right path:
>
thanks, it fix the problem, I've got back the 4 queues:
igb2: port 0x3
On Tue, Jan 10, 2017 at 4:31 AM, Sean Bruno wrote:
>
> I've updated sys/dev/e1000 at svn R311849 to match Matt Macy's work on
> IFLIB in the kernel.
>
> At this point, the driver deviates from Intel's code dramatically and
> you now get to yell directly into the freebsd-net@ megaphone for things
On Sat, Dec 17, 2016 at 10:19 AM, Slawa Olhovchenkov wrote:
>
> ===
> On FreeBSD older than 11.0, use more compact ip_fastfoward routine. It
> processes most packets falling back to 'normal' forward routine for
> fragments, packets with options, etc. Can save you up to 20% speed
> (but will break
thub.com/ocochard/netbenches/blob/master/AMD_GX-
412TC_4Cores_Intel_i210AT/ipsec/results/fbsd12.projects-
ipsec.equilibrium/graph.png
Thanks for your work!
Olivier
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To
I've checked tools/build/mk/OptionalObsoleteFiles.in and found that
lot's files are missing in the ".if ${MK_TOOLCHAIN} == no" section.
I've started a new run of phk's build_options_survey script:
https://people.freebsd.org/~olivier/build_option_survey_20160406/
An
SD 11.0-CURRENT #0 r294522: Thu
Jan 21 20:07:04 CET 2016
r...@lame5.bsdrp.net:/usr/obj/usr/src/sys/GENERIC-NODEBUG
amd64
root@lame5 # kldload ip_mroute
root@lame5
# kldstat -m ip_mroute
Id Refs Name
4971 ip_mroute
Regards,
Olivier
___
freebsd-c
On Tue, Jan 19, 2016 at 9:11 PM, Adrian Chadd
wrote:
> CAn you test AR9380 on that revision? That's -head, right?
>
No, sorry: I've got only AR9280 based wifi card (Compex WLE200NX
802.11a/b/g/n miniPCI).
And yes: it's
r293631
on
-head.
___
freeb
phones, several notebooks).
>
Hi,
I've got no problem on r293631
in hostap mode (
ath0: AR9280 mac 128.2 RF5133 phy 13.0
).
Regards,
Olivier
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd
On Wed, Jan 13, 2016 at 9:45 AM, Alexander V. Chernikov
wrote:
>
> I suspect the reason here is link state bridge handling.
> ix0 does not seem to have IFCAP_LINKSTATE option but re(4) does. Probably
> wlan0 doesn't have LINKSTATE option.
> Code in bridge_linkcheck() doesn't handle the case with
On Tue, Jan 12, 2016 at 9:52 PM, Alexander V. Chernikov <
melif...@freebsd.org> wrote:
>
> Could you show 'netstat -rn' output when one of bridge members is down?
> Btw, I tried to reproduce it today (but, with ix0 instead of wlan0) and I
> wasn't able to trigger the problem.
>
>
Sure,
here some
On Tue, Jan 12, 2016 at 7:22 PM, Adrian Chadd
wrote:
> This is actually the intended behaviour, right? The routed interface
> is down, so the IP address on it and connected to it are unreachable.
>
Hi Adrian,
the routed interface is a bridge interface, and this bridge interface had
only one of
After weeks of troubleshooting, at last I found how to reproduce this
problem ;-)
Here is the setup:
LAN0 <--> [(re0) fbsd router (bridge0 addm re1 addm wlan0)] <--> Wireless
LAN
If interface re1 (bridge0 member with wlan0) is in "active" status
(=ethernet cable plugged to something): I don't ha
Hi,
If wlan0 interface is member of a bridge, FreeBSD didn't reach to
forward-back packets to wireless client
My setup is this one:
internet gateway <--> [net0] fbsd router [net1 + wifi-hostap in bridge0]
<--> wireless client
and the problem description:
- wireless clients didn't receive any
On Wed, Oct 14, 2015 at 7:00 AM, Rui Paulo wrote:
> Hi,
>
> Please download and test the wpa_supplicant/hostapd import patch:
>
> http://people.freebsd.org/~rpaulo/patches/wpa-2.5.diff
>
>
>
Your patch were ested with success:
- hostapd v2.5
- Atheros 9280 (ath) in hostapd mode (WPA2-EAP
e on a bigger disk without any problem.
Regards,
Olivier
___
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"
drp.net/FreeBSD/GLEBWIFI-0.2-full-i386-vga.img.xz
-o - | xzcat | dd of=/dev/da1 bs=128k
Then boot on this USB flash disk.
Regards,
Olivier
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
On Thu, Jun 18, 2015 at 10:16 AM, Kevin Lo wrote:
>
> After bringing interface up I'm getting:
> http://i.imgur.com/XhOVJ68.jpg
>
>
I didn't meet this problem on head (r284301) with D2655 applied and using
an Alpha network AWUS036NHR v.2
___
freebsd
On Thu, Apr 30, 2015 at 5:28 PM, Edvard Fagerholm wrote:
>
> ping: unable to limit access to system.dns service: File exists
>
> Any ideas?
>
>
What's your exact revision number ?
I didn't meet the problem on r282220, but I've got the same problem on
r282296.
_
On Sun, Dec 14, 2014 at 3:52 PM, Ian Lepore wrote:
> I was testing at 115kbps, maybe at 9600 it would be significant. I
> don't understand why anything these days is still defaulting to 9600.
> It's the 21st century, but we never got the George Jetson flying cars we
> were promised, and apparent
For a simple workstation, we can use this simple configuration in
/etc/rc.conf:
firewall_type="workstation"
firewall_enable="YES"
firewall_myservices="22,80"
firewall_allowservices="any"
But the firewall_myservices allows only TCP services.
It's not possible to declare UDP services (like a torrent
On Wed, Jan 22, 2014 at 9:41 PM, Olivier Cochard-Labbé
wrote:
> I've meet the problem on FreeBSD 10.0 with a Kingston DT 101 G2 (this is
> why I've fill the PR usb/185747), but it wasn't my key then I didn't have
> access to it anymore.
> Then the author of the PR
On Wed, Jan 22, 2014 at 8:39 PM, Hans Petter Selasky wrote:
> On 01/22/14 11:39, Hans Petter Selasky wrote:
>
>> On 01/22/14 11:31, Olivier Cochard-Labbé wrote:
>>
>>> Hi all,
>>> There is a regression since 9.2 (still not fixed on 10.0) regarding a
>>
Hi all,
There is a regression since 9.2 (still not fixed on 10.0) regarding a list
of Kingston DataTraveler/DT USB keys
- usb/180837, regarding "Kingston DT 101 G2": This PR include a patch for
9.2 and a link to netbsd code that include other Kingston USB keys;
- usb/184014, regarding "Kingston DT
On Tue, Jan 21, 2014 at 2:33 PM, Gleb Smirnoff wrote:
> On Sun, Jan 19, 2014 at 02:42:32AM +0100, Olivier Cochard-Labbé wrote:
> O> But there is still a regression regarding the PIM socket behavior not
> O> related to the packet format.
>
> Can you please try this patch
On Wed, Jan 15, 2014 at 12:34 PM, Gleb Smirnoff wrote:
> Olivier,
>
>
> TL;DR version: you need not subtract iphdrlen in 10.0. Code in
> igmp.c:accept_igmp()
> should be smth like:
>
> iphdrlen = ip->ip_hl << 2;
> #ifdef RAW_INPUT_IS_RAW /* Linux *
Hi all,
I'm trying to port a PIM sparse-mode daemon (
https://github.com/troglobit/pimd/) and I've meet a problem:
This daemon compile and run fine on FreeBSD 9.2 but on 10-RC5 this daemon
can't understand received multicast packets (received from other PIM
neighbors) and display this kind of erro
p->b_error = bip->bio_error;
> if (bp->b_error)
>
Problem fixed with your patch for me too: Thanks.
Olivier
___
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"
urrent/2013-December/047032.html
Regards,
Olivier
___
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"
d0 of=/tmp/DEST.img bs=64k
=> This last "dd" works great on 10.0-BETA3 and older but failed on
-current (r258675 and r259096) with the message:
dd: /dev/md0s1: Input/output error
Regards,
Olivier
___
freebsd-current@freebsd.org mailing list
h
p://lists.ntp.org/pipermail/pool/2013-November/thread.html
Regards,
Olivier
___
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,
2013/11/14 Herbert J. Skuhra
>
> to. 14. nov. 2013 kl. 11.02 +0100 skrev Olivier Smedts:
>
>
> Hello,
>>
>> cc'ing glebius since he committed r257694 ("Remove remnants of BIND from
>> /etc, since there is no BIND in base now.") which re
misc
To remove old files and directories run 'make delete-old'.
To remove old libraries run 'make delete-old-libs'.
Thanks !
--
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@g
uot;C programming, a modern approach", then you have to wait :-)
By the way, I've documented a little more my benching lab and scripts used
here:
http://bsdrp.net/documentation/examples/freebsd_performance_regression_lab
Regards,
Olivier
___
fre
server was poweroff without unmounting this
sub-folder first.
I need to check the NFS mount option for avoiding to stuck all the
disk-related process once the NFS server disapear.
Thanks for pointing this.
Olivier
___
freebsd-current@freebsd.or
21 cmd: fstat 15781 [rpcrecon] 2879.63r 0.00u 0.01s 0% 0k
load: 0.24 cmd: df 15919 [connec] 1047.98r 0.00u 0.00s 0% 0k
load: 0.22 cmd: df 15919 [connec] 1054.22r 0.00u 0.00s 0% 0k
and the PS status:
olivier15919 0.0 0.0 14400 16 7 D+7:06PM 0:00.01 df -h
olivier1578
For information: It's possible to reproduce this problem using the
indication given in kern/121385 (5 years old PR).
Regards,
Olivier
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubs
I've just have another crash related to mount_unionfs but on sparc64
arch this time ( 10.0-ALPHA4 #2 r255947).
Still no core dump:
panic: vm_fault: fault on nofault entry, addr: 1c05f2000
cpuid = 0
KDB: stack backtrace:
panic() at panic+0x1d4
vm_fault_hold() at vm_fault_hold+0x174
vm_fault() at
1 - 100 of 249 matches
Mail list logo
