Re: Labeling Vinum partitions in the sysinstall(8) [patch]
Maxim Sobolev wrote: John Baldwin wrote: On 02-Mar-01 Maxim Sobolev wrote: Hi folks, I'm currently creating a Vinum(4) configuration wizard for sysinstall(8), which would simplify Vinum configuration procedure for the vinum newbies. So far I finished a patch that allows create vinum partitions using sysinstall's disklabel editor and would like to commit it. Please review attached patches. Heh, I wrote http://www.FreeBSD.org/~jhb/patches/sysinstall.vinum.patch probably a year ago now, but because it only changes the disklabel editor and doesn't add a full vinum configurator the patch was rejected. :-/ Hopefully you will have better luck than I did... I hope so, because it greatly simplifies the task even without a full vinum configurator (as I said I'm working on it as well). Yeah, I know that disklabel(8) is cool, but it is not very intuitive and easy to use tool, especially for GUI-pampered win32 converts. So, we're impatiently awaiting your nice GUI-ish vinum configurator in Tcl/Tk, Python, Ruby, Perl, Java, or whatever. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems compiling kern_mutex.c
Matthew Thyer [EMAIL PROTECTED] writes: /usr/src/sys/kern/kern_mutex.c:593: warning: no previous prototype for `_mtx_ assert' /usr/src/sys/kern/kern_mutex.c: In function `_mtx_assert': /usr/src/sys/kern/kern_mutex.c:595: `MA_OWNED' undeclared (first use in this function) /usr/src/sys/kern/kern_mutex.c:595: (Each undeclared identifier is reported o nly once /usr/src/sys/kern/kern_mutex.c:595: for each function it appears in.) /usr/src/sys/kern/kern_mutex.c:596: `MA_RECURSED' undeclared (first use in th is function) /usr/src/sys/kern/kern_mutex.c:597: `MA_NOTRECURSED' undeclared (first use in this function) /usr/src/sys/kern/kern_mutex.c:610: `MA_NOTOWNED' undeclared (first use in th is function) It looks like these are defined when you have, options INVARIANTS in your kernel config. It shouldn't be required, but try adding it and see if that helps. Rcent kernels require `option INVARIANT_SUPPORT' in addition to `options INVARIANTS'. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Getting a first build up and running?
Hi, I have a machine I want to use as a FreeBSD-Current machine since I want to work with some of the new features in 5.x that I require for a port (I'm trying to port The Click Modular Router from Linux and it would be good to have kernel threads). The problem is that the machine is right now at 4.0-RELEASE. I've done a cvsup for current and am trying to build. I get the following error during make buildworld. The error output is at the end of the email. So, do I need to do something special? Is there a CURRENT-STABLE label of some sort as the last time that -CURRENT was known to build/install? I can't find anything in the handbook on this kind of thing. Is there a "guide to -CURRENT" somewhere? Thanks, George stage 3: cross tools -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" MACHINE_ARCH=i386 TOOLS_PREFIX=/usr/obj/usr/src/i386 PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/ src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin TARGET_ARCH=i386 make -f Makefile.inc1 -DNO_FORTRAN -DNO_GDB -DNOHTML -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cross-tools cd /usr/src/gnu/usr.bin/perl/libperl; make obj; make depend; make all; make install /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl created for /usr/src/gnu/usr.bin/perl/libperl Extracting config.h (with variable substitutions) rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -DPERL_CORE -I/usr/obj/usr/src/i386/usr/include /usr/src/gnu/usr.bin/perl/libperl/../../.. /../contrib/perl5/perl.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/ perl5/gv.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/toke.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perly.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/op.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/regcomp.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/dump.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/util.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/mg.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/hv.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/av.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/run.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/pp_hot.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/sv.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/pp.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/scope.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/pp_ctl.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/pp_sys.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/doop.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/doio.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/regexec.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/utf8.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/taint.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/deb.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/universal.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/xsutils.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/globals.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perlio.c /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/perlapi.c cd /usr/src/gnu/usr.bin/perl/libperl; make _EXTRADEPEND cc -O -pipe -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -DPERL_CORE -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../ ../../contrib/perl5/perl.c -o perl.o cc -O -pipe -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -DPERL_CORE -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../ ../../contrib/perl5/gv.c -o gv.o cc -O -pipe -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -DPERL_CORE -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../ ../../contrib/perl5/toke.c -o toke.o cc -O -pipe -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -DPERL_CORE -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/usr.bin/perl/libperl/../../ ../../contrib/perl5/op.c -o op.o cc -O -pipe -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/perl/libperl -I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 -DPERL_CORE
Re: Getting a first build up and running?
On Sat, Mar 03, 2001 at 11:06:15AM -0800, George V. Neville-Neil wrote: I have a machine I want to use as a FreeBSD-Current machine since I want to work with some of the new features in 5.x that I require for a port (I'm ... The problem is that the machine is right now at 4.0-RELEASE. I've done a cvsup for current and am trying to build. You first want to CVSup to and `make world' to the latest RELENG_4. Then jump to -current from that. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Labeling Vinum partitions in the sysinstall(8) [patch]
ccd anybody? AFAIK, unlike vinum, ccd doesn't require any special disk labeling. Sorry, I should have been clearer. If I got it right, you're working not only on disk labeling for vinum, but on a complete frontend. If that is true, I think we (yes I am volunteering, in case nobody else will - but I might need help) should look into it and see how hard it might be to turn the non-disklabel part into also a ccdconfig frontend. I think what I'm trying to achieve is quite clear. It's currently very hard to install a system with say a mirrored /usr; you need to do a lot of post-install games. Having done that a lot of times in last year, I would love to have the option to ccdconfig partitions in sysinstall, and install on them. Bye, Andrea -- ...and that is how we know the Earth to be banana-shaped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel logging under heavy load
A simple but intensive fork bomb were started on 5.0-current UP machine.
After it, /var/log/messages contains:
Mar 3 19:16:46 iv /boot/kernel/kernel: roc: table is full
Mar 3 19:16:46 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:46 iv last message repeated 42 times
Mar 3 19:16:46 iv /boot/kernel/kernel: proc: table 3proc: table is full
Mar 3 19:16:46 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:47 iv last message repeated 41 times
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is fs full
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:47 iv last message repeated 42 times
Mar 3 19:16:47 iv /boot/kernel/kernel: proc:ll
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:47 iv last message repeated 43 times
Mar 3 19:16:47 iv /boot/kernel/kernel: table is full
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:47 iv last message repeated 42 times
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is futable is full
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:47 iv last message repeated 42 times
Mar 3 19:16:47 iv /boot/kernel/kernel: l
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:47 iv last message repeated 43 times
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: l
Mar 3 19:16:47 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:16:50 iv last message repeated 10212 times
Mar 3 19:17:16 iv /boot/kernel/kernel: roc: table is full
Mar 3 19:17:16 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 42 times
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table roc: table is full
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 42 times
Mar 3 19:17:17 iv /boot/kernel/kernel: ull
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 43 times
Mar 3 19:17:17 iv /boot/kernel/kernel: procull
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 43 times
Mar 3 19:17:17 iv /boot/kernel/kernel: table is full
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 42 times
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is f table is full
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 42 times
Mar 3 19:17:17 iv /boot/kernel/kernel: ll
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 43 times
Mar 3 19:17:17 iv /boot/kernel/kernel: proc:ll
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 43 times
Mar 3 19:17:17 iv /boot/kernel/kernel: table is full
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 42 times
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is futable is full
Mar 3 19:17:17 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:17 iv last message repeated 42 times
Mar 3 19:17:17 iv /boot/kernel/kernel: l
Mar 3 19:17:18 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:18 iv last message repeated 43 times
Mar 3 19:17:18 iv /boot/kernel/kernel: proc: l
Mar 3 19:17:18 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:18 iv last message repeated 3524 times
Mar 3 19:17:46 iv /boot/kernel/kernel: roc: table is full
Mar 3 19:17:46 iv /boot/kernel/kernel: proc: table is full
Mar 3 19:17:47 iv last message repeated 3559 times
The message is generated with command
kern_fork.c:246:tablefull("proc");
The system in question is UP, 5.0-current of 2001-02-27
/netch
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Problem with sio in -current ... possible cause of hangs?
Morning all ...
I'm trying to get my serial console to work on my desktop, and
appear to be failing miserably at even just getting it to accept a 'getty'
serial connection, let alone serial console ...
First, my X/mouse runs on /dev/ttyd1 ... if I startx, my mouse
does work, but X hangs *very* quickly. Based on this, I know that
/dev/ttyd1 does work, at least for a short time.
Now, to confirm ... a NULL modem cable *is* pin 2-3, 3-2, right?
rx-tx, tx-rx? I've tested the cable using a multi-meter, just to make
sure that it is doing what I expect ...
If I plug my cable from /dev/ttyd0 - /dev/ttyd1 on the same
machine, run getty on /dev/ttyd1 and use kermit to connect to /dev/cuaa0,
I get no response back, which is why I'm wondering about sio ...
I've also tried connecting my serial port on my laptop to both
/dev/ttyd0 and /dev/ttyd1, and run getty, and that doesn't get any login
prompt either ...
Since, albeit briefly, I know that /dev/ttyd1 does work when X
starts up, I'd expect that getty would give me a login prompt if I enabled
it on that port, no?
I'm running -CURRENT as of Feb 27th, and am just about to upgrade
again ... dmesg shows my sio devices as:
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
Which look right to me ...
I've scan'd /usr/src/UPGRADING to see if there was something in
the past that I might have missed concerning sio, but couldn't find
anything ...
And, sio is defined in my kernel as simple 'device sio' ...
Thoughts?
Thanks ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: Problem with sio in -current ... possible cause of hangs?
On 03-Mar-01 The Hermit Hacker wrote: Morning all ... I'm trying to get my serial console to work on my desktop, and appear to be failing miserably at even just getting it to accept a 'getty' serial connection, let alone serial console ... First, my X/mouse runs on /dev/ttyd1 ... if I startx, my mouse does work, but X hangs *very* quickly. Based on this, I know that /dev/ttyd1 does work, at least for a short time. Now, to confirm ... a NULL modem cable *is* pin 2-3, 3-2, right? rx-tx, tx-rx? I've tested the cable using a multi-meter, just to make sure that it is doing what I expect ... If I plug my cable from /dev/ttyd0 - /dev/ttyd1 on the same machine, run getty on /dev/ttyd1 and use kermit to connect to /dev/cuaa0, I get no response back, which is why I'm wondering about sio ... Try turning clocal off on the host and port you are running kermit on. Even then, I still have yet to get getty to work at all, it's always stuck in 'siodcd'. I've noticed via debugging output that the DCD change bit does raise for a read, but that teh DCD status bit stays at zero the entire time. The sio driver seems to ignore the change bit and only read the status bit, so it thinks DCD is never raised and hangs forever on open. Note that I can get a getty fine on a serial console, just not on a /dev/ttydX that's not also the serial console. :( I've had this problem since before PRE_SMPNG however. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Problem with sio in -current ... possible cause of hangs?
Woo hoo ... got the serial console working ... I had put -D into
/boot.config, vs -P ...
... neat ... I got all the boot info on my serial console, then the login
prompt went to the main screen, and no control on either one ...
is that supposed to happen?
On Sat, 3 Mar 2001, John Baldwin wrote:
On 03-Mar-01 The Hermit Hacker wrote:
Morning all ...
I'm trying to get my serial console to work on my desktop, and
appear to be failing miserably at even just getting it to accept a 'getty'
serial connection, let alone serial console ...
First, my X/mouse runs on /dev/ttyd1 ... if I startx, my mouse
does work, but X hangs *very* quickly. Based on this, I know that
/dev/ttyd1 does work, at least for a short time.
Now, to confirm ... a NULL modem cable *is* pin 2-3, 3-2, right?
rx-tx, tx-rx? I've tested the cable using a multi-meter, just to make
sure that it is doing what I expect ...
If I plug my cable from /dev/ttyd0 - /dev/ttyd1 on the same
machine, run getty on /dev/ttyd1 and use kermit to connect to /dev/cuaa0,
I get no response back, which is why I'm wondering about sio ...
Try turning clocal off on the host and port you are running kermit on. Even
then, I still have yet to get getty to work at all, it's always stuck in
'siodcd'. I've noticed via debugging output that the DCD change bit does raise
for a read, but that teh DCD status bit stays at zero the entire time. The
sio driver seems to ignore the change bit and only read the status bit, so it
thinks DCD is never raised and hangs forever on open. Note that I can get a
getty fine on a serial console, just not on a /dev/ttydX that's not also the
serial console. :( I've had this problem since before PRE_SMPNG however.
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Using serial console to debug system hangs ...
Well, after some hurdles with getting the serial console to work, I've now
go it to work ... I put the two sysctl commands into a file so that I
could run it as a script:
#!/bin/sh
sysctl -w debug.ktr.mask=0x1208
sysctl -w debug.ktr.verbose=2
When I 'try' to run it, I get all the 'KTR'(?) messages on my serial
console, something is changing/happening so fast that my ssh connection
into the machine hangs before I finish typing in the shell script:
enable_kernel_debug: 3 lines, 72 characters.
thelab# !./
needless to say, running the command to hang the computer is proving
difficult :)
Then again, if I do a cold boot of the machine, the messages stop
scrolling up the console, but a cut-n-paste of them is sort of illegible:
k0clo.c/k...c/.k4e3r8n /RkEeLr n(_scplionc)k .scch2e0d9 lRoEcLk (s[p0xicn0)
32c1al1l8o0]ut r[=00x ca0t 31.d./8.2.0/] ker=r0n/ akte r.n._c/l.o./ckk.ecrn:4/k3e8r
e_cpluo1c k..c/:.2.0/9k
rcnp/uk0e r.n./.l.o/ckke.rcn./3k5e0r nG_OcTl o(cskp.icn.)2 0s3c hGeOdT
l(oscpki n[)0 xccall2o1u1t8 0[]0 xrc=003 1adt8 2.0.]/ ..0/k aertn
./.k/er..n_/ckllorcnk/.kecr:n35_0c
.ok.uc1: 2.0.3/
.c/pkue0r.n/.k/.er./n_kcelrnoc/kke.crn.4_c38l ocRkEL. c(.s2p09in )R ELs ch(sepd
iln)oc kc al[0loxuct03 [210x18c003] 1rd=802 0a] t r=..0/ a..t
/.k.er/.n./.ckerenrn_c/lkoerckn_.ccl:4oc3k8
:20u91
.c.p/u.0. /.k.e/r.n.//kkeerrnn_/ckleorcnk_.ccl.o3c5k0. cG.O2T0 3( sGpOiTn )(
sspcihne)d claolclko u[t0 x[c00x3213118d08]2 0r]= 0r =a0t a.t.
///.k.e/0ke/rkne/rkne_rcnl_occlko.cck:.3c5:02
p3c
uc1p u.0. ///.k.e/rkne/rkne/rkne_rcnl_occlko.cck..4c3.82 RE LR E(Ls
p(isnp)i ns)c hceadl lloouctk [[00xxcc003312d1812800]] rr==00 aatt
////kkeerrnn//kkeerrnn__cclloocckk..cc::24398
ccppuu01 ////kkeerrnn//kkeerrnn__cclloocckk..cc..230530 GGOOTT
((ssppiinn)) csaclhleodu tl o[c0kx c[003x1cd0832201]1 8r0=]0 ra=t0 .a.t
then again, looking at it, it looks like everything is going in duplicates?
suggestions?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Sorry. Off topic but need help.
While trying to upgrade a 3.3-Stable box to 4.2-Release, we crashed during the upgrade. After restoring the system from tape, password no longer work. We've tried killing all files except master.passwd and regenerating with pwd_mkdb, but that didn't work. Any help would be greatly appreciated. Bob Martin -- As far as the laws of mathematics refer to reality, they are not certain, and as far as they are certain, they do not refer to reality. -- Albert Einstein To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Using serial console to debug system hangs ...
On 04-Mar-01 The Hermit Hacker wrote: Well, after some hurdles with getting the serial console to work, I've now go it to work ... I put the two sysctl commands into a file so that I could run it as a script: #!/bin/sh sysctl -w debug.ktr.mask=0x1208 sysctl -w debug.ktr.verbose=2 When I 'try' to run it, I get all the 'KTR'(?) messages on my serial console, something is changing/happening so fast that my ssh connection into the machine hangs before I finish typing in the shell script: enable_kernel_debug: 3 lines, 72 characters. thelab# !./ Put the sysctl's and the command that hangs the machine into one script and run that one shell script.. needless to say, running the command to hang the computer is proving difficult :) Then again, if I do a cold boot of the machine, the messages stop scrolling up the console, but a cut-n-paste of them is sort of illegible: k0clo.c/k...c/.k4e3r8n /RkEeLr n(_scplionc)k .scch2e0d9 lRoEcLk (s[p0xicn0) 32c1al1l8o0]ut r[=00x ca0t 31.d./8.2.0/] ker=r0n/ akte r.n._c/l.o./ckk.ecrn:4/k3e8r e_cpluo1c k..c/:.2.0/9k rcnp/uk0e r.n./.l.o/ckke.rcn./3k5e0r nG_OcTl o(cskp.icn.)2 0s3c hGeOdT l(oscpki n[)0 xccall2o1u1t8 0[]0 xrc=003 1adt8 2.0.]/ ..0/k aertn ./.k/er..n_/ckllorcnk/.kecr:n35_0c .ok.uc1: 2.0.3/ .c/pkue0r.n/.k/.er./n_kcelrnoc/kke.crn.4_c38l ocRkEL. c(.s2p09in )R ELs ch(sepd iln)oc kc al[0loxuct03 [210x18c003] 1rd=802 0a] t r=..0/ a..t /.k.er/.n./.ckerenrn_c/lkoerckn_.ccl:4oc3k8 :20u91 .c.p/u.0. /.k.e/r.n.//kkeerrnn_/ckleorcnk_.ccl.o3c5k0. cG.O2T0 3( sGpOiTn )( sspcihne)d claolclko u[t0 x[c00x3213118d08]2 0r]= 0r =a0t a.t. ///.k.e/0ke/rkne/rkne_rcnl_occlko.cck:.3c5:02 p3c uc1p u.0. ///.k.e/rkne/rkne/rkne_rcnl_occlko.cck..4c3.82 RE LR E(Ls p(isnp)i ns)c hceadl lloouctk [[00xxcc003312d1812800]] rr==00 aatt ////kkeerrnn//kkeerrnn__cclloocckk..cc::24398 ccppuu01 ////kkeerrnn//kkeerrnn__cclloocckk..cc..230530 GGOOTT ((ssppiinn)) csaclhleodu tl o[c0kx c[003x1cd0832201]1 8r0=]0 ra=t0 .a.t Hmm, it's colliding with itself a lot. Unfortunately, to make this useful over the serial console, you need to shut up all the sio lock messages. Hmmm, well for now try just using a 'debug.ktr.mask' of 0x1200 to skip all the mutex operations. If we need them later on, then I will try and get some other work done to make it easier to shut up certain mutexes in the log output without having to change each individual mutex operation. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with sio in -current ... possible cause of hangs?
The Hermit Hacker [EMAIL PROTECTED] writes: ... neat ... I got all the boot info on my serial console, then the login prompt went to the main screen, and no control on either one ... is that supposed to happen? You aren't supposed to get a login screen on the serial line unless you enabled ttyd0 in /etc/ttys. For example, the following, ttyd0 "/usr/libexec/getty std.9600" cons25 on secure enables getty on the serial line. The default in /etc/ttys is for ttyd? to be marked 'off' (second field from the end). Change that and try again. Hope this helps Dima Dorfman [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/kern kern_intr.c src/sys/sys interrupt.h
John Baldwin wrote: without causing problems. However, it may be that a sleep mutex wouldn't be but so evil. If desired I can whip up a patch to do that instead and see how much worse it is. It would probably hurt lpr performance a bit unless the ppbus was fixed to do its own multiplexing of the interrupt. I get an instance panic if I start lpd, so I doubt you can make lpr performance any worse ;-) The printer is connected to the parallel port. On my work machine, lpd/lpr work fine, but the printer is connected via tcp/ip. I have a crash dump if you need it. Sources are from 2 Mar 01 at 2158 PST. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Using serial console to debug system hangs ...
Wow, that was painful ... after 2 hrs, I got as far as:
thelab# ./enable_debug
debug.ktr.mask: 1 - 4608
debug.ktr.verbose: 0 - 2
waiting for X server to begin accepting connections .
XFree86 Version 4.0.2 / X Window System
(protocol Version 11, revision 0, vendor release 6400)
Release Date: 18 December 2000
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems. (See http://www.XFree86.Org/FAQ)
Operating System: FreeBSD 5.0-CURRENT i386 [ELF]
Module Loader present
(==) Log file: "/var/log/XFree86.0.log", Time: Sat Mar 3 22:08:37 2001
(==) Using config file: "/root/XF86Config"
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (??) unknown.
(==) ServerLayout "Simple Layout"
(**) |--Screen "Screen 1" (0)
(**) | |--Monitor "Samtron 95P"
(**) | |--Device "TNT"
(**) |--Input Device "Mouse1"
(**) |--Input Device "Keyboard1"
(**) XKB: rules: "xfree86"
(**) XKB: model: "microsoft"
(**) XKB: layout: "us"
(**) FontPath set to
"/usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(--) Using syscons driver with X support (version 2.0)
and gave up ... am going to try again just before I go to bed tonight,
hopefully its running (and hung) by the time I get up in the morning ;)
On Sat, 3 Mar 2001, John Baldwin wrote:
On 04-Mar-01 The Hermit Hacker wrote:
Well, after some hurdles with getting the serial console to work, I've now
go it to work ... I put the two sysctl commands into a file so that I
could run it as a script:
#!/bin/sh
sysctl -w debug.ktr.mask=0x1208
sysctl -w debug.ktr.verbose=2
When I 'try' to run it, I get all the 'KTR'(?) messages on my serial
console, something is changing/happening so fast that my ssh connection
into the machine hangs before I finish typing in the shell script:
enable_kernel_debug: 3 lines, 72 characters.
thelab# !./
Put the sysctl's and the command that hangs the machine into one script and run
that one shell script..
needless to say, running the command to hang the computer is proving
difficult :)
Then again, if I do a cold boot of the machine, the messages stop
scrolling up the console, but a cut-n-paste of them is sort of illegible:
k0clo.c/k...c/.k4e3r8n /RkEeLr n(_scplionc)k .scch2e0d9 lRoEcLk
(s[p0xicn0) 32c1al1l8o0]ut r[=00x ca0t 31.d./8.2.0/] ker=r0n/ akte
r.n._c/l.o./ckk.ecrn:4/k3e8r
e_cpluo1c k..c/:.2.0/9k
rcnp/uk0e r.n./.l.o/ckke.rcn./3k5e0r nG_OcTl o(cskp.icn.)2 0s3c
hGeOdT l(oscpki n[)0 xccall2o1u1t8 0[]0 xrc=003 1adt8 2.0.]/ ..0/k aertn
./.k/er..n_/ckllorcnk/.kecr:n35_0c
.ok.uc1: 2.0.3/
.c/pkue0r.n/.k/.er./n_kcelrnoc/kke.crn.4_c38l ocRkEL. c(.s2p09in )R
ELs ch(sepd iln)oc kc al[0loxuct03 [210x18c003] 1rd=802 0a] t r=..0/ a..t
/.k.er/.n./.ckerenrn_c/lkoerckn_.ccl:4oc3k8
:20u91
.c.p/u.0. /.k.e/r.n.//kkeerrnn_/ckleorcnk_.ccl.o3c5k0. cG.O2T0 3(
sGpOiTn )( sspcihne)d claolclko u[t0 x[c00x3213118d08]2 0r]= 0r =a0t a.t.
///.k.e/0ke/rkne/rkne_rcnl_occlko.cck:.3c5:02
p3c
uc1p u.0. ///.k.e/rkne/rkne/rkne_rcnl_occlko.cck..4c3.82 RE LR
E(Ls p(isnp)i ns)c hceadl lloouctk [[00xxcc003312d1812800]] rr==00 aatt
////kkeerrnn//kkeerrnn__cclloocckk..cc::24398
ccppuu01 ////kkeerrnn//kkeerrnn__cclloocckk..cc..230530
GGOOTT ((ssppiinn)) csaclhleodu tl o[c0kx c[003x1cd0832201]1 8r0=]0 ra=t0
.a.t
Hmm, it's colliding with itself a lot. Unfortunately, to make this useful over
the serial console, you need to shut up all the sio lock messages. Hmmm, well
for now try just using a 'debug.ktr.mask' of 0x1200 to skip all the mutex
operations. If we need them later on, then I will try and get some other work
done to make it easier to shut up certain mutexes in the log output without
having to change each individual mutex operation.
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/kern kern_intr.c src/sys/sys interrupt.h
In message [EMAIL PROTECTED] Steve Kargl writes: : I get an instance panic if I start lpd, so I doubt you can make : lpr performance any worse ;-) The printer is connected to the : parallel port. On my work machine, lpd/lpr work fine, but the : printer is connected via tcp/ip. I can start lpd on my machine, but sometimes the machine will panic when an actual print job hits it. On reboot it will panic when lpd starts sometimes. Other times it will just work. This is from a Feb 24th -current. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: contrib/sendmail/cf ownership spammed
msmith I've noticed that 'make world' spams the ownership of msmith src/contrib/sendmail/cf, leaving it owned by root. This is bad. 8) I'll fix this as soon as I get back from the east coast (Monday, assuming the snow storm they are expecting waits until I am in the air before hitting). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/kern kern_intr.c src/sys/sys interrupt.h
Warner Losh wrote: In message [EMAIL PROTECTED] Steve Kargl writes: : I get an instance panic if I start lpd, so I doubt you can make : lpr performance any worse ;-) The printer is connected to the : parallel port. On my work machine, lpd/lpr work fine, but the : printer is connected via tcp/ip. I can start lpd on my machine, but sometimes the machine will panic when an actual print job hits it. On reboot it will panic when lpd starts sometimes. Other times it will just work. This is from a Feb 24th -current. I have printing jobs sitting in the queue, so when lpq fires up my machine panics. I haven't tried deleting the print jobs, restarting lpd, and then printing. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Getting a first build up and running?
"George V. Neville-Neil" wrote: Hi, I have a machine I want to use as a FreeBSD-Current machine since I want to work with some of the new features in 5.x that I require for a port (I'm trying to port The Click Modular Router from Linux and it would be good to have kernel threads). The click router was designed around he same time as netgraph with many of the sme design goals, except they wanted to make it slightly less lego than I did. It is interesting how many common ideas came up but also how many differences To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Getting a first build up and running?
The click router was designed around he same time as netgraph with many of the same design goals, except they wanted to make it slightly less lego than I did. It is interesting how many common ideas came up but also how many differences As one of the designers of netgraph I'd be interested to hear your thoughts on the comparison. I've looked at both but only played with netgraph a little. Having read the major papers on Click I think it's an excellent way to build highly extensible, field upgradable, fast routers. I guess we'll see of course :-) Later, George To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
