OK. I have pushed 4 series of commits. (1) remove sccs IDs by and large (a
couple of exceptions where @(#) didn't mark an SCCS id). (2) remove if 0'd
copyright strings. (3) Mechanical changes to most of the tree to cleanup
style divots after these changes (and the $FreeBSD$ removal) (4) cdefs.h
cle
> Hello,
>
> I decided to try to run some bhyve VM's on my machine and bridge
> them to a guest vlan on my main interface. I also want to support
> running bhyve VM's on the untagged part of the interface as well
> (this is the key problem as I'll describe later).
>
> I configure it as you'd exp
Rodney W. Grimes wrote this message on Fri, Nov 24, 2017 at 18:26 -0800:
> > I decided to try to run some bhyve VM's on my machine and bridge
> > them to a guest vlan on my main interface. I also want to support
> > running bhyve VM's on the untagged part of the interface as well
> > (this is the
Hello,
I decided to try to run some bhyve VM's on my machine and bridge
them to a guest vlan on my main interface. I also want to support
running bhyve VM's on the untagged part of the interface as well
(this is the key problem as I'll describe later).
I configure it as you'd expect. Bridge the
On 5/23/16 9:45 AM, Bryan Drewery wrote:
> On 5/22/16 1:21 PM, Shawn Webb wrote:
>> Hey All,
>>
>> I’m getting this error when doing `make installworld` on recent builds of
>> HEAD. It seems that the error is non-critical as installworld doesn’t
>> actually error out. I’m running HardenedBSD 11-C
On 5/22/16 1:21 PM, Shawn Webb wrote:
> Hey All,
>
> I’m getting this error when doing `make installworld` on recent builds of
> HEAD. It seems that the error is non-critical as installworld doesn’t
> actually error out. I’m running HardenedBSD 11-CURRENT on amd64.
>
> sh: tail: not found
> mak
On Sun, May 22, 2016 at 04:02:43PM -0700, Conrad Meyer wrote:
> FreeBSD has tail(1). Does HardenedBSD remove it? Or is /usr/bin
> missing from your PATH?
>
I noticed this with a straight vanilla FreeBSD build/install, but
have been busy with "other things" today.
It appears to me that the
FreeBSD has tail(1). Does HardenedBSD remove it? Or is /usr/bin
missing from your PATH?
On Sun, May 22, 2016 at 1:21 PM, Shawn Webb wrote:
> Hey All,
>
> I’m getting this error when doing `make installworld` on recent builds of
> HEAD. It seems that the error is non-critical as installworld do
HardenedBSD has it and it’s in /usr/bin. The only utilities that aren’t
compiled by default in HardenedBSD are freebsd-update and portsnap.
Thanks,
Shawn Webb
Cofounder and Security Engineer
HardenedBSD
GPG Key ID: 0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E
Hey All,
I’m getting this error when doing `make installworld` on recent builds of HEAD.
It seems that the error is non-critical as installworld doesn’t actually error
out. I’m running HardenedBSD 11-CURRENT on amd64.
sh: tail: not found
make[4]: "/usr/src/share/mk/bsd.compiler.mk" line 151: wa
Alexander V. Chernikov wrote this message on Thu, Jan 09, 2014 at 15:04 +0400:
> On 09.01.2014 05:18, John-Mark Gurney wrote:
> >Well, I was trying to manually add a route for a host on the local
> >network (I can explain why, but it doesn't matter) and I got this:
> Hello!
> There are several diff
On 09.01.2014 05:18, John-Mark Gurney wrote:
Well, I was trying to manually add a route for a host on the local
network (I can explain why, but it doesn't matter) and I got this:
Hello!
There are several different kernel & userland bugs :)
# netstat -rnfinet
Routing tables
Internet:
Destinati
Well, I was trying to manually add a route for a host on the local
network (I can explain why, but it doesn't matter) and I got this:
# netstat -rnfinet
Routing tables
Internet:
DestinationGatewayFlagsNetif Expire
default192.168.0.14 UGS re0
127.0.0.
On Sun, Sep 8, 2013 at 4:27 PM, Sean Bruno wrote:
> On Sat, 2013-09-07 at 17:05 +0200, Davide Italiano wrote:
>> On Fri, Sep 6, 2013 at 6:00 PM, Sean Bruno wrote:
>> > Our "yBSD" builder needs to mount a disk image temporarily that has a
>> > dos partition (for openstack-ish things) to put config
On Sat, 2013-09-07 at 17:05 +0200, Davide Italiano wrote:
> On Fri, Sep 6, 2013 at 6:00 PM, Sean Bruno wrote:
> > Our "yBSD" builder needs to mount a disk image temporarily that has a
> > dos partition (for openstack-ish things) to put configs into it. It
> > seems that under high stress, we can
On Fri, Sep 6, 2013 at 6:00 PM, Sean Bruno wrote:
> Our "yBSD" builder needs to mount a disk image temporarily that has a
> dos partition (for openstack-ish things) to put configs into it. It
> seems that under high stress, we can squeeze a panic out of it in
> namei().
>
> Sean
>
>
> Unread port
Our "yBSD" builder needs to mount a disk image temporarily that has a
dos partition (for openstack-ish things) to put configs into it. It
seems that under high stress, we can squeeze a panic out of it in
namei().
Sean
Unread portion of the kernel message buffer:
panic: namei: nameiop contaminat
Very interesting! Thanks
On Fri, Oct 1, 2010 at 4:05 PM, Andre Oppermann wrote:
> Just saw the link to a very interesting paper on SMP scalability.
> A very good read and highly relevant for our efforts as well. In
> certain areas we may already fare better, in others we still have
&g
Just saw the link to a very interesting paper on SMP scalability.
A very good read and highly relevant for our efforts as well. In
certain areas we may already fare better, in others we still have
some work to do.
An Analysis of Linux Scalability to many Cores
ABSTRACT
This paper analyzes the
Hi,
Bug report sais:
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/144786
bsdtar(1) doesn't support multi line matching or it is broken.
This patch [1] should solve it but not sure about this line in the
original code:
if (lr->nullSeparator) {
...
}
This is constant '\n' so this code par
Hi,
Hardware is a Supermicro p4ce+, with 2x2.0Ghx HTT capable xeons with HHT
disabled. Running with all debug options in the kernel turned off (i.e
no INVARIANTS, KGDB, etc).
As for linux - went to Mandrake 9.2 Beta with 2.2.22, currently running
2.6.0-test7. Both ran fine. I tend to switch back
On Sat, 11 Oct 2003, Brendon and Wendy wrote:
> Hi,
>
> Just saw the talk about sched_ule, nvidia driver, moused and pauses...
>
> I was running -current up until about a month ago, using the nvidia
> driver, sched_bsd on a dual ht xeon, with htt disabled. Mouse
> interactivity with moused was ter
Hi,
Just saw the talk about sched_ule, nvidia driver, moused and pauses...
I was running -current up until about a month ago, using the nvidia
driver, sched_bsd on a dual ht xeon, with htt disabled. Mouse
interactivity with moused was terrible - I actually thought the mouse
was faulty. Getting ri
know it's due to the file date, but
that's quite an interesting way of saying that.
BTW, yes the date on my computer is fine. it must have been the ftp
server I grabbed it off of.
My only real comment on this, was the way it said it. Maybe we could
have made it more informational t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 06 June 2003 14.21, Soeren Schmidt wrote:
>
> Get me a 3112 based controller on my desk :)
>
If this is an option, let me know what make and model you would need and I
will make sure we get a sponsor for such a controller from the sponsor o
> >
> > There is no ATA support that is not included in the stock GENERIC
> > kernel, so I'm not sure what you mean here ?
> > It would be helpfull to know what controller and disk we are talking
> > about, 'a' SATA controller and disk isn't really h
e helpfull to know what controller and disk we are talking
about, 'a' SATA controller and disk isn't really helpfull :)
Interesting... I thought for certain someone had told me there was a
driver
for the Silicon Image Sil 3112A Controller in FreeBSD.
The disk is a West
It seems David Leimbach wrote:
> So... I have this nice SATA drive and controller which I believe is
> supported
> by FreeBSD but not in the default build for releases.
>
> What is the best way to cross-build a version of FreeBSD's release ISOs
> that
> will include drivers not included in the d
So... I have this nice SATA drive and controller which I believe is
supported
by FreeBSD but not in the default build for releases.
What is the best way to cross-build a version of FreeBSD's release ISOs
that
will include drivers not included in the default distribution? Or is
it possible
to s
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
-
This email was sent
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
-
This email was sent
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
-
This email was sent
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
-
This email was sent
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
-
This email was sent
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
-
This email was sent
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
-
This email was sent
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
FUCK SCOTT LONG AND FUCK BILL FUMEROLA
-
This email was sent
When playing with jail earlier, I found an interesting bug in devfs. After
playing with devfs a bit more, I found that jail isn't necessary to cause
the bug to show itself. Here's a copy of the session. The problem should be
obvious.
edgemaster# uname -a
FreeBSD edgemaster.zombie.org 5
On Thu, Jul 18, 2002 at 01:40:48PM -0400, Bosko Milekic wrote:
> As pointed out, the change was fairly bogus. There's a new change
> that should be committed soon that fixes the problem in a "sort of"
> less bogus way. When Peter gets around to reviewing it, it'll be
> committed and you
On Thu, Jul 18, 2002 at 07:38:39PM +0200, Szilveszter Adam wrote:
> Hello everybody,
>
> I would like to report that after incorporating today's fixes into the
> kernel source and recompiling, the panic does not occur again.
>
> This is probably due to the commit to pmap.c (rev 1.345 by Peter W
Hello everybody,
I would like to report that after incorporating today's fixes into the
kernel source and recompiling, the panic does not occur again.
This is probably due to the commit to pmap.c (rev 1.345 by Peter Wemm).
Although the log only talks about SMP, this UP box likes it too.
So anyw
> That there could be a real error in that code surprises me, since
> Peter really knows what he's doing, even if that low in the
> hardware, there are undocumented interactions that even Intel's
> errata doesn't seem to know about.
Turns out the workaround is to use DISABLE_PG_G.
Two things mad
Szilveszter Adam wrote:
> On Wed, Jul 17, 2002 at 11:35:35AM -0700, Terry Lambert wrote:
> > My bet on the root cause, if I am correct, means that if you change
> > the amount of physical RAM installed in the machine, the problem will
> > go away, and that the problem is probably rare because it d
On Wed, Jul 17, 2002 at 11:35:35AM -0700, Terry Lambert wrote:
> My bet on the root cause, if I am correct, means that if you change
> the amount of physical RAM installed in the machine, the problem will
> go away, and that the problem is probably rare because it depends on
> certain things that
On Wed, Jul 17, 2002 at 07:38:22PM +0200, Szilveszter Adam wrote:
> Bakul mentioned that the panic happens on a PPro. For me, it's a PII. I
> am using a CPUTYPE setting of "p2" in /etc/make.conf. This gets
> converted to a "-march=pentiumpro" on the actual compile line. This may
> be the same for
Szilveszter Adam wrote:
> Ok, so it's time to speculate a bit more about this.
>
> Although I have been seeing this panic since Sunday, only one other
> person has reported it so far. Although it may be that this is due to
> the fact that developers do not run up-to-date -CURRENT and hence do not
Bakul Shah wrote:
> > I believe setting DISABLE_PSE in the config file and rebuilding
> > will make this go away.
>
> Terry, thanks for the suggestion but that didn't do it.
This surprises me. I thought it would be the result of Peter's
recent pmap changes, and the fact that there is a bad prob
On Wed, Jul 17, 2002 at 09:57:41AM -0700, Bakul Shah wrote:
Terry suggested:
> > I believe setting DISABLE_PSE in the config file and rebuilding
> > will make this go away.
>
> Terry, thanks for the suggestion but that didn't do it.
Ok, so it's time to speculate a bit more about this.
Although
> I believe setting DISABLE_PSE in the config file and rebuilding
> will make this go away.
Terry, thanks for the suggestion but that didn't do it.
Time to review recent changes and single step the kernel.
BTW, how do you stop the kernel before it panics? It
panics so early that there is no time
Bakul Shah wrote:
> I've run into a very similar bug -- the kernel panics almost
> right after it is started by the loader. With remote gdb
> I've traced it to this point so far:
I believe setting DISABLE_PSE in the config file and rebuilding
will make this go away.
-- Terry
To Unsubscribe: se
I've run into a very similar bug -- the kernel panics almost
right after it is started by the loader. With remote gdb
I've traced it to this point so far:
(kgdb) target remote /dev/cuaa0
Remote debugging using /dev/cuaa0
pmap_set_opt () at /usr/src/sys/i386/i386/pmap.c:449
449
you can use addr2line to get info, but
at a pinch you can just use nm -n to figure out what function each address
is in.
On Sun, 14 Jul 2002, Szilveszter Adam wrote:
> Hello everybody,
>
> I have recently finished to upgrade my system to today morning's
> -CURRENT, with sources just *before* t
On Sun, Jul 14, 2002 at 08:06:49PM +0200, Szilveszter Adam wrote:
> On Sun, Jul 14, 2002 at 07:49:57PM +0200, Szilveszter Adam wrote:
> > Hello everybody,
> >
> > I have recently finished to upgrade my system to today morning's
> > -CURRENT, with sources just *before* the commit of rev 1.154 to
>
On Sun, Jul 14, 2002 at 07:49:57PM +0200, Szilveszter Adam wrote:
> Hello everybody,
>
> I have recently finished to upgrade my system to today morning's
> -CURRENT, with sources just *before* the commit of rev 1.154 to
> src/sys/kern/kern_fork.c by Julian.
>
> I have an UP IA32 machine, I am no
Hello everybody,
I have recently finished to upgrade my system to today morning's
-CURRENT, with sources just *before* the commit of rev 1.154 to
src/sys/kern/kern_fork.c by Julian.
I have an UP IA32 machine, I am not using any additional kernel modules,
and now, upon rebooting with the new kern
In the last episode (Jun 27), Szilveszter Adam said:
> On Thu, Jun 27, 2002 at 12:13:39PM -0700, Juli Mallett wrote:
> > If no file is specified for nm to operate on it operates on a.out
> > by default like most other programs that deal with binaries.
> >
> > If a.out does not exist, then you wil
On Thu, Jun 27, 2002 at 12:13:39PM -0700, Juli Mallett wrote:
> If no file is specified for nm to operate on it operates on a.out by default
> like most other programs that deal with binaries.
>
> If a.out does not exist, then you will indeed see that.
Thanks for the clarification, I expected it
atthew Dillon
> > > <[EMAIL PROTECTED]>
> > >
> > >
> >
> > Everything works great with the fix.
>
> Which exposes another interesting problem.
>
> If I issue 'nm -v', it says:
>
> /usr/libexec/elf
* Szilveszter Adam <[EMAIL PROTECTED]> escriuréres
> > Everything works great with the fix.
>
> Which exposes another interesting problem.
>
> If I issue 'nm -v', it says:
>
> /usr/libexec/elf/nm: a.out: No such file or directory
If no file is speci
Matthew Dillon
:> ><[EMAIL PROTECTED]>
:> >
:> >
:>
:> Everything works great with the fix.
:
:Which exposes another interesting problem.
:
:If I issue 'nm -v', it says:
:
:/usr/libexec/elf/nm: a
<[EMAIL PROTECTED]>
> >
> >
>
> Everything works great with the fix.
Which exposes another interesting problem.
If I issue 'nm -v', it says:
/usr/libexec/elf/nm: a.out: No such file or directory
This system was last upgrad
Yeah, I'm also using the SMP kernel.
Dan Nelson wrote:
> In the last episode (Jan 28), Jim Bryant said:
>
>>Oh yeah, I immediately did a shutdown with reboot, and the problem
>>did not duplicate itself.
>>
>>Jim Bryant wrote:
>>
>>
>>>After upgrading -current, then reverting back to the previou
In the last episode (Jan 28), Jim Bryant said:
> Oh yeah, I immediately did a shutdown with reboot, and the problem
> did not duplicate itself.
>
> Jim Bryant wrote:
>
> >After upgrading -current, then reverting back to the previous [more
> >stable] kernel, upon rebooting after reverting, I not
Oh yeah, I immediately did a shutdown with reboot, and the problem did not duplicate
itself.
Jim Bryant wrote:
> After upgrading -current, then reverting back to the previous [more
> stable] kernel, upon rebooting after reverting, I noticed the oddest
> thing on ttyv0. Apparently, after /etc
After upgrading -current, then reverting back to the previous [more stable] kernel,
upon rebooting after reverting, I noticed the
oddest thing on ttyv0. Apparently, after /etc/rc took over in init all of the text
was still in the kernel color scheme.
FreeBSD wahoo.kc.rr.com 5.0-CURRENT FreeBS
Leif Neland <[EMAIL PROTECTED]> writes:
> > (kgdb) kernel 1
> Because that command doesn't work for me..
exec-file kernel.1
symbol-file symbols.1
core-file vmcore.1
(where symbols.1 is a copy kernel.debug)
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROT
On 18 Mar 2001, Dag-Erling Smorgrav wrote:
> Anyway, here's the backtrace:
>
> root@des /var/crash# gdb -k
...
> This GDB was configured as "i386-unknown-freebsd".
> (kgdb) source ~des/kgdb <-- What's in here?
I guess it is commands to load the crash dump into the debugger.
Could you post it,
> On Wed, Mar 21, 2001 at 11:16:01PM +, David Malone wrote:
> > The graph seems to peak at about 160kB/s, which seems plausable.
> > The code is at:
> >
> > http://www.maths.tcd.ie/~dwmalone/comp/-time.S
> > http://www.maths.tcd.ie/~dwmalone/comp/-time.c
> http://www.maths.tcd.ie/~dw
On Wed, 21 Mar 2001, David Malone wrote:
> On Mon, Mar 19, 2001 at 02:47:34PM +1100, Bruce Evans wrote:
> > > npx.c already has one "fix" for the overflow problem. The problem
> > > is may be that clocks don't work early any more.
> >
> > It must be that microtime() doesn't work early any more.
On Mon, Mar 19, 2001 at 02:47:34PM +1100, Bruce Evans wrote:
> > npx.c already has one "fix" for the overflow problem. The problem
> > is may be that clocks don't work early any more.
>
> It must be that microtime() doesn't work early any more.
I did a quick check, and it does seem that i586_bz
On Mon, 19 Mar 2001, Jake Burkholder wrote:
[bde wrote]
> > Wrong yourself. The fpu is too slow to use for copying for everything
> > except original Pentiums. The bandwidth test is just done to avoid hard-
> > configuring this knowledge.
>
> If this is the case, is there much point in keeping
> On 19 Mar 2001, Dag-Erling Smorgrav wrote:
>
> > Bruce Evans <[EMAIL PROTECTED]> writes:
> > > K6-2's aren't really i586's and i586_bzero should never be used for
> > > them (generic bzero is faster),
> >
> > Wrong. I fixed machdep.c to compute and print the bandwidth correctly:
>
> Wrong you
On 19 Mar 2001, Dag-Erling Smorgrav wrote:
> Bruce Evans <[EMAIL PROTECTED]> writes:
> > On 19 Mar 2001, Dag-Erling Smorgrav wrote:
> > > Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> > > > Wrong. I fixed machdep.c to compute and print the bandwidth correctly:
> > > I mean npx.c. I'll commit
On 19 Mar 2001, Dag-Erling Smorgrav wrote:
> Anyway, the bug is not K6-specific - I guess the reason why we're only
> seeing it on K6's is that they're the only 586-class CPUs that are
> fast enough to still be in widespread use.
I have the same panics in one of my pentium 166 mmx boxes. Even som
Bruce Evans <[EMAIL PROTECTED]> writes:
> On 19 Mar 2001, Dag-Erling Smorgrav wrote:
> > Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> > > Wrong. I fixed machdep.c to compute and print the bandwidth correctly:
> > I mean npx.c. I'll commit the fix in a second.
> Please send it to the maintaine
On 19 Mar 2001, Dag-Erling Smorgrav wrote:
> Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> > Wrong. I fixed machdep.c to compute and print the bandwidth correctly:
>
> I mean npx.c. I'll commit the fix in a second.
Please send it to the maintainer for review.
Bruce
To Unsubscribe: send m
On 19 Mar 2001, Dag-Erling Smorgrav wrote:
> Bruce Evans <[EMAIL PROTECTED]> writes:
> > K6-2's aren't really i586's and i586_bzero should never be used for
> > them (generic bzero is faster),
>
> Wrong. I fixed machdep.c to compute and print the bandwidth correctly:
Wrong yourself. The fpu is
On Mon, 19 Mar 2001, Bruce Evans wrote:
> K6-2's aren't really i586's and i586_bzero should never be used for
> them (generic bzero is faster), but there is apparently another
> bug that may cause them to be used. From des's dmesg output:
>
> > i586_bzero() bandwidth = -1980152482 bytes/sec
>
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> Wrong. I fixed machdep.c to compute and print the bandwidth correctly:
I mean npx.c. I'll commit the fix in a second.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curren
John Baldwin <[EMAIL PROTECTED]> writes:
> Can you throw some extra tests in there to make sure m isn't NULL? Also, you
> might want to check VM_PAGE_TO_PHYS(m) for any weird values.
No need - David and Jake already tracked it down to evilness in
i586_bzero().
DES
--
Dag-Erling Smorgrav - [EMA
Bruce Evans <[EMAIL PROTECTED]> writes:
> K6-2's aren't really i586's and i586_bzero should never be used for
> them (generic bzero is faster),
Wrong. I fixed machdep.c to compute and print the bandwidth correctly:
des@des ~% egrep '(CPU|bzero)' /var/run/dmesg.boot
CPU: AMD-K6(tm) 3D processor (
On 18-Mar-01 Dag-Erling Smorgrav wrote:
> I finally caught a backtrace from one of those recurring stack smash
> panics. I've been getting a few of these every day for a couple of
> weeks now but never caught a dump; I caught this one by typing 'panic'
> immediately instead of trying to get a tra
On Sun, 18 Mar 2001, David Malone wrote:
> Presumably what is happening is i586_bzero begins and finds that
> PCPU(NPXPROC) is not zero, so it decides to preserve the fpu
> registers. Then something interrupts it, but doesn't restore
> PCPU(NPXPROC). When i586_bzero returns it uses the first 8 by
On Sun, Mar 18, 2001 at 04:41:03PM +0100, Dag-Erling Smorgrav wrote:
> I finally caught a backtrace from one of those recurring stack smash
> panics. I've been getting a few of these every day for a couple of
> weeks now but never caught a dump; I caught this one by typing 'panic'
> immediately in
Verbose boot log as requested.
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #63: Sun Mar 18 22:21:49 CET 2001
[EMAIL PROTECTED
Valentin Nechayev <[EMAIL PROTECTED]> writes:
> I did not reported them yet because of lack of understanding
> what's happen because pmap_zero_page() call is occured in vm_fault()
> without this call in source code ;|
It's called by vm_page_zero_fill() which is inlined and therefore
doesn't show
Sun, Mar 18, 2001 at 16:41:03, des (Dag-Erling Smorgrav) wrote about "Interesting
backtrace...":
> I finally caught a backtrace from one of those recurring stack smash
> panics. I've been getting a few of these every day for a couple of
> weeks now but never caught a
On Sun, Mar 18, 2001 at 04:41:03PM +0100, Dag-Erling Smorgrav wrote:
> I finally caught a backtrace from one of those recurring stack smash
> panics. I've been getting a few of these every day for a couple of
> weeks now but never caught a dump; I caught this one by typing 'panic'
> immediately in
I finally caught a backtrace from one of those recurring stack smash
panics. I've been getting a few of these every day for a couple of
weeks now but never caught a dump; I caught this one by typing 'panic'
immediately instead of trying to get a trace at the ddb prompt first.
These panics invaria
>I also have a problem with my laptop that built world at the same
>time. Because
>of the above, I decided to restart it to put the kernel and programs in
>sync to
>see if that was causing the error. Murphy caught me in the act and my laptop
>now hangs on boot:-( I haven't tried rebooting an
With this morning's make world, I get the following error with man. I've checked
six different machines with slightly different cvsup and build times and using
different cvsup locations. They all coincide.
FreeBSD dsl.mexcomusa.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Jan 19
07:52:22 PST 2001
On Tue, Dec 19, 2000 at 09:56:36PM +0100, Ollivier Robert wrote:
> According to Donald J . Maddox:
> > open. Also, why the odd format in the addresses?
>
> Looks like some kind of IPv6 address...
You're right. I compiled the new kernel with IPV6 enabled. I
didn't have IPV6 in my previous kern
According to Donald J . Maddox:
> open. Also, why the odd format in the addresses?
Looks like some kind of IPv6 address...
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000
To Unsubscribe: send m
You're right that the answer to my question was IPV6 (I didn't have
it compiled into the previous kernel). You're wrong that a port
need not be open to receive connections. You will note in the
log excerpt below that these are connection *attempts*, not actual
connections.
On Tue, Dec 19, 2000
To answer your first question, a port need not be open in order to receive
connections. To answer your second, these appear to be IPv4 addresses
encapsulated as IPv6 addresses.
> Dec 19 12:21:04 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP
> ::0001:25 from ::0001:1286
> Dec 19
On Tue, Dec 19, 2000 at 07:33:49PM +0100, Szilveszter Adam wrote:
> On Tue, Dec 19, 2000 at 01:20:57PM -0500, Donald J . Maddox wrote:
> > After my latest update, I am getting LOTS of the following in my logs:
> >
> > Dec 19 12:21:04 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP
>
On Tue, Dec 19, 2000 at 01:20:57PM -0500, Donald J . Maddox wrote:
> After my latest update, I am getting LOTS of the following in my logs:
>
> Dec 19 12:21:04 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP
>::0001:25 from ::0001:1286
> Dec 19 12:24:08 cae88-102-101 /boot/kernel/ke
After my latest update, I am getting LOTS of the following in my logs:
Dec 19 12:21:04 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25
from ::0001:1286
Dec 19 12:24:08 cae88-102-101 /boot/kernel/kernel: Connection attempt to TCP ::0001:25
from ::0001:1299
Dec 19 12:27:13
After last night's new kernel and 'make world', I find I am seeing
some interesting new warnings at boot time:
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD
On Sat, 30 Sep 2000, Tony Johnson wrote:
> I must admit that I have been less then tactful about this thread. I
> apologize for this. This is my last response to this because once again
> this has gone on far too long.
>
> As far as this response goes. I sense "selective reading." I never sa
1 - 100 of 160 matches
Mail list logo
