ible given the lack of upstream
support) for many years to come.
Think of this as "You have about 4 years to make other arrangements
before this support is gone."
-- Ian
___
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"
ry)
> *** Error code 1
>
> Stop.
> make[2]: stopped in /usr/obj/usr/src/sys/GENERIC
> *** Error code 1
>
> Stop.
> make[1]: stopped in /usr/src
Did you update your source and then "make buildkernel" without
buildworld? If so, a "make kernel-toolchain&q
On Mon, 2013-11-04 at 19:44 -0500, Outback Dingo wrote:
> On Mon, Nov 4, 2013 at 7:36 PM, Ian Lepore wrote:
>
> > On Mon, 2013-11-04 at 19:25 -0500, Outback Dingo wrote:
> > > cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls
> > > -Wnest
On Tue, 2013-11-05 at 11:01 +0400, Gleb Smirnoff wrote:
> On Mon, Nov 04, 2013 at 10:09:54PM -0700, Ian Lepore wrote:
> I> > > /usr/src/sys/dev/aic7xxx/aic7xxx.seq
> I> > > > make[2]: exec(aicasm) failed (No such file or directory)
> I> > > > ***
On Tue, 2013-11-05 at 19:12 +0400, Gleb Smirnoff wrote:
> On Tue, Nov 05, 2013 at 08:00:52AM -0700, Ian Lepore wrote:
> I> > I> You were just unlucky that your updates bracketed my checkin that
> I> > I> changed the build process for the aicasm tool so that it gets bui
I'll do it.
-- Ian
On Fri, 2013-11-08 at 08:05 -0800, Adrian Chadd wrote:
> Can someone please take care of this? I'm a little busy for the next
> couple days.
>
> Feel free to commit to the contrib code.
>
> Thanks!
>
>
>
> -adrian
>
>
>
tions ?
>
> Tnx
> sorry for my English ..
Try adding hw.ata.ata_dma=0 to your /boot/loader.conf. I don't know why
the bios can do DMA on a CF and freebsd can't, but we've needed to add
that at $work for years (going back to freebsd 4.x at least).
nclude the BeagleBone, the
Wandboard, and to a lesser degree, the Cubieboard (which has sketchy
documentation, but a good bit of reverse engineering has been done to
support it).
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.f
On Thu, 2013-11-21 at 10:35 +0100, Berislav Purgar wrote:
> On Wed, Nov 20, 2013 at 11:29 PM, Ian Lepore wrote:
>
> > On Wed, 2013-11-20 at 21:27 +0100, Berislav Purgar wrote:
> > > Hello ..
> > >
> > > I have problem with microdrive and some CF cards on IG
s logging in /var/log/message provide that is
> not provided by 'pkg info'? It is useless noise.
>
"Useless noise" is what you get when someone holds an opinion that
clearly nobody else agrees with, and yet they somehow think that just
saying it over and over again will
"^Z bg".
Also, at the point you would hit ^Z, it might be handy to hit ^T and see
what the process is actually doing.
-- Ian
___
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"
lt boot slice back to 1, then
> "shutdown -p now" -- and re-created the panic.
>
> I can leave the machine up for a while if anyone has suggestions for me
> to poke around. I have a local private mirror of the FreeBSD SVN repos
> and a spare bootable slice; I'm williing to try patches. The machine
> isn't especially fast, but it's generally OK.
>
> If it would be worthwhile, I could reboot my laptop to slice 4 (head) &
> attempt the same reset-to-slice-1-default & power-off.
>
> This definitely did not happen @r260875, and it appears to be quite
> repeatable @r260904.
>
> Peace,
> david
Since you mention serial console, I think r260890 might be a candidate.
-- Ian
___
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"
update?
Ian
--
Ian Freislich
___
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 missing. Run 'make ahcfirmware'
>
> (don't think it matters, but i am cross compiling amd64
> from a stable/9 amd64 system, using clang).
> I am not sure which commit triggered the problem,
> but this used to work in the past -- toolchain was e
s asking had nothing to do with running a VM on ARM. If you
were actually a developer as you claim, you'd know that.
Everything posted by this person so far is indeed off-topic spam.
-- Ian
>
> On Sun, Feb 16, 2014 at 6:25 AM, Boris Samorodov wrote:
>
> > 16.02.
On Fri, 2014-02-14 at 13:46 -0800, Luigi Rizzo wrote:
> On Fri, Feb 14, 2014 at 10:23 AM, Ian Lepore wrote:
>
> > On Fri, 2014-02-14 at 18:35 +0100, Luigi Rizzo wrote:
> > > on a freshly checked out HEAD,
> > > "make toolchain" followed b
o know when a disk was replaced.
> >
> > Would there be any other mechanism to accomplish this?
>
> I think if you hot attach a device post-boot it will have the time it was
> attached as the birth time. I think it is only devices created during boot
> that use time 0.
&
kern.ipc.nmbclusters="1048576"
kern.ipc.maxmbufmem="10737418240"
kern.ipc.nmbufs=13045170
Ian
--
Ian Freislich
___
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"
rn |wc -l
> ia> 480446
>
> Perhaps does the attached patch fix this?
Sadly, not.
Ian
--
Ian Freislich
___
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"
rew, retrying
netstat: Routing table grew, retrying
netstat: Routing table grew, retrying
netstat: Routing table grew, retrying
netstat: Routing table grew, retrying
netstat: sysctl: net.route.0.0.dump.0: Cannot allocate memory
1
[firewall1.jnb1] ~ # netstat -rn |wc -l
rage
> ia> case.
>
> Can you try the attached patch? It will attempt to enlarge the
> buffer every retry.
I think the routing table grows too fast. It still fails.
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing l
matic files for FreeBSD ?
>
> Last time I looked there were only a handful. I’ll conduct a census and get a
> concrete enumeration of the problem…
Last time I noticed (early last year) there were 3 files ending in a dot
and no case conflicts. Mercurial now finds just the one file endi
> > > AES-NI... Are you using gcc as cc? If so, do you have the necessary
> > > tool chain work that I did in r255185 in your local tree?
> >
> >
> > The problem is that the kernel is deepening on a compiler header which is
> not in the rig
ot;rule" appears to be an undocumented prejudice.
People love to throw around assertions about "rules" of the English
language. It doesn't have many rules (subject has to agree in number
with the verb, that's about it for unbreakable rules), but it has as
many opinions on pro
for that is: sendmail_enable="NONE"
Once you have that setting in place you'll find that the periodic
scripts complain because they don't read rc.conf, they just assume
sendmail is there and running and generating logs to be scanned.
-- Ian
___
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"
Sorry about that, hopefully I've fixed it for now with r264054 (but
whenever you're checking in a fix for a fix you're on pretty shakey
ground). This is a temporary workaround while I spend a few days
rewriting some legacy arm code to fix the problem for real.
-- Ian
On Wed, 2014
> Glen
>
A couple weeks corresponds somewhat with the parallel subdir build
changes (it's about 3 weeks now). Try this patch I cooked up today for
$work, and in src/lib/Makefile add .WAIT (as if it were a directory
name) between ${SUBDIR_ORDERED} and the rest of the directories.
-- Ian
On Mon, 2014-04-21 at 23:26 -0400, Glen Barber wrote:
> On Mon, Apr 21, 2014 at 11:21:24PM -0400, Glen Barber wrote:
> > On Mon, Apr 21, 2014 at 09:09:42PM -0600, Ian Lepore wrote:
> > > > The last successful build for powerpc on head/ was April 8. But I am
> > >
On Mon, 2014-04-21 at 23:26 -0400, Glen Barber wrote:
> On Mon, Apr 21, 2014 at 11:21:24PM -0400, Glen Barber wrote:
> > On Mon, Apr 21, 2014 at 09:09:42PM -0600, Ian Lepore wrote:
> > > > The last successful build for powerpc on head/ was April 8. But I am
> > >
On Tue, 2014-04-22 at 00:13 -0400, Glen Barber wrote:
> On Mon, Apr 21, 2014 at 10:05:57PM -0600, Ian Lepore wrote:
> > On Mon, 2014-04-21 at 23:26 -0400, Glen Barber wrote:
> > > On Mon, Apr 21, 2014 at 11:21:24PM -0400, Glen Barber wrote:
> > > > On Mon, Apr 21,
this:
WITH_GCC=yes \
WITH_GNUCXX=yes \
WITHOUT_CLANG=yes \
WITHOUT_CLANG_IS_CC=yes \
But that's now several weeks out of date, and there are two new knobs I
haven't investigated yet: WITH_CLANG_BOOTSTRAP and WITH_GCC_BOOTSTRAP.
-- Ian
_
On Mon, 2014-04-28 at 14:47 +0800, Julian Elischer wrote:
> On 4/28/14, 12:30 AM, Ian Lepore wrote:
> > On Sun, 2014-04-27 at 22:25 +0800, Julian Elischer wrote:
> >> I need to hold off using CLANG for a while at $JOB. We are moving to a
> >> newer FBSD in the vicinity
On Mon, 2014-04-28 at 14:54 +0800, Julian Elischer wrote:
> On 4/28/14, 12:30 AM, Ian Lepore wrote:
> > WITH_GCC=yes \
> > WITH_GNUCXX=yes \
> > WITHOUT_CLANG=yes \
> > WITHOUT_CLANG_IS_CC=yes \
> forgot to ask.. is this in /etc/make.conf?
> or
set BUILDENV_SHELL in
your environment. There's also a "buildenvvars" target that will let
you capture the environment you need so that you can use it within your
own build scripts without needing an interactive shell.
-- Ian
___
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 Mon, 2014-04-28 at 22:03 +0800, Julian Elischer wrote:
> On 4/28/14, 8:05 PM, Ian Lepore wrote:
> > On Mon, 2014-04-28 at 14:54 +0800, Julian Elischer wrote:
> >> On 4/28/14, 12:30 AM, Ian Lepore wrote:
> >>> WITH_GCC=yes \
> >>> W
On Mon, 2014-04-28 at 22:07 +0800, Julian Elischer wrote:
> On 4/28/14, 8:19 PM, Ian Lepore wrote:
> > On Mon, 2014-04-28 at 15:50 +0800, Julian Elischer wrote:
> >> I need to do the equivalent of "cd /usr/src/cddl/usr.sbin/dtrace;
> >> make DESTDIR=/mumble all in
On Mon, 2014-04-28 at 10:04 -0600, Warner Losh wrote:
> On Apr 28, 2014, at 9:52 AM, Kevin Oberman wrote:
>
> > On Mon, Apr 28, 2014 at 7:23 AM, Ian Lepore wrote:
> >
> >> On Mon, 2014-04-28 at 22:03 +0800, Julian Elischer wrote:
> >>> On 4/28/14, 8:05 PM
l, option :)
>
> Warner
Actually the hooks are in place to do this stuff. Instead of make
buildenv to get an interactive shell you can do something like
BLDENV=`${MAKE} buildenvvars`
chroot buildchroot/ "env -i $${BLDENV} cd /usr/src/somewhere && \
make all install"
-- Ian
___
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"
27;t
compatible with clang, or something along those lines.
-- Ian
___
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 Tue, 2014-04-29 at 13:31 +0800, Julian Elischer wrote:
> On 4/29/14, 8:57 AM, Ian Lepore wrote:
> > On Mon, 2014-04-28 at 18:36 -0600, Warner Losh wrote:
> >> On Apr 28, 2014, at 1:48 AM, Julian Elischer wrote:
> >>
> >>> I need to do the equivalent of
gt; "/usr/src/lib/libc/Makefile"
> line 113: Malformed conditional (${MK_FP_LIBC} == "no") make:
> "/usr/src/lib/libc/Makefile" line 116: Malformed conditional
> (${MK_NS_CACHING} != "no")
> make: Fatal errors encountered -- cannot con
/FreeBSD/arm
It is partially supported, in that freebsd should be able to boot and
run on the Utilite box (I'm not sure anyone has done it yet). But for
your needs, we don't have all the support yet -- there is no driver for
the wifi chip, and nobody has worked on PCIe yet so the seco
t; > invocation)
> > *** Error code 1
> >
> > Stop.
> > make[6]: stopped in /usr/src/lib/clang/liblldbAPI
> > *** Error code 1
> > -
While I don't think it should affect this problem, "ARCH=arm" isn't
needed. If anything it wo
On Mon, 2014-05-19 at 00:08 +0400, Boris Samorodov wrote:
> 18.05.2014 20:38, Ian Lepore пишет:
> > On Sun, 2014-05-18 at 20:09 +0400, Boris Samorodov wrote:
> >> 18.05.2014 19:48, Boris Samorodov пишет:
> >>> Hi All,
> >>>
> >>> The system:
r patches are in place? I've never seen anything
like that on arm. The 0xc000 address is the start of the kernel
address space. Also, the userland stack grows down from 0xbfff, so
walking off the top of the stack would hit that address.
-- Ian
> I also have a sparc64 box, but
gure out the mapping
between pthread scheduling classes and priorities and freebsd's idea of
thread prorities. I eventually gave up on the pthread API and used the
freebsd native function rtprio_thread() instead.
-- Ian
___
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 first email, both libncurses.a and libncurses_p.a build fine.
>
It looks like this is a SUBDIR_PARALLEL build fallout. I've finally
committed the fine-grained dependency fix I've been sitting on for
weeks, could you please try updating to r267511 and then applying the
attached t
ime -t -a$i >/tmp/mprime$i.log &
done
Many overclockers use this to ensure the system is stable with the OC
settings. If your system can run a copy of mprime per cpu continuously
for 24 hours the hardware is fine.
-- Ian
___
freebsd-current@freeb
;t prevent
contacting the server (the override may be for a different nfs path).
See http://svnweb.freebsd.org/base?view=revision&revision=253847 for
details.
I didn't consider at the time that someone might want to avoid doing any
bootp configuration at all, but in retrospect I can think o
On Sat, 2014-07-26 at 02:03 -0700, Beeblebrox wrote:
> @ Ian:
> I added your code and rebuilt the kernel.
> /boot/loader.conf also has vfs.nfs.bootp_disable="YES"
> Previously described problem persists.
>
It needs to be set to =1, not =YES.
-- Ian
> SEPARATE KBD_KE
closer to bare metal. Different people will be attracted to, and will
be able to work most efficiently with, such different approaches.
I've no idea how pf works at the kernel level, as compared with ipfw's
virtual machine opcode execution; I daresay each has its strengths and
weaknesses. However it's the ruleset configuration language that is the
main concern of most packet filter users, not kernel level operation.
I believe in ecosystem strength through diversity, as much in projects
like FreeBSD as anywhere in the 'real' world. It could even discourage
(for example) ongoing ipfw development if there were no other options.
cheers, Ian
___
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"
ites to a slow flash-based device can
block reads from faster devices makes me think this is somehow related
to available buffers in the OS. I wonder if this could be one of those
situations where reducing the amount of buffers improves responsiveness
(if not necessarily overall throughput).
-- Ian
On Sun, 2013-03-03 at 13:35 +, Poul-Henning Kamp wrote:
> Content-Type: text/plain; charset=ISO-8859-1
>
> In message <1362317291.1195.216.ca...@revolution.hippie.lan>, Ian Lepore
> writes
> :
>
> >I run into this behavior all the time too, mostly on
lack of TCQ/NCQ slots, given that no such
thing exists with SD card IO.
When this is going on, the process driving the massive output spends
almost all its time in a wdrain wait, and if you try to launch an app
that isn't already in cache, a siginfo generally shows it to be in a
getblk wait
ers at
specific code until I have better information.
I kind of like the suggestion someone else made of having a NOATIME
kernel config option. I can't make a strong case for it, but it appeals
to me. If it would allow signifcant pieces of kernel or filesystem code
to be eliminated at co
On Sun, 2013-03-03 at 20:28 +, Steven Hartland wrote:
> - Original Message -
> From: "Ian Lepore"
> To: "Poul-Henning Kamp"
> Cc: "deeptech71" ; ;
> "Peter Jeremy"
> Sent: Sunday, March 03, 2013 1:54 PM
> Subject: Re:
On Mon, 2013-03-04 at 21:27 -0800, Don Lewis wrote:
> On 4 Mar, Ian Lepore wrote:
> > On Sun, 2013-03-03 at 19:01 -0800, Don Lewis wrote:
> >> On 3 Mar, Poul-Henning Kamp wrote:
> >>
> >> > For various reasons (see: Lemming-syncer) FreeBSD will block al
On Mon, 2013-03-04 at 21:33 -0800, Don Lewis wrote:
> On 4 Mar, Ian Lepore wrote:
> > On Sun, 2013-03-03 at 20:28 +, Steven Hartland wrote:
> >> - Original Message -----
> >> From: "Ian Lepore"
> >> To: "Poul-Henning Kamp"
&
Ethernet autoselect (1000baseT )
status: active
These are both the same thing. Is there any particular reason that
you want multiple interfaces? I can't see a use for it beyond "it's
what I'm used to seeing" unless the
:
ifconfig vlan11 create vlan 11 vlandev arge0 inet 10.10.11.1 netmask
255.255.255.0
or
ifconfig vlan11 create vlan 11 vlandev arge0 inet 10.10.11.1/24
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailm
be better, worse, or no different by changing to the ata+cam
way of doing things (but I don't really have time to do extensive
testing right now either).
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailma
ynchronous-unwind-tables -ffreestanding -fstack-protector
> > cc: error: no such file or directory: '/src/sys/dev/nvme/nvme_uio.c'
> > mkdep: compile failed
> >
>
> I deleted nvme_uio.c in r249420, as well as removing it from the Makefile.
> Can someone kindly point me to what step I'm missing here?
>
> Thanks,
References to it also appear in sys/conf/files.{amd64,i386}.
-- Ian
___
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"
Hi
For quite some time this mirror site has been unreachable. AFAICT,
my ex colleagues who used to maintain it have moved on and it's now
been left unmaintained. I left there in 2004 and Mark Murray who
set it up left shortly thereafter. Perhaps it should be dropped
from the mirror list.
es from the kernel, but I've never really
noticed any performance hit, even with dozens of nullfs and devfs mounts
in various chroots.
-- Ian
___
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"
: /usr/obj/usr/src/lib32: Directory not empty
*** [_worldtmp] Error code 1
Ian
--
Ian Freislich
___
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"
ll -CS" in the make.conf.
Ah, thanks. That would be the difference, except that I have:
INSTALL=install
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubs
allow the rc system to reload and stop named (without a
kill) no matter what the configured chroot is.
Ian
--
Ian Freislich
___
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"
ally rndc (not named) that fails to find its key
or config if you choose to use a chrootdir that isn't the default.
Ian
--
Ian Freislich
___
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"
e 1
gw is defined 'const'.
@625:
error = (*ifp->if_output)(ifp, m, (struct sockaddr *)gw, ro)
if_output arg3 needs to be protoyped const or gw needs to not be
declared const.
Ian
--
Ian Freislich
___
freebsd-current@freebs
f97a8, rbp = 0x8014f68d4 ---
Uptime: 20m13s
Dumping 1688 out of 16368 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
Dump complete
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...
cpu_reset: Restarting BSP
cpu_reset_proxy: Stopped CPU 15
Ian
--
Ian Frei
x800a96daa, rsp =
0x7fffccc8, rbp = 0x7fffcce0 ---
Ian
--
Ian Freislich
___
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"
about a potentially corrupted pointer. This makes me wonder
> whether (a) you are experiencing hardware faults -- it would be worth running
> some memory/cpu/etc tests and (b) if we might be seeing a software memory
> corruption bug of some sort.
>
> Other users have reported
pdate was done).
>
> I see a number locking changes in the area. Note that this is UDP,
> most likely a dns lookup.
I'll work to confirm this here. I was a little slow in bisecting
because I spent 2 days trying to figure out what revision caused
PF to rapidly expire its entire s
f846b3c3c00) at /usr/src/sys/kern/kern_fork.c:991
#23 0x805ff39e in fork_trampoline ()
at /usr/src/sys/amd64/amd64/exception.S:602
#24 0x000000000000 in ?? ()
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://l
counted back up to 15, then ticks - td->td_blktick gives
an elapsed time of 16, as it should be. Whether exploiting this
property of signed overflow is elegant or ugly is in the eye of the
beholder. :)
If the intent of the "ticks < td->td_blktick" is
trsep(&p, ":"), "nfs") != 0)
> > + panic("ROOTDEVNAME is not an NFS mount point");
> > + }
> > +#endif
> > if (p != NULL) {
> > if (gctx->setrootfs != NULL) {
> > printf("rootfs %s (ignored) ", p);
> >
I've seen several requests over the past year for an nfs ROOTDEVNAME
along with BOOTP to work properly from ARM developers (myself included),
so I don't think we should worry about breaking existing config that
happens to be checked in but a) hasn't been tested by anyone for ages,
and b) doesn't work anyway (ROOTDEVNAME just gets ignored).
-- Ian
___
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"
; }
>
>
> or something like that?
I'm strongly opposed to removing the ROOTDEVNAME config option, for the
simple reason that loader(8) is optional so there has to be a way to set
certain basic runtime options at compile time, and ROOTDEVNAME is one of
them.
There is already a loader
all ()
at /usr/src/sys/amd64/amd64/exception.S:387
#12 0x00080160670a in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb)
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
On Sun, 2013-06-02 at 19:57 -0400, Rick Macklem wrote:
> Ian Lepore wrote:
> > On Sat, 2013-06-01 at 20:28 -0400, Rick Macklem wrote:
> > > Lars Eggert wrote:
> > > > Hi,
> > > >
> > > > to conclude this thread, the patch below allow
/kern/kern_fork.c:991
#25 0x805f5d7e in fork_trampoline ()
at /usr/src/sys/amd64/amd64/exception.S:602
#26 0x in ?? ()
Current language: auto; currently minimal
(kgdb)
--
Ian Freislich
___
freebsd-current@free
Andre Oppermann wrote:
> On 19.06.2013 11:10, Ian FREISLICH wrote:
> > Hi
> >
> > I'm seeing this panic quite regularly now. Most recent sighting on r251858.
>
> This panic message is not very informative and very hard to extract any
> meaningful hints. D
Gleb Smirnoff wrote:
> A> This seems to be a fallout of the recent UMA changes and its interaction
> A> with the per-cpu counter(9) system.
> A>
> A> Adding in and handing over to Gleb and Jeff as they touched this area last
.
>
> Ian has reported this panic seve
s = 0x0082
bmAttributes = 0x0002
wMaxPacketSize = 0x0040
bInterval = 0x0001
bRefresh = 0x
bSynchAddress = 0x0000
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listin
"Daniel O'Connor" wrote:
>
> On 22/06/2013, at 4:10, Ian FREISLICH wrote:
> > I bought a relay control board that has a USB interface. It presents
> > a serial port to Linux on /dev/ttyACMx. However when I plug it
> > into my FreeBSD host, it detects a
Hans Petter Selasky wrote:
> On 06/22/13 20:54, Ian FREISLICH wrote:
> > "Daniel O'Connor" wrote:
> >>
> >> On 22/06/2013, at 4:10, Ian FREISLICH wrote:
> >>> I bought a relay control board that has a USB interface. It presents
> >>
Hans Petter Selasky wrote:
> On 06/23/13 10:33, Ian FREISLICH wrote:
> > status 0xea1a1
> > 10:29:19.904434 usbus0.2 SUBM-BULK-EP=0002,SPD=FULL,NFR=1,SLEN=4,IVAL=0
> > frame[0] WRITE 1 bytes
> > 6F -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |o
t seems to ignore the configured string.
I can however 'ifconfig lagg0 ether 00:1e:c9:53:3e:15' from the
cammand line, so there's something in the rc scripts that's mangling
the argument.
Ian
--
Ian Freislich
___
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"
"Ian FREISLICH" wrote:
> What I have been doing is probably wrong, but it worked up until
> r252360:
I see from the commit log that it was actually 252015 that broke my router.
--
Ian Freislich
___
freebsd-current@freebsd.org m
C address though.
>
> Please try r252426.
Thanks. That fixes it.
BTW, nice new features in network.subr.
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubs
Id = 0x10676 Family = 0x6 Model = 0x17 Stepping =
6
Features=0xbfebfbff
Features2=0x8e39d
AMD Features=0x20100800
AMD Features2=0x1
TSC: P-state invariant, performance statistics
real memory = 4294967296 (4096 MB)
avail memory = 3970727936 (3786 MB)
Ian
--
Ian Freislich
___
hat's wedged. A lot of the time the
userland process is unkillable, but often it is killable. How do
I get from from the PID to where the FS is stuck in the kernel?
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://lists.free
John Baldwin wrote:
> On Thursday, July 04, 2013 5:03:29 am Ian FREISLICH wrote:
> > Konstantin Belousov wrote:
> > >
> > > Care to provide any useful information ?
> > >
> > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-
> handbo
John Baldwin wrote:
> On Thursday, July 11, 2013 6:54:35 am Ian FREISLICH wrote:
> > John Baldwin wrote:
> > > On Thursday, July 04, 2013 5:03:29 am Ian FREISLICH wrote:
> > > > Konstantin Belousov wrote:
> > > > >
> > > > > Care t
Konstantin Belousov wrote:
>
> --rMuTkhzRlt+HYtLC
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Fri, Jul 12, 2013 at 08:11:36PM +0200, Ian FREISLICH wrote:
> > John Baldwin wrote:
> &g
Konstantin Belousov wrote:
> On Fri, Jul 12, 2013 at 11:34:18PM +0200, Ian FREISLICH wrote:
> > (kgdb) print runningbufreq
> > $1 = 1
> > (kgdb) print runningbufspace
> > $2 = 0
> > (kgdb) print lorunningspace
> > $3 = 4587520
> > (kgdb) print hirunning
values get significantly tuned up? I recall now setting this nearly
a year ago when we did our ZFS tuning and it was a four fold increase
on the defaults.
Sorry for the noise.
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://list
is so long ago... It might have been tuning for our postgres
servers.
It might be worth while putting in a sanity check that doesn't allow
hirunningspace to be set lower than lorunningspace.
Thanks for your patience.
Ian
--
Ian Freislich
___
ave a preferred method for handling running
daenmons on uninstall? I know that Linux will even start daemons
on install.
Ian
--
Ian Freislich
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubs
nter.h. I don't know which is the correct fix.
Ian
--
Ian Freislich
___
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"
sonally, I'd rather that the package management system ports,pkg,etc
doesn't take liberties with my running daemons. If I want to kill
them off, I'll kill them off, but there have been several times
where I've left uninstalled things running while the system was in
flux during a
601 - 700 of 866 matches
Mail list logo
