Re: In-kernel PPPoE
On Sun, Dec 5, 2010 at 6:32 PM, Andriy Gapon a...@freebsd.org wrote: on 05/12/2010 22:30 Julian Elischer said the following: On 12/5/10 9:30 AM, Bernd Walter wrote: On Sun, Dec 05, 2010 at 12:14:21PM -0500, Pierre Lamy wrote: Just curious about why the in-kernel PPPoE interface was never ported from NetBSD or OpenBSD, to FreeBSD. Does anyone know why? Maybe because everyone who cares about in-kernel uses the FreeBSD in-kernel ng_pppoe via mpd? From using it for a long time in OpenBSD I always found it quite stable and easy to use. The same is true with mpd/ng_pppoe. while I like mpd, I should point out that the regular 'in source' ppp that comes with freebsd also uses the in-kernel netgraph pppoe module. I use it 24 x 7 on my gateway as I never got around to installing mpd and it did the job. BTW, there is a rumor that mpd may become an 'in source' program too. -- Andriy Gapon Does mpd work in -current ? Last tried I, netgraph had problems with mpd. ___ 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
Re: How a full fsck screwed up my SU+J filesystem
Hello, what do you make of this PR report ? http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/152605 This panic happens during bg-fsck every time. I have to boot into single user-mode and do a fsck to correct. ___ 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
Re: Only display ACPI bootmenu key if ACPI is present
What are the chances the detection fails and one still needs to disable ACPI and can't because it's not showing as a option ? Thanks, David Rhodus On Nov 8, 2010, at 5:14 PM, John Baldwin j...@freebsd.org wrote: This patch changes the Forth code for the Beastie menu to only display the menu option to enable or disable ACPI if the loader detects ACPI. This avoids displaying a menu item prompting to enable ACPI if the BIOS doesn't actually include ACPI. Any objections? --- //depot/projects/smpng/sys/boot/forth/beastie.4th2010-11-08 21:53:18.0 +++ //depot/user/jhb/ktrace/boot/forth/beastie.4th2010-11-08 22:14:04.0 @@ -140,12 +140,16 @@ fbsdbw-logo ; -: acpienabled? ( -- flag ) +: acpipresent? ( -- flag ) s hint.acpi.0.rsdp getenv dup -1 = if drop false exit then 2drop +true +; + +: acpienabled? ( -- flag ) s hint.acpi.0.disabled getenv dup -1 if s 0 compare 0 if @@ -178,8 +182,7 @@ 42 20 2 2 box 13 6 at-xy . Welcome to FreeBSD! printmenuitem . Boot FreeBSD [default] bootkey ! -s arch-i386 environment? if -drop +acpipresent? if printmenuitem . Boot FreeBSD with ACPI bootacpikey ! acpienabled? if . disabled -- John Baldwin ___ 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 ___ 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
Re: ngctl can crash the kernel
Same panic here...
Also the MPD2 port is broken, I'm guessing a netgraph problem too.
2010/11/5 sdfsdf rwerwer freebsd-tracker-int...@mail.ru:
Hi everybody,
The following commands lead the 9.0-CURRENT kernel to crash:
[r...@freebsd /usr/home/int0dh]# ngctl
Available commands:
config get or set configuration of node at path
connect Connects hook peerhook of the node at relpath to hook
debug Get/set debugging verbosity level
dot Produce a GraphViz (.dot) of the entire netgraph.
help Show command summary or get more help on a specific command
list Show information about all nodes
mkpeer Create and connect a new node to the node at path
msg Send a netgraph control message to the node at path
name Assign name name to the node at path
read Read and execute commands from a file
rmhook Disconnect hook hook of the node at path
show Show information about the node at path
shutdown Shutdown the node at path
status Get human readable status information from the node at path
types Show information about all installed node types
write Send a data packet down the hook named by hook.
quit Exit program
+ mkpeer ksocket myhook inet/stream/tcp
+ msg .:myhook connect inet/127.0.0.1:22
After last command the kernel panics.
Any listening TCP port can be used instead of 22.
The panic occurs here (sys/kern/uipc_sockbuf.c):
int
sbappendaddr_locked(struct sockbuf *sb, const struct sockaddr *asa,
struct mbuf *m0, struct mbuf *control)
{
struct mbuf *m, *n, *nlast;
int space = asa-sa_len;
SOCKBUF_LOCK_ASSERT(sb);
if (m0 (m0-m_flags M_PKTHDR) == 0)
{
panic(sbappendaddr_locked ;
}
I`ve tried with the custom kernel only, but I think that issue can be
reproduced with GENERIC too.
___
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
___
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
calcru: runtime went backwards
I haven't seen much of this since 5.x days. Anyone else see calcru messages lately ? -DR NFS# uname -a FreeBSD NFS.Lesmilde.com 9.0-CURRENT FreeBSD 9.0-CURRENT #2: Fri Oct 29 01:07:40 CDT 2010 r...@nfs.lesmilde.com:/usr/obj/usr/src/sys/GENERIC amd64 NFS# tail -25 /var/log/messages Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 91464 usec to 40935 usec for pid 2709 (csh) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 4334 usec to 1927 usec for pid 2134 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 4814 usec to 2140 usec for pid 2133 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 4752 usec to 2113 usec for pid 2132 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 5322 usec to 2366 usec for pid 2131 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 5183 usec to 2304 usec for pid 2130 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 4495 usec to 1998 usec for pid 2129 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 4501 usec to 2001 usec for pid 2128 (getty) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 15315 usec to 6809 usec for pid 2127 (login) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 32057357 usec to 28943929 usec for pid 2063 (cron) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 1381 usec to 613 usec for pid 2015 (rsync) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 1606 usec to 936 usec for pid 1940 (smbd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 20818 usec to 9600 usec for pid 1895 (smbd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 18992 usec to 8440 usec for pid 1760 (cupsd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 3378 usec to 1501 usec for pid 1720 (mountd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 1458 usec to 648 usec for pid 1681 (nfsuserd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 568 usec to 308 usec for pid 1335 (devd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 214373 usec to 95273 usec for pid 1335 (devd) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 965 usec to 428 usec for pid 132 (adjkerntz) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 191 usec to 84 usec for pid 15 (vmdaemon) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 74 usec to 33 usec for pid 7 (sctp_iterator) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 984227 usec to 748883 usec for pid 4 (g_down) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 1281130 usec to 979529 usec for pid 3 (g_up) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 10320 usec to 4890 usec for pid 1 (init) Oct 30 19:13:25 NFS kernel: calcru: runtime went backwards from 6244341 usec to 2848133 usec for pid 1 (init) NFS# ___ 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
Re: Xorg build error on -current-amd64
Thanks, make delete-old fixed everything. On Thu, Jun 3, 2010 at 4:43 AM, Alexander Pyhalov a...@rsu.ru wrote: Hello. I've just had this error yesterday. It seems, that utmp.h file is still in the system. Make in /usr/src: make delete-old and try again . David Rhodus wrote: === Verifying install for sessreg in /usr/ports/x11/sessreg === Building for sessreg-1.0.5 make all-am cc -std=gnu99 -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wformat=2 -Wold-style-definition -Wdeclaration-after-statement -I/usr/local/include -O2 -pipe -fno-strict-aliasing -o sessreg sessreg.o sessreg.o(.text+0xada): In function `main': : undefined reference to `ttyslot' *** Error code 1 Stop in /usr/ports/x11/sessreg/work/sessreg-1.0.5. *** Error code 1 Stop in /usr/ports/x11/sessreg/work/sessreg-1.0.5. *** Error code 1 Stop in /usr/ports/x11/sessreg. *** Error code 1 Stop in /usr/ports/x11/xorg-apps. *** Error code 1 Stop in /usr/ports/x11/xorg-apps. *** Error code 1 Stop in /usr/ports/x11/xorg. # uname -a FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Wed Jun 2 15:10:14 UTC 2010 root@:/usr/obj/usr/src/sys/GENERIC amd64 # ___ 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 -- С уважением, Александр Пыхалов, системный администратор ЮГИНФО ЮФУ. ___ 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
Auto doadump()
Is there a rc.conf variable to automatically save core on a panic and reboot ? Setting dumpdev=AUTO doesn't seem to do the trick. # uname -a FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Thu Jun 3 20:00:22 UTC 2010 root@:/usr/obj/usr/src/sys/GE amd64 # ___ 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
Re: Running all regression tests
Doing a ./test.sh make crashes my -current machine pretty quickly. It stops inBuilding in /usr/src/tools/regression/bin/mv On Thu, Jun 3, 2010 at 6:19 PM, Erik Cederstrand e...@cederstrand.dk wrote: Den 03/06/2010 kl. 21.54 skrev Giorgos Keramidas: On Thu, 03 Jun 2010 14:50:13 +0200, Alexander Leidinger alexan...@leidinger.net wrote: Quoting Erik Cederstrand e...@cederstrand.dk (from Thu, 3 Jun 2010 12:02:51 +0200): Hi, I'd like to run the regression tests in src/tools/regression on a regular basis. What's the official way to do this? Is there some way I can run them all in one go? It seems it's necessary to enter every single subdirectory and execute any Makefiles located there before running 'prove -r'. Some You could write a Makefile which recurses into the subdirs. I ended up with the attached shell script which does the job (but not very elegantly) for the time being. As stated elsewhere in this thread, some tests need cleaning up and rewriting to the standard format. Erik ___ 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
SUJ Patches for 8.X ???
Anyone have a SUJ patch set for 8.x ? ___ 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
Xorg build error on -current-amd64
===Verifying install for sessreg in /usr/ports/x11/sessreg === Building for sessreg-1.0.5 make all-am cc -std=gnu99 -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wformat=2 -Wold-style-definition -Wdeclaration-after-statement -I/usr/local/include -O2 -pipe -fno-strict-aliasing -o sessreg sessreg.o sessreg.o(.text+0xada): In function `main': : undefined reference to `ttyslot' *** Error code 1 Stop in /usr/ports/x11/sessreg/work/sessreg-1.0.5. *** Error code 1 Stop in /usr/ports/x11/sessreg/work/sessreg-1.0.5. *** Error code 1 Stop in /usr/ports/x11/sessreg. *** Error code 1 Stop in /usr/ports/x11/xorg-apps. *** Error code 1 Stop in /usr/ports/x11/xorg-apps. *** Error code 1 Stop in /usr/ports/x11/xorg. # uname -a FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Wed Jun 2 15:10:14 UTC 2010 root@:/usr/obj/usr/src/sys/GENERIC amd64 # ___ 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
Apples linking
Terry Lambert wrote: FWIW, even though I support the idea of dynamically linking everything, the flipping of the switch there followed this same pattern. -- Terry Terry, what are some of the changes that Apple made to have everything dynamically linked in darwin ? Has anyone done timed runs lately on dynamically vers. static linking on darwin ? Or did they find just cleaning up the dlopen code path seems to be enough to pull dynamically linking everything ? -DR ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-BETA: giving up on 4 buffers (ata)
Ryan Sommers wrote: I'll also note in my FreeBSD current debugging of some drivers it was about a 50/50 shot as to if this would happen. Having to fsck every other reboot was only made less painful by the background fsck thing. Don't some BIOS' protect the superblocks as a kind of virus protection? Could this be related to them? No. -DR ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Release Engineering Status Report
On Tuesday, September 16, 2003, at 06:11 AM, Bruce Evans wrote: On Tue, 16 Sep 2003, Maxim Konovalov wrote: PAE MFC brought an incredible instability to stable branch. It affects 100% of our user community especially when we issued several SAs since PAE commit. They often can't switch to RELENG_4_x security branches because even RELENG_4_8 misses several critical non-security fixes. Right, say if still the OpenSSH did or still comes out to be real. Ops, now thats right, we don't have 3.6.1 in STABLE, why ? It was released on April 1, does that not give one enough time to merge this in ? Perhaps someone new is needed then to manage the import of OpenSSH if that is the case, if it is re@ or other decision member's of FreeBSD wouldn't allow it, then perhaps its time to restructure that part I'm not sure what the case is as other parts of been MFC'd lately without very much testing if any, noting the panic's that have been accruing on users running stable for the past 8 months. Should that just be taken as a sign of EoL for RELENG_4 ? I merged PAE into my version of -current a bit at a time and didn't notice any problems (with PAE not actually configured) despite having some large logical inconsistencies from not having all of it. Most of the global changes had no effect since they just changed the names of some typedefs without changing the underlying types in the !PAE case. So I suspect that any instabilities in RELENG_4 in the !PAE case are indirectly related to PAE and/or localized and thus easy to find and fix. Right the fix(es) should be trivial though incredibly hard to track down. Even more so that FreeBSD no long has anyone that is qualified to do any real work on the VM system. It is ridicules that re@ has allowed PAE to stay in the STABLE branch for still long with the amount of instability that it has created. I know its just uncovering bugs in the system that have always been present. Now we have many many kernel stack trace's and should be able to track it down over the next week months. For now though, the PAE commit should be removed from the RELENG_4 tree. Anything else should be not excepted by the FreeBSD community. -DR ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Release Engineering Status Report
On Tuesday, September 16, 2003, at 11:54 AM, Dag-Erling Smørgrav wrote: David Rhodus [EMAIL PROTECTED] writes: Right, say if still the OpenSSH did or still comes out to be real. Ops, now thats right, we don't have 3.6.1 in STABLE, why ? It was released on April 1, does that not give one enough time to merge this in ? Is there a specific problem with OpenSSH 3.5 which requires an update to 3.6.1? Or do you just want me to update it to make the numbers look pretty on your screen? Umm, yeah, so after today are we going to get a new import into RELENG_4 before 4.9 is pushed out the door ? -DR ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsh commands to 5.1-CURRENT being rejected
On Sunday, September 14, 2003, at 07:29 PM, [EMAIL PROTECTED] wrote: Sep 14 17:46:52 local7.notice target logger: TCP_Wrappers ALLOW: source/target,rshd,974,[EMAIL PROTECTED] Sep 14 17:46:52 auth.info target inetd[974]: connection from source, service rshd (tcp) Sep 14 17:46:52 auth.info target rshd[974]: [EMAIL PROTECTED] as root: permission denied (authentication error). cmd='date' What happens if you type in rsh target ? Does that then give you a shell ? -DR ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic while fsck
On Saturday, September 6, 2003, at 05:33 PM, Petri Helenius wrote: While fscking from previous panic in ufs2 code on -CURRENT from Sep 2, I got this: panic: ffs_copyonwrite: recursive call Reboot into single usermode and run the fsck. Then update your kernel as Jeff had broken a fews things could most likely are causing this panic. -DR ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvsup failing with ASSERT failed
On Wednesday, August 27, 2003, at 12:48 PM, Peter Wemm wrote: Oh, that *is* interesting. I get this 100% of the time when trying to run the i386 binary on my amd64 boxes. Hmm. Maybe I dont have an emulation bug then? [EMAIL PROTECTED]:46am]~-99 ./cvsup -gL2 cvs-supfile Parsing supfile cvs-supfile Connecting to malaise Wow, now I don't get my /compat dir populated during my installworld/installkernel on my amd64 machines. How do I go about installing those bits so that I can run i386 binary's ? -DR ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
rsync --daemon problems
When I start the rsync daemon under 5-RELEASE, I can only connect to it on the localhost. Trying to connect to it from any remote host fails. Trying to telnet to the 873 port fails as well. Everything is on a local lan connection without any type of fire-walling going on, also using the default install of 5.0 -- David To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: rsync --daemon problems
On Thursday, February 6, 2003, at 05:31 PM, Sean Winn wrote: What does netstat -na | grep 873 show? On one machine that rsync start's on, I get this from netstat. tcp6 0 0 *.873 *.* LISTEN On another machine that it just dies and never seems to startup, I'm seeing this in ktrace. 839 rsyncRET __getcwd 0 839 rsyncCALL getsockopt(0,0x,0x1008,0xbfbffba0,0xbfbffba4) 839 rsyncRET getsockopt -1 errno 38 Socket operation on non-socket 839 rsyncCALL fork 839 rsyncRET fork 840/0x348 839 rsyncCALL exit(0) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel message -- a prank?
On Tuesday, February 4, 2003, at 09:01 PM, Greg 'groggy' Lehey wrote:
with last hour, cvsup current, rebuild everything,... immediately
after kernel mount msg for /
kernel cranks out msg
Be nice to each other, mmmkay?
system otherwise fine. Is this a known prank?
It is now. It's in /sys/kern/init_main.c:
1.112(des 20-Apr-99):
1.224(des 04-Feb-03): printf(Be nice to each other,
mmmkay?\n);
1.223(des 04-Feb-03):
1.118(jb 05-May-99): for (path = init_path; *path
!= '\0'; path = next) {
des 2003/02/04 10:16:50 PST
Modified files:
sys/kern init_main.c
Log:
Extra precautions before trying to start init(8).
Revision ChangesPath
1.223 +2 -0 src/sys/kern/init_main.c
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
ftpd mkdir problems
Using the default ftpd that comes with FreeBSD, in the mkdir command, why doesn't it expand '~', the cd and rmdir commands seem to. Passing over the code it just calls the c function with should expand it. ftp cd ~will 250 CWD command successful. ftp mkdir ~will/test 550 ~will/test: No such file or directory. ftp mkdir test 257 test directory created. ftp rmdir ~will/test 250 RMD command successful. ftp -- David Rhodus To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
i386 buildkernel failure
make buildkernel KERNCONF=GENERIC ... cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/i386/i386/mp_machdep.c cc1: warnings being treated as errors /usr/src/sys/i386/i386/mp_machdep.c: In function `forwarded_statclock': /usr/src/sys/i386/i386/mp_machdep.c:2615: warning: passing arg 1 of `statclock_process' from incompatible pointer type *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. client# To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pthread ^T problem on recent -CURRENT: death in libc_r mutex
On Saturday, January 4, 2003, at 06:00 PM, Robert Watson wrote: On Sat, 4 Jan 2003, Juli Mallett wrote: * De: Robert Watson [EMAIL PROTECTED] [ Data: 2003-01-04 ] [ Subjecte: pthread ^T problem on recent -CURRENT: death in libc_r mutex ] Juli Mallett pointed me at the following reproduceable problem on my -current notebook with userland/kernel dated Dec 29: Incidentally, this doesn't illustrate the problem I was actually trying to point out. Try making the sleep's pthread_yield(). That will make the threads never run again. sleep is the hack I've had to do. In my appp, I have a 'my_yield' function which will sleep on FreeBSD, and yield on everywhere else :( Hmm. I'm not experiencing that problem -- if I replace the sleep() with pthread_yield(), I get a long sequence of '1's until thread2 is started, and then clean alternation between '1' and '2'. I don't see any failure to schedule a thread after it has yielded. I'm updating my box from Dec 29 to today to see if that makes a difference either way on either problem. With pthread_yield() I get the same as Watson. It still core's with a few ctrl-T's. I'm running today's source. -DR To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HELP: vinum and newfs on 5.0-RC1
I have also been having a few problems with vinum on 5.0-RC1. I've been having a hard time making a striped or raid5 vinum with more than 4 disk's. On the 5th+ disk's vinum will see and says device is not configured. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: backgroud fsck is still locking up system (fwd)
On Friday, December 6, 2002, at 01:39 PM, Archie Cobbs wrote: Kirk McKusick wrote: Does the background fsck process continue to run, or does the whole system come to a halt? If the fsck process continues to run, what happens when it eventually finishes? Is the system still dead, or does it come back to life? If the system does not come back to life can you get me the output of `ps axl'? If not, can you break into the debugger and get a ps output? (You will need to have the DDB option specified in your config file). OK, here is some more info.. I easily reproduced the problem again. So far it's 100% reproducible. This time to reproduce it simply booted in single user mode, typed mount -a -t nonfs and then pulled the plug. After the reboot, the HDD light soon stops blinking altogether. I waited for several minutes (which should have been long enough) and it never came back to life, which is not surprising considering there's no disk activity. Breaking into the debugger still works. However, pressing the soft power button no longer causes a graceful shutdown as it normally does. To copy the 'ps' debugger output, I'd have to manually copy it all, so here are just a few highlights: Proc State - fsck_ufs 0004000 norm[SLPQ nbufbs c036e5b0][SLP] fsck 0004002 norm[SLPQ wait c124dce8][SLP] syncer 204 norm[SLPQ nbufbs c036e5b0][SLP] vnlru 204 norm[SLPQ vlruwt c12c0ce8][SLP] bufdaemon 204 norm[SLPQ qsleep c036e5a4][SLP] swapper 200 norm[SLPQ sched c0315a20][SLP] Softupdates is enabled on /usr and /var but not /. This machine also acts as an NFS client for /home/archie. Why does softupdates not get enabled on / , by default on the install? -DR To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
