Eric P Liedtke [EMAIL PROTECTED] writes:
Warning: devsm() called on 154/0
Warning: Driver mistake: destroy_dev on 154/0
panic don't do that
Please refer to the first paragraph of section 19.2.1.4 in the
handbook.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail
/dev, how do you plan to open the console ?
Mkdir(/dev) isn't an option because the rootfs is mounted R/O.
You could modify devfs so it can be union-mounted on top of /; or you
could hack namei to return a fake vnode for /dev so it's always
present.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED
such
questions. Please use [EMAIL PROTECTED] or [EMAIL PROTECTED]
instead.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
affected by changes in the kernel. The stuff that usually breaks when
your kernel is out of synch (ps, top, ipfw...) isn't needed to build
world. Of course, there are exceptions, like trying to run a 4.x or
5.x world on a pre-sigset_t kernel.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED
is still there
before you ask the lists about it.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
output I added to linux_ioctl.c,
and it's supposed to print an interface name after on.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Bruce Evans [EMAIL PROTECTED] writes:
On 12 Oct 2001, Dag-Erling Smorgrav wrote:
Remove UCONSOLE from kernel config. This has been discussed to death
several times on the lists.
That only prevents non-root from triggering the bug.
True. The only thing I know of that uses TIOCCONS apart
the error message it got from the server.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
, thanks for the warning.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
August 22 (which has issues with the syncer, causing horrible
interrupt latency, but at least it doesn't panic every ten minutes or
so).
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
}' .kgdb.temp
source .kgdb.temp
add-symbol-file $arg0 $kld-address + $offset
end
end
document kldload
Loads a module. Arguments are module name and offset of text section.
end
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
0x80b2962 in ?? ()
#36 0x80617c7 in ?? ()
#37 0x80610e3 in ?? ()
#38 0x8060a3e in ?? ()
#39 0x283cdb08 in ?? ()
#40 0x283cd91a in ?? ()
#41 0xbfbffae8 in ?? ()
#42 0x0 in ?? ()
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
*** Error code 1
Stop in /usr/src/gnu/lib/csu.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
I'd also like to know why it took *six hours* to get there on a 350
MHz K6-2 with 512 MB RAM.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED
to import
tdbm.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
[EMAIL PROTECTED] (Joerg Wunsch) writes:
Do you have any further input? Does fdformat still work? Does
fdread -I 1 return you a sector ID?
Fdread seems to work, fdformat just hangs.
root@des ~# fdread -I 1
C = 0, H = 0, R = 2, N = 2
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED
Bruce Evans [EMAIL PROTECTED] writes:
On 8 Jul 2001, Dag-Erling Smorgrav wrote:
My -DNOPERL build broke in games/fortune in the building everything
phase because the Alpha compiler tried to use the i386 strfile.o that
was left over from the bootstrap phase.
This shouldn't happen
Bruce Evans [EMAIL PROTECTED] writes:
[explaining how to build an LP64 world on i386]
I just had a major doh moment...
# cd /usr/src
# make MACHINE_ARCH=alpha buildworld /var/log/world.alpha
[1] 13655
Ought to catch any Alpha WARNS fuckups. Or did I overlook something?
DES
--
Dag-Erling
/fortune in the building everything
phase because the Alpha compiler tried to use the i386 strfile.o that
was left over from the bootstrap phase.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
Jens Schweikhardt [EMAIL PROTECTED] writes:
-current as of Jun 17, even with an updated sysctl.c revision 1.36,
prints garbage when used with -A:
Remove the line that says offset--; near the end of
sys/vm/vm_zone.c.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
Jens Schweikhardt [EMAIL PROTECTED] writes:
-current as of Jun 17, even with an updated sysctl.c revision 1.36,
prints garbage when used with -A:
Remove the line that says offset--; near the end of
sys/vm/vm_zone.c.
Ick, what am I saying
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
)
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
David O'Brien [EMAIL PROTECTED] writes:
OR build a 64-bit long (LP64) x86 gcc and test compile with that also.
BDE found *lots* of 64-bit dirty code using this technique.
Mind revealing how that's done?
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
(when working on userland code) Alpha, IA64 and Sparc64 will
be equivalent, as will i386 and PowerPC.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Matthew Jacob [EMAIL PROTECTED] writes:
There is, in my mailbox, a grotesque and unforgiveable insult from you
from some months back. You deserve no respect whatsoever.
Heh. You're so cute.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED
: lockmgr: locking against myself
[ad nauseam]
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
June 5th doesn't work (dumps core when it gets to crt1.c). Today's
won't build anything at all.
I think I've found the problem - what doesn't work is:
- building crt1.c with -fno-builtin
- building anything with gcc compiled with -fno-builtin
Mark Murray [EMAIL PROTECTED] writes:
I want to remove S/Key from CURRENT completely, and replace it
with OPIE where necessary.
How will this affect OpenSSH's SKeyAuthentication option, which is
required for certain types of token-based authentication (like
CryptoCard)?
DES
--
Dag-Erling
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
I think I've found the problem - what doesn't work is:
- building crt1.c with -fno-builtin
- building anything with gcc compiled with -fno-builtin
Ah, no, I understand now: crt1 is the first item to be built in the
libraries stage
In recent versions of -CURRENT, gcc built with CPUTYPE set to k6-2
will dump core when compiling specific source files (crt1.c at least),
and in the very latest -CURRENT, when compiling anything at all. So
far, gcc built with CPUTYPE set to i586 seem to work fine.
DES
--
Dag-Erling Smorgrav
David O'Brien [EMAIL PROTECTED] writes:
On Thu, Jun 21, 2001 at 12:37:00AM +0200, Dag-Erling Smorgrav wrote:
In recent versions of -CURRENT, gcc built with CPUTYPE set to k6-2
will dump core when compiling specific source files (crt1.c at least),
and in the very latest -CURRENT, when
Terry Lambert [EMAIL PROTECTED] writes:
So we removed it from the kernel config... and the damn
thing enabled it again.
You're thinking of ATA_ENABLE_ATAPI_DMA, which is only for ATAPI
devices (i.e. CD-ROMs), not for disks.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send
Jonathan Smith [EMAIL PROTECTED] writes:
I am thinking of what _was_ 'sysctl hw.atamodes' (or similar) in -STABLE.
You are not Terry.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I've converted linprocfs to use the pseudofs framework. Unfortunately
this means that proc/pid/cmdline and proc/pid/mem are currently
disabled as they rely on code from procfs, which hasn't been converted
yet. I'll try to remedy this as soon as possible.
DES
--
Dag-Erling Smorgrav - [EMAIL
drive. Most (nearly all) of
that time is spent in phase 2.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
-Erling Smorgrav - [EMAIL PROTECTED]
#include sys/types.h
#include sys/mman.h
#include stdlib.h
#include unistd.h
#define CHUNKSIZE 1048576
#define CHUNKS 4096
int
main(int argc, char *argv[])
{
int i, j, n, ps;
char *p;
n = (argc 1) ? atoi(argv[1]) : CHUNKS;
ps
), and one triggered a little later that kills any
process that doesn't catch it.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
mmap() an
amount of memory larger than RAM + swap and touch every page. Even
then, the result will be a SIGSEGV, not a graceful termination.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Dennis Glatting [EMAIL PROTECTED] writes:
On Monday 07 May 2001 08:10 am, Dag-Erling Smorgrav wrote:
malloc() will return NULL only if you hit a resource limit or exhaust
address space. There may or may not be memory (real or virtual)
available at that time.
Isn't memory exhaustion
.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
), and to the bugginess of his code.
BTW, I was wrong - his code doesn't smash the malloc() arena, because
the termination condition in the if loop guarantees it never makes
more than one iteration.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED
Dennis Glatting [EMAIL PROTECTED] writes:
On 7 May 2001, Dag-Erling Smorgrav wrote:
Dennis Glatting [EMAIL PROTECTED] writes:
On Monday 07 May 2001 08:10 am, Dag-Erling Smorgrav wrote:
malloc() will return NULL only if you hit a resource limit or exhaust
address space. There may
location of the ssh host key files has been
changed from /etc/ssh to /etc. Was it intentional?
That has been fixed.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
) show up on -STABLE, but result in an immediate core dump on
-CURRENT because it has malloc() debugging enabled by default.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
.
Hmm, I might try that.
BTW, last time I asked Warner about this his reply was (I paraphrase)
it's not supposed to work, and if it ever worked for you it was out
of sheer luck, which I find surprising.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED
Peter Jeremy [EMAIL PROTECTED] writes:
Is there any progress on fixing this?
I posted a patch a couple of months ago. Search the archives.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
in question not configured in the kernel.
Wrong (well, it depends on your definition of configured).
AIUI such
messages are currently disabled unless one boots in verbose mode.
Wrong.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe
work fine, no longer does.
I'll try the latest greatest and see if the problem goes away.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[EMAIL PROTECTED] writes:
Trying to mount a music cd might cause the atapi code to try to read
9408 bytes into a 8192 bytes long buffer.
That's not it. There was a music CD in the drive, but no attempt was
made to mount it - I wasn't even there when it crashed.
DES
--
Dag-Erling Smrgrav -
Got this on sunday on my laptop (400 MHz PII running a week-old
-CURRENT):
root@aes /var/crash# gdb -k
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under
patch can affect the functionality of your
network adapter, and network interfaces don't care about DEVFS.
Has this or another fix been committed?
No, Certain People [tm] are opposed to it, though it's not clear why.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail
"Michael C . Wu" [EMAIL PROTECTED] writes:
(DES: please resist the ironies and the -chat post ;) )
Huh? what did I say?
DES (make it look like the cat did it)
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
"Edwin L. Culp" [EMAIL PROTECTED] writes:
One of the error messages was that card0 didn't exist in /dev
That's pccard stuff, not your network driver. Did you check to see
that the pccard bridge was probed and attached?
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe:
*) CMAP2 = 0;
}
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
p rendezvous
mcount
db panic
panic: from debugger
cpuid = 1; lapic.id = 0100
boot() called on cpu#1
Uptime: 22s
dumping to dev da3b, offset 1048576
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
milar crash for you, I've left an x86 binary of ex6
at http://www.cs.duke.edu/~gallatin/ex6.x86
Thanks, I'll give it a whirl.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
Andrew Gallatin [EMAIL PROTECTED] writes:
Where does witness_enter+0x355 map to, in terms of line numbers?
root@rsa /var/crash# gdb -k
[...]
Argh! Please ignore this, the machine gdb was running on had an old
source tree. I'll get a correct
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
Try this workaround (apply with 'patch -l'):
Here's a better workaround. Revert the previous patch and apply this
one:
Index: npx.c
===
RCS file: /home/ncvs/src/sys/i386/isa/npx.c,v
the stack got corrupted
while handling that fault (possibly somewhere in pmap_zero_page(),
called from vm_page_zero_fill() which is inlined in vm_fault()).
(BTW, this is a K6-2, which as far as I can tell is a 586-class CPU)
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [
in the backtrace.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ad0a
ad0s1: type 0xa5, start 0, end = 19746719, size 19746720 : OK
start_init: trying /sbin/init
ad1s1: type 0xa5, start 0, end = 17840695, size 17840696 : OK
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
mode.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I've never done that on FreeBSD and couldn't find a
nicer way then sticking boot_single="YES" in /boot/loader.conf...
Any pointer anybody (private email)?
Interrupt the boot loader's countdown and type 'boot -s'.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail
Pascal Hofstee [EMAIL PROTECTED] writes:
With a CURRENT build/installworld from yesterday ... i get a VERY unstable
system that page faults under the slightest CPU load (e.g. playing MP3's)
What kind of CPU?
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
remembered I have a dual Pentium box I use for SMP work,
but haven't booted in several weeks... because it keeps crashing...
with a smashed stack.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
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 - [EMAIL
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-cu
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 maintainer for review
don't
think that qualifies as file corruption. As far as I could see, no
files were damaged - only one of the gnats subdirectories.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Matt Dillon [EMAIL PROTECTED] writes:
How old a kernel are you running?
Maybe five days old.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
the machine rebooted, fsck complained of an unexpected
softupdates inconsistency. It turned out the /usr/gnats directory had
empty blocks in it and had to be truncated - a sizeable portion of the
GNATS database ended up in /lost+found.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe
interlock @ ../../ufs/ffs/ffs_vfsops.c:948
This is a known (and probably benign) bug.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
"Alexander N. Kabaev" [EMAIL PROTECTED] writes:
Do you have WITNESS_SKIPSPIN option in your kernel config?
Yes.
Here is what supposedly causing the trouble:
You're telling the guy who did the analysis.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail
ip_inq
lo
ufs ihash
ifsvgt
cd9660_ihash
vnode_free_list
spechash
mntid
mntvnode
mountlist
ed
bpf interface lock
xl
buftime lock
vm object_list
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Alfred Perlstein [EMAIL PROTECTED] writes:
Vinum+DEVFS doesn't make the million symlinks that non-devfs
vinum does.
Why not? make_dev_alias() is cheap and easy to use.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fr
I fixed the bug in linux_clone() that made caused the 'not SRUN'
panics in -CURRENT. Opera, Tivoli and other threaded Linux apps should
now work again.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
uot;.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Matthew Jacob [EMAIL PROTECTED] writes:
Hmm. Sounds to me more like an argument for requiring devfs if you
use vinum.
Not until vinum works equally well with devfs as without it.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
Mikhail Teterin [EMAIL PROTECTED] writes:
Here is the trace with my attempts to browse through it.
If you can, please reproduce the panic on a kernel compiled with the
INVARIANTS, INVARIANT_SUPPORT and WITNESS options.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send
it. And get acquainted with the
issue at hand before joining the discussion.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
it doesn't really
harvest entropy at all, and I suspect it of smashing the stack. Try
again with the new code.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Mark Murray [EMAIL PROTECTED] writes:
Is DEBUG defined?
Nope.
DES
--
Dag-Erling Smrgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
7 6 5 4 3 2 1 0 succeeded
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
went
backwards 536 - 444
This has been a known problem for several months now. Please do not
run -CURRENT unless you follow the freebsd-current mailing list
closely.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
db trace
kernel: type 12 trap, code=0
Blah. Here's what gdb says:
(kgdb) where
#0 dumpsys () at ../../kern/kern_shutdown.c:478
#1 0xc019131b in boot (howto=260) at ../../kern/kern_shutdown.c:321
#2 0xc01916e5 in panic (fmt=0xc02940b4 "
apno = 12, tf_err = 2, tf_eip = 678761248,
tf_cs = 31, tf_eflags = 647, tf_esp = 142872400, tf_ss = 47})
at ../../i386/i386/trap.c:1184
1184error = (*callp-sy_call)(p, args);
(kgdb) up
#15 0xc026690d in syscall_with_err_pushed ()
(kgdb) up
#16 0x285cac35 in ?? ()
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
/~chart/download/pnpid.txt
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
problem before in -current, it's probably
something simliar.
Sounds likely. On my laptop, the "giving up on n buffers" message is
usually accompanied by an ata0 timeout.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
John Baldwin [EMAIL PROTECTED] writes:
On 22-Feb-01 Maxim Sobolev wrote:
Dag-Erling Smorgrav wrote:
Maxim Sobolev [EMAIL PROTECTED] writes:
It's not an ata specific problem, but rather a problem of all ISA
devices (I have an ISA based ata controller).
I don't think it has
is a bad idea, BTW, there's a (presumably harmless) lock
order reversal in the FS code that you're practically guaranteed to to
hit during boot.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
own option `FFS_ROOT' removed from
/usr/obj/home/src/sys/DCS/opt_ff
s.h
Neither KERNFS nor FFS_ROOT exist any more. The warning about FFS is
correct.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
is probably a bug in the preemption code.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
) goes to great lengths to determine
the actual dependencies of a specific port. You might have better luck
trying to hack an update function into porteasy than using pkg_update.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fr
"David O'Brien" [EMAIL PROTECTED] writes:
On Tue, Feb 13, 2001 at 05:18:04AM +0100, Dag-Erling Smorgrav wrote:
Donny Lee [EMAIL PROTECTED] writes:
===ipfilter
make: don't know how to make machine/lock.h Stop.
*** Error code 2
Looks like a stale dependency file to me.
. It only accidentally works because you always use 'config -r'.
The correct command is 'make depend make make install'. If you
do 'make depend all', the dependency information generated by the
'depend' target is ignored by the 'all' target.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED
Donny Lee [EMAIL PROTECTED] writes:
Dag-Erling Smorgrav wrote:
config -r mykernel
No point.
-r removes objects generated by a previous kernel config, i guess.
Still no point. Unless your tree is hosed, make(1) takes care of that,
as long as you don't screw up by running all three
Jake Burkholder [EMAIL PROTECTED] writes:
As I mentioned in the commit message, this changes the size and layout
of struct kinfo_proc, so you'll have to recompile libkvm-using programs.
I thought the whole point with kinfo_proc was to avoid this kind of
situation...
DES
--
Dag-Erling
Warner Losh [EMAIL PROTECTED] writes:
Alternatively, the upgrade path must be fixed.
I don't see any way to do that. Everything on your system that isn't
statically linked will need to be recompiled unless the libc major
number is bumped.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED
801 - 900 of 1088 matches
Mail list logo
