Re: 6.1-R ? 6-Stable ? 5.5-R ?
Albert Shih writes: I've nfs server running 6-Stable (5 April 2006) with some trouble but ... well approx stable. But today he crash again (after ~1.5 mounth). Now I'm like have some advise : 1/ I can upgrade to 6.1-Release, but I've see many problem with nfsd heavy load. And the only purpose of this server is .. nfsd. We have been upgrading to 6.X.. including 6.1 and so far the server seems, for the most part stable, until a few days ago(more below). What is a HUGE problem for us so far is that if the server hanks.. all clients that are 6.X can't unmount. 6.0 stable, 6.1 stable.. recent 6.1.. not so recent 6.1.. UDP, TCP, softmount with retrycount 1... In short. Right now I would not recommend 6.X for nfs client. 3/ I can downgrade to 5.5. I known this is legacy release but if it's workthat's enought for me... So far 6.X has been for the most part stable as NFS sever for us.. but one of our servers has been hanging crashing and NFSD was showing as status GIANT... and locking.. It had 6.0 stable and upgrading it to 6.1 stable (6-26) has not helped. But other machines are ok.. so may be an application. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-R ? 6-Stable ? 5.5-R ?
On Wed, Jun 28, 2006 at 04:09:14AM -0400, Francisco Reyes wrote: So far 6.X has been for the most part stable as NFS sever for us.. but one of our servers has been hanging crashing and NFSD was showing as status GIANT... and locking.. It had 6.0 stable and upgrading it to 6.1 stable (6-26) has not helped. But other machines are ok.. so may be an application. You'll want to upgrade to the latest 6-STABLE, where this bug has been fixed. -- Rink P.W. Springer- http://rink.nu Richter: Tribute? You steal men's souls, and make them your slaves! Dracula: Perhaps the same could be said of all religions. - Castlevania: Symphony of the Night pgpa9nxeDyVMF.pgp Description: PGP signature
NFS clients freeze and can not disconnect
I have a series of machines 6.0 stable (various dates), 6.1 stable (various dates) that freeze if the NFS sever they are connected to becomes unresponsive or crashes. Was able to confirm this behavior for both i386 and AMD64. A 5.3 machine connected to the same nfs server was able to umount -f the volume. I was able to reproduce the problem in a test environment. Tried TCP, UDP connections, soft mount and a retry count of 1. It doesn't seem to matter whether the server is 6.X or 5.X (tested in both), it is the 6.X client that has the problem. Searching the archives seem to be a known issue. Is there a patch? Or has it recently being fixed? The dates of my 6.X client machines varies, but are 6.0 stable up to 6.1Stable may 29. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-R ? 6-Stable ? 5.5-R ?
Rink Springer writes: On Wed, Jun 28, 2006 at 04:09:14AM -0400, Francisco Reyes wrote: So far 6.X has been for the most part stable as NFS sever for us.. but one of our servers has been hanging crashing and NFSD was showing as status GIANT You'll want to upgrade to the latest 6-STABLE, where this bug has been fixed. RELENG_6? From what I can tell that is stable RELENG_6 The line of development for FreeBSD-6.X, also known as FreeBSD 6-STABLE FreeBSD 6.1-STABLE #4: Sun Jun 25 Was it fixed after Jun 25? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trap 12: supervisor write, page not present on 6.1-STABLE Tue May 16 2006
On Tue, 27 Jun 2006, Stanislaw Halik wrote:
On Tue, Jun 27, 2006, Robert Watson wrote:
6.1-STABLE crashed on me. I'm providing a backtrace. Could any of you,
experienced people, suggest me if it's a hardware problem or is it an
error inside the OS?
This is a known bug in the TCP code; a large set of outstanding changes is
present in 7.x that will fix the problem when merged. However, I recently
had push-back on merging the larger batch of changes, so am looking at
merging a workaround that will also correct the problem without the larger
set of architectural changes. I hope to have a chance to look at that in
detail this weekend.
I'm glad to know that it isn't either unknown or hardware-related. Thank you
for your prompt reply!
Per my earlier e-mail, I had hoped to merge a larger set of changes from HEAD
that resolve the underlying problem here (that inpcb's can be detached from a
socket while the socket is still in use), but right now I'm deferring merging
those changes as they are somewhat risky (as they are large). Instead, I've
produced a candidate work-around patch, now attached to kern/97095. This does
not fix the underlying problem, but seeks to narrow the window for the race to
be exercised by avoiding caching a volatile pointer across user memory
copying, which under load can result in blocking I/O. I would be quite
interested in knowing if this resolves the problem in practice -- if so, it's
a definite short-term merge candidate to reduce the symptoms of this problem
until the proper fix can be merged.
http://www.watson.org/~robert/freebsd/netperf/20060628-ip_ctloutput.diff
Thanks,
Robert N M Watson
Computer Laboratory
University of Cambridge
Index: ip_output.c
===
RCS file: /home/ncvs/src/sys/netinet/ip_output.c,v
retrieving revision 1.242.2.9
diff -u -r1.242.2.9 ip_output.c
--- ip_output.c 4 Jun 2006 10:19:34 - 1.242.2.9
+++ ip_output.c 28 Jun 2006 09:03:14 -
@@ -1154,7 +1154,7 @@
struct socket *so;
struct sockopt *sopt;
{
- struct inpcb *inp = sotoinpcb(so);
+ struct inpcb *inp;
int error, optval;
error = optval = 0;
@@ -1187,6 +1187,7 @@
m_free(m);
break;
}
+ inp = sotoinpcb(so);
INP_LOCK(inp);
error = ip_pcbopts(inp, sopt-sopt_name, m);
INP_UNLOCK(inp);
@@ -1209,6 +1210,7 @@
if (error)
break;
+ inp = sotoinpcb(so);
switch (sopt-sopt_name) {
case IP_TOS:
inp-inp_ip_tos = optval;
@@ -1274,6 +1276,7 @@
case IP_MULTICAST_LOOP:
case IP_ADD_MEMBERSHIP:
case IP_DROP_MEMBERSHIP:
+ inp = sotoinpcb(so);
error = ip_setmoptions(inp, sopt);
break;
@@ -1283,6 +1286,7 @@
if (error)
break;
+ inp = sotoinpcb(so);
INP_LOCK(inp);
switch (optval) {
case IP_PORTRANGE_DEFAULT:
@@ -1325,6 +1329,7 @@
req = mtod(m, caddr_t);
len = m-m_len;
optname = sopt-sopt_name;
+ inp = sotoinpcb(so);
error = ipsec4_set_policy(inp, optname, req, len, priv);
m_freem(m);
break;
@@ -1341,6 +1346,7 @@
switch (sopt-sopt_name) {
case IP_OPTIONS:
case IP_RETOPTS:
+ inp = sotoinpcb(so);
if (inp-inp_options)
error = sooptcopyout(sopt,
mtod(inp-inp_options,
@@ -1362,6 +1368,7 @@
case IP_FAITH:
case IP_ONESBCAST:
case IP_DONTFRAG:
+ inp = sotoinpcb(so);
switch (sopt-sopt_name) {
case IP_TOS:
@@ -1427,6 +1434,7 @@
case IP_MULTICAST_LOOP:
case IP_ADD_MEMBERSHIP:
case IP_DROP_MEMBERSHIP:
+ inp = sotoinpcb(so);
error = ip_getmoptions(inp, sopt);
break;
@@ -1441,7 +1449,8 @@
req = mtod(m, caddr_t);
len = m-m_len;
}
- error = ipsec4_get_policy(sotoinpcb(so), req, len, m);
+ inp = sotoinpcb(so);
+ error = ipsec4_get_policy(inp, req, len, m
Re: FreeBSD 6.1 Tor issues (Once More, with Feeling)
On Tue, 27 Jun 2006, Fabian Keil wrote: There was a request for Tor related problem reports a while ago, I couldn't find the message again, but I believe it was posted here. I'm very interested in tracking down this problem, but have had a lot of trouble getting reliable reports of problems -- i.e., ones where I could get any debugging information. I had a similar conversation on these lines yeterday with Roger (Tor author) here at the WEIS conference. If this is easily reproduceable, I would like you to do the following: - Compile in options DDB, options KDB, options BREAK_TO_DEBUGGER, options WITNESS, options WITNESS_SKIPSPIN, options INVARIANTS, options INVARIANT_SUPPORT. - Make sure to have a kernel with debugging symbols for the kernel. - Turn on core dumps. The above debugging options will have a significant performance impact, and may or may not affect the probability of the race or deadlock being exercised. The first question is: - Are there any warnings on the console from WITNESS or other debugging options? If so, please copy/paste them into an e-mail for me. - Does a panic occur? If so, the output of the following comments would be very useful: show pcpu show allpcpu ps show locks show alllocks show lockedvnods trace Then walk the list of all processes listed in 'show alllocks', and run trace on each pid. - Does the hang occur? If so, use a serial break to get into DDB, see the above. In both of the last two cases, attempt to get a core dump. Robert N M Watson Computer Laboratory University of Cambridge Last week I installed: FreeBSD tor.fabiankeil.de 6.1-RELEASE-p2 FreeBSD 6.1-RELEASE-p2 #0: Fri Jun 23 20:06:57 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BIGSLEEP i386. At the moment it is only acting as Tor node http://serifos.eecs.harvard.edu/cgi-bin/desc.pl?q=zwiebelsuppe tor-devel (maintainer CC'd) is running jailed in a Geli image, ntpd, named, cron and sshd are running in the host system and that's about it. No mail or web server and nearly no traffic besides the one caused by Tor. I started Tor Friday night and had to reset the box three times since then. The server just suddenly stops responding, the logs stop as well, therefore I assume it either panics or hangs. I only have remote access, a serial console is available, but it becomes unresponsive as well. I didn't configure DDB yet, so maybe that is to be expected? cron creates some stats every five minutes, a few minutes before a hang this morning the load was: last pid: 7996; load averages: 0.40, 0.37, 0.36 up 0+18:38:2505:55:02 83 processes: 2 running, 66 sleeping, 15 waiting CPU states: 21.3% user, 0.0% nice, 17.8% system, 20.2% interrupt, 40.7% idle Mem: 100M Active, 157M Inact, 102M Wired, 12K Cache, 60M Buf, 134M Free Swap: 1024M Total, 1024M Free PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND 11 root1 171 52 0K 8K RUN857:30 53.61% idle 12 root1 -44 -163 0K 8K WAIT45:22 6.54% swi1: net 23 root1 -68 -187 0K 8K WAIT14:48 2.83% irq12: fxp0 fxp1 7973 root1 960 2264K 1544K RUN 0:00 0.51% top 13 root1 -32 -151 0K 8K WAIT 5:49 0.10% swi4: clock sio 33 root1 171 52 0K 8K pgzero 0:02 0.10% pagezero 3 root1 -80 0K 8K -0:16 0.05% g_up 1586 _tor 14 20099M 97912K kserel 188:36 0.00% tor 15 root1 -160 0K 8K -1:01 0.00% yarrow 1443 root1 -80 0K 8K geli:w 0:49 0.00% g_eli[0] md0 4 root1 -80 0K 8K -0:21 0.00% g_down 35 root1 200 0K 8K syncer 0:17 0.00% syncer 1439 root1 -80 0K 8K mdwait 0:13 0.00% md0 24 root1 -64 -183 0K 8K WAIT 0:08 0.00% irq14: ata0 2 root1 -80 0K 8K -0:07 0.00% g_event 42 root1 -160 0K 8K -0:06 0.00% schedcpu 453 root1 960 2920K 1752K select 0:05 0.00% ntpd 256 _pflogd 1 -580 1548K 1216K bpf 0:05 0.00% pflog pfctls -si: Status: Enabled for 0 days 18:37:52 Debug: Urgent Hostid: 0x1ec3da6b Interface Stats for fxp0 IPv4 IPv6 Bytes In 250778591590 Bytes Out274988633620 Packets In Passed361927600 Blocked 322130 Packets Out Passed368714320 Blocked2650 State Table Total Rate current entries 5290 searches73567507 1096.8/s inserts 6000688.9/s removals
Re: 6.1-R ? 6-Stable ? 5.5-R ?
Was it fixed after Jun 25? This comment fixed it for me: --- Date: Tue, 13 Jun 2006 10:50:29 + (UTC) From: Konstantin Belousov [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], cvs-all@FreeBSD.org Subject: cvs commit: src/sys/nfsserver nfs_serv.c nfs_srvsubs.c kib 2006-06-13 10:50:29 UTC FreeBSD src repository Modified files:(Branch: RELENG_6) sys/nfsservernfs_serv.c nfs_srvsubs.c Log: MFC of the temporary fix for nfsd leaking GIANT. src/sys/nfsserver/nfs_serv.c rev. 1.165 src/sys/nfsserver/nfs_srvsubs.c rev. 1.141 Approved by:pjd (mentor) Revision ChangesPath 1.156.2.3 +16 -0 src/sys/nfsserver/nfs_serv.c 1.136.2.3 +4 -0 src/sys/nfsserver/nfs_srvsubs.c --- Perhaps you could check your revisions of these files? If this does not fix it, something more is certainly going on ... -- Rink P.W. Springer- http://rink.nu Richter: Tribute? You steal men's souls, and make them your slaves! Dracula: Perhaps the same could be said of all religions. - Castlevania: Symphony of the Night pgp0uHgVgNFSB.pgp Description: PGP signature
Re: 6.1-R ? 6-Stable ? 5.5-R ?
Rink Springer writes: FreeBSD src repository Modified files:(Branch: RELENG_6) sys/nfsservernfs_serv.c nfs_srvsubs.c Log: MFC of the temporary fix for nfsd leaking GIANT. src/sys/nfsserver/nfs_serv.c rev. 1.165 src/sys/nfsserver/nfs_srvsubs.c rev. 1.141 Both of those files were older. Approved by:pjd (mentor) Revision ChangesPath 1.156.2.3 +16 -0 src/sys/nfsserver/nfs_serv.c 1.136.2.3 +4 -0 src/sys/nfsserver/nfs_srvsubs.c The above files are what I have. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-R ? 6-Stable ? 5.5-R ?
On Wed, Jun 28, 2006 at 06:23:15AM -0400, Francisco Reyes wrote: Rink Springer writes: FreeBSD src repository Modified files:(Branch: RELENG_6) sys/nfsservernfs_serv.c nfs_srvsubs.c Log: MFC of the temporary fix for nfsd leaking GIANT. src/sys/nfsserver/nfs_serv.c rev. 1.165 src/sys/nfsserver/nfs_srvsubs.c rev. 1.141 Both of those files were older. Approved by:pjd (mentor) Revision ChangesPath 1.156.2.3 +16 -0 src/sys/nfsserver/nfs_serv.c 1.136.2.3 +4 -0 src/sys/nfsserver/nfs_srvsubs.c The above files are what I have. What this means ? That you have _this_ revisions of the files, and your LA skyrocketed ? pgpjIkjbtX0HR.pgp Description: PGP signature
Re: FreeBSD 6.1 Tor issues (Once More, with Feeling)
--- Fabian Keil [EMAIL PROTECTED] wrote: There was a request for Tor related problem reports a while ago, I couldn't find the message again, but I believe it was posted here. Is anyone on this list running a Tor node on FreeBSD 6.1-RELEASE or later with similar or higher load? I am hitting the same issue still Fabian. I had that PR closed as works for me with insignificant testing. I am still crashing (as before) but maybe only once every week or two instead of every couple hours with 6.1 RELEASE. The PR really should be reopened. Couple other folk have emailed me with similiar issues offline (and also spoke with it about me on IRC). I am still 99% sure this is NOT A TOR ISSUE!!! I have spoken with many tor users on other platforms and the actual developers and this is not seen by any of them. I can also recreate this crash NOT running tor but just generating a heavy load with freenet and i2p. My gut feeling is still a network code regression between 5.x - 6.x with the stack rewrite. I am at a loss how to troubleshoot this anymore (as noted in the PR and my earlier email). I truly hope somebody (e.g. a developer) can shed some light on this issue or troubleshoot it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Tor issues (Once More, with Feeling)
Peter Thoenen wrote: --- Fabian Keil [EMAIL PROTECTED] wrote: [ ... ] Is anyone on this list running a Tor node on FreeBSD 6.1-RELEASE or later with similar or higher load? I am hitting the same issue still Fabian. I had that PR closed as works for me with insignificant testing. I am still crashing (as before) but maybe only once every week or two instead of every couple hours with 6.1 RELEASE. The PR really should be reopened. Couple other folk have emailed me with similiar issues offline (and also spoke with it about me on IRC). Well, having several people show similar problems will help track the issue down, if only by letting us examine common aspects (ie, this happens on SMP systems, it happens when people are using PF, or IPFW, it only happens to people using vr0, or rl0, or some other specific NIC, etc). I am still 99% sure this is NOT A TOR ISSUE!!! I have spoken with many tor users on other platforms and the actual developers and this is not seen by any of them. I can also recreate this crash NOT running tor but just generating a heavy load with freenet and i2p. It's probably not a TOR issue, no. I gather that you've already run the manufacturer's hardware diagnostics and something like prime95 or memtest86 overnight or longer than 24 hours (ideally)... My gut feeling is still a network code regression between 5.x - 6.x with the stack rewrite. I am at a loss how to troubleshoot this anymore (as noted in the PR and my earlier email). I truly hope somebody (e.g. a developer) can shed some light on this issue or troubleshoot it. It would also be interesting to know whether you can revert to running FreeBSD 5.5 on the same hardware under the same workload and have it stay up for longer. Put your dmesg(s), kernel config files, /etc/make.conf, and best efforts at logging the issue (serial console, running vmstat whatever or sysctl -a kern via cron periodicly to a file), on a webpage someplace, and try to cross-link with other people showing the same problem. Post that URL to a PR and/or the mailing lists... -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Tor issues (Once More, with Feeling)
On Tue, 27 Jun 2006, Peter Thoenen wrote: --- Fabian Keil [EMAIL PROTECTED] wrote: There was a request for Tor related problem reports a while ago, I couldn't find the message again, but I believe it was posted here. Is anyone on this list running a Tor node on FreeBSD 6.1-RELEASE or later with similar or higher load? I am hitting the same issue still Fabian. I had that PR closed as works for me with insignificant testing. I am still crashing (as before) but maybe only once every week or two instead of every couple hours with 6.1 RELEASE. The PR really should be reopened. Couple other folk have emailed me with similiar issues offline (and also spoke with it about me on IRC). In the future, it would be helpful if you replied to the PR saying so. It looks like it was closed at your request as you stated the problem had gone away, so I've been working under the assumption that the problem has gone away, as that's the last information I have. I am still 99% sure this is NOT A TOR ISSUE!!! I have spoken with many tor users on other platforms and the actual developers and this is not seen by any of them. I can also recreate this crash NOT running tor but just generating a heavy load with freenet and i2p. My gut feeling is still a network code regression between 5.x - 6.x with the stack rewrite. I am at a loss how to troubleshoot this anymore (as noted in the PR and my earlier email). I truly hope somebody (e.g. a developer) can shed some light on this issue or troubleshoot it. I have appealed a number of times on the freebsd-security mailing list and eslewhere for information from people who could reproduce the problem. In general the replies I got were that people either had the problem go away with recent 6.x, or that they did not have time or were not interested in helping debug the problem. If you are interested, please take a look at my recent reply to the reported problem, and work through the steps there. I strongly recommend using a serial console on the box. I can only debug a problem if I know it exists, and with enough information, and so far, there's been insufficient information to track down the problem. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vanderpool on FreeBSD
Sorry! Here is the attachment Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning NIIF/HUNGARNET, HUNGARY Key 00F9AF98: 8645 1312 D249 471B DBAE 21A2 9F52 0D1F 00F9 AF98 On Wed, 28 Jun 2006, Mohacsi Janos wrote: Dear All, Does anybody succeed to boot FreeBSD on an Intel Vanderpool capable machine? My colleague tried it and the result is a BTX halt as can be seen on the screenshot attached. He succesfully run unmodified Linux, Windows 2003 under Xen virtual machines, but FreeBSD failed in the boot phase. By the way what is the state of Xen port of FreeBSD? Thanks, Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning NIIF/HUNGARNET, HUNGARY Key 00F9AF98: 8645 1312 D249 471B DBAE 21A2 9F52 0D1F 00F9 AF98 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Vanderpool on FreeBSD
Dear All, Does anybody succeed to boot FreeBSD on an Intel Vanderpool capable machine? My colleague tried it and the result is a BTX halt as can be seen on the screenshot attached. He succesfully run unmodified Linux, Windows 2003 under Xen virtual machines, but FreeBSD failed in the boot phase. By the way what is the state of Xen port of FreeBSD? Thanks, Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning NIIF/HUNGARNET, HUNGARY Key 00F9AF98: 8645 1312 D249 471B DBAE 21A2 9F52 0D1F 00F9 AF98 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.x CVSUP today crashes with zero load ...
On Mon, 26 Jun 2006, Marc G. Fournier wrote: I think this is a useful activity, especially if you've already run extensive memory testing on the box. If you haven't yet done that, I encourage you to take a break from buildworld's and make sure the memory tests pass. I spent several months on and off trying to track down a bug a few years ago, which turned out to be a one bit error in memory on the box. It would appear and disappear based on how the memory page was used -- for debugging kernels, it consistently got mapped to padding in the kernel's bss. For non-debugging kernels, it typically manifested in other usable kernel momory. Changes in kernel versions would move the bit around kernel memory and user memory, resulting in hard to debug failure modes. I wish I'd run the memory test earlier, but the lesson is clear! Is there something that I can run *from* FreeBSD, remotely, to do this? Not that I know of. In the past, the discussion has been held about adopting a memory tester into the boot loader, which is almost certainly the right place to put it (before VM kicks off and we load many megabytes of critical data structures, etc). Some hands to make this happen would be most welcome. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trap 12: supervisor write, page not present on 6.1-STABLE Tue May 16 2006
On Wed, Jun 28, 2006, Robert Watson wrote: 6.1-STABLE crashed on me. I'm providing a backtrace. Could any of you, experienced people, suggest me if it's a hardware problem or is it an error inside the OS? This is a known bug in the TCP code; a large set of outstanding changes is present in 7.x that will fix the problem when merged. However, I recently had push-back on merging the larger batch of changes, so am looking at merging a workaround that will also correct the problem without the larger set of architectural changes. I hope to have a chance to look at that in detail this weekend. I'm glad to know that it isn't either unknown or hardware-related. Thank you for your prompt reply! Per my earlier e-mail, I had hoped to merge a larger set of changes from HEAD that resolve the underlying problem here (that inpcb's can be detached from a socket while the socket is still in use), but right now I'm deferring merging those changes as they are somewhat risky (as they are large). Instead, I've produced a candidate work-around patch, now attached to kern/97095. This does not fix the underlying problem, but seeks to narrow the window for the race to be exercised by avoiding caching a volatile pointer across user memory copying, which under load can result in blocking I/O. I would be quite interested in knowing if this resolves the problem in practice -- if so, it's a definite short-term merge candidate to reduce the symptoms of this problem until the proper fix can be merged. http://www.watson.org/~robert/freebsd/netperf/20060628-ip_ctloutput.diff Thank you for the patch. I'll let you know in few days if the crash occurs again. It's quite reproducible (crashed yesterday in the same code path). pgpeerBZV3ylV.pgp Description: PGP signature
Re: FreeBSD 6.x CVSUP today crashes with zero load ...
On Tuesday 27 June 2006 22:15, Matthew D. Fuller wrote: On Tue, Jun 27, 2006 at 01:16:11PM + I heard the voice of Eprha Carvajal, and lo! it spake thus: I see no ACPI capability in the processor features ACPI is not a CPU feature. There is an 'ACPI' feature bit, but I think it has to do with preserving the TSC rate while the CPU is throttled. It's not required for core ACPI operation. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vanderpool on FreeBSD
Here is a link where you can find screenshot. http://skye.ki.iif.hu/~mohacsi/freebsd/xen-vt-freebsd.png I try to find a way to boot with serial console in order to capture the first error message. Regards, Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning NIIF/HUNGARNET, HUNGARY Key 00F9AF98: 8645 1312 D249 471B DBAE 21A2 9F52 0D1F 00F9 AF98 On Wed, 28 Jun 2006, Mohacsi Janos wrote: Sorry! Here is the attachment Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning NIIF/HUNGARNET, HUNGARY Key 00F9AF98: 8645 1312 D249 471B DBAE 21A2 9F52 0D1F 00F9 AF98 On Wed, 28 Jun 2006, Mohacsi Janos wrote: Dear All, Does anybody succeed to boot FreeBSD on an Intel Vanderpool capable machine? My colleague tried it and the result is a BTX halt as can be seen on the screenshot attached. He succesfully run unmodified Linux, Windows 2003 under Xen virtual machines, but FreeBSD failed in the boot phase. By the way what is the state of Xen port of FreeBSD? Thanks, Janos Mohacsi Network Engineer, Research Associate, Head of Network Planning NIIF/HUNGARNET, HUNGARY Key 00F9AF98: 8645 1312 D249 471B DBAE 21A2 9F52 0D1F 00F9 AF98 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
bad pte panic, no dump :(
Greetings, FreeBSD/amd64 6.1-STABLE (June 18, 18:44 US/Central), running on Intel EM64T Xeons. got a one-off bad pte panic, and when it tried to dump to a gmirror slice, it hung. Box had been rock stable. Had an issue with a neighbor (NFS server to this box) box yesterday, and had to force reboot it to get the NFS stuff back in sync, and all I thought(!) was ok. The out of the blue, while talking IMAP to this one, got the bad pte panic. when the box came back up, it had a massive amount of fsck to do, and then resync the mirror. While the mirror was re-syncing, there were times when I saw LOTS of processes blocked in ufs or getblk or related wait_chans. I'm not sure there is anything more I can provide (no serial console, and the box is in a colo cage 3.5 hours (by car) north of me. Just an FYI, and suggestions welcome. Thanks for listening to my rant. Larry Rosenman -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
(no subject)
___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
atheros card connectivity diminishes
i'm using an atheros 5212 on 6.x release w/ the ath driver finding that i need to bounce the card fairly often to keep the pipe from diminishing to 1Mps. is there a fix for this? -- David Coder Network Engineer Emeritus, Verio/NTT Telluride, CO Washington, DC ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ufs_dirbad: bad dir
haven't seen one of these in awhile ... June 15th kernel ...
Script started on Wed Jun 28 13:59:08 2006
You have mail.
pluto# kgdb kernel.0 vmcore.1
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined
symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 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 certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-marcel-freebsd.
Unread portion of the kernel message buffer:
/vm: bad dir ino 5936839 at offset 512: mangled entry
panic: ufs_dirbad: bad dir
cpuid = 0
Uptime: 25m2s
Dumping 4031 MB (2 chunks)
chunk 0: 1MB (143 pages) ... ok
chunk 1: 4031MB (1031920 pages) 4015 3999 3983 3967 3951 3935 3919 3903 3887
3871 3855 3839 3823 3807 3791 3775 3759 3743 3727 3711 3695 3679 3663 3647 3631
3615 3599 3583 3567 3551 3535 3519 3503 3487 3471 3455 3439 3423 3407 3391 3375
3359 3343 3327 3311 3295 3279 3263 3247 3231 3215 3199 3183 3167 3151 3135 3119
3103 3087 3071 3055 3039 3023 3007 2991 2975 2959 2943 2927 2911 2895 2879 2863
2847 2831 2815 2799 2783 2767 2751 2735 2719 2703 2687 2671 2655 2639 2623 2607
2591 2575 2559 2543 2527 2511 2495 2479 2463 2447 2431 2415 2399 2383 2367 2351
2335 2319 2303 2287 2271 2255 2239 2223 2207 2191 2175 2159 2143 2127 2111 2095
2079 2063 2047 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839
1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583
1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327
1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071
1055 1039 1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767
751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447
431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127
111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) where
#0 doadump () at pcpu.h:165
#1 0xc049cb62 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc049ce89 in panic (fmt=0xc060d59d ufs_dirbad: bad dir) at
/usr/src/sys/kern/kern_shutdown.c:565
#3 0xc0588f32 in ufs_dirbad (ip=0x0, offset=512, how=0xc060d557 mangled
entry) at /usr/src/sys/ufs/ufs/ufs_lookup.c:599
#4 0xc0588772 in ufs_lookup (ap=0xef0f9aa0) at
/usr/src/sys/ufs/ufs/ufs_lookup.c:287
#5 0xc05ec7a8 in VOP_CACHEDLOOKUP_APV (vop=0x0, a=0x0) at vnode_if.c:150
#6 0xc04e98fa in vfs_cache_lookup (ap=0x0) at vnode_if.h:82
#7 0xc05ec737 in VOP_LOOKUP_APV (vop=0xc0639360, a=0xef0f9b3c) at vnode_if.c:99
#8 0xc04edf75 in lookup (ndp=0xef0f9c18) at vnode_if.h:56
#9 0xc04ed816 in namei (ndp=0xef0f9c18) at /usr/src/sys/kern/vfs_lookup.c:203
#10 0xc04fd920 in kern_rename (td=0xcb592a80, from=0x0, to=0x0,
pathseg=UIO_USERSPACE) at /usr/src/sys/kern/vfs_syscalls.c:3237
#11 0xc04fd829 in rename (td=0xcb592a80, uap=0x0) at
/usr/src/sys/kern/vfs_syscalls.c:3193
#12 0xc05dba67 in syscall (frame=
{tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 134714120, tf_esi =
134690056, tf_ebp = -1077942136, tf_isp = -284189340, tf_ebx = 134690184,
tf_edx = 134690077, tf_ecx = 134664804, tf_eax = 128, tf_trapno = 12, tf_err =
2, tf_eip = 673997415, tf_cs = 51, tf_eflags = 642, tf_esp = -1077942292, tf_ss
= 59}) at /usr/src/sys/i386/i386/trap.c:981
#13 0xc05c90df in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:200
#14 0x0033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) u p 3
#3 0xc0588f32 in ufs_dirbad (ip=0x0, offset=512, how=0xc060d557 mangled
entry) at /usr/src/sys/ufs/ufs/ufs_lookup.c:599
599 panic(ufs_dirbad: bad dir);
(kgdb) list
594
595 mp = ITOV(ip)-v_mount;
596 (void)printf(%s: bad dir ino %lu at offset %ld: %s\n,
597 mp-mnt_stat.f_mntonname, (u_long)ip-i_number,
(long)offset, how);
598 if ((mp-mnt_flag MNT_RDONLY) == 0)
599 panic(ufs_dirbad: bad dir);
600 }
601
602 /*
603 * Do consistency checking on a directory entry:
(kgdb) quit
pluto# exit
exit
Script done on Wed Jun 28 13:59:31 2006
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED]
Yahoo . yscrappy Skype: hub.orgICQ . 7615664___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.x CVSUP today crashes with zero load ...
At 3:34 PM +0100 6/28/06, Robert Watson wrote: On Mon, 26 Jun 2006, Marc G. Fournier wrote: I wish I'd run the memory test earlier, but the lesson is clear! Is there something that I can run *from* FreeBSD, remotely, to do this? Not that I know of. In the past, the discussion has been held about adopting a memory tester into the boot loader, which is almost certainly the right place to put it (before VM kicks off and we load many megabytes of critical data structures, etc). Some hands to make this happen would be most welcome. It doesn't even need to be *inside* the boot loader, does it? Could it be done as an alternate-kernel that could be loaded by the boot-loader? -- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute; Troy, NY; USA ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Tor issues (Once More, with Feeling)
Robert Watson [EMAIL PROTECTED] wrote: On Tue, 27 Jun 2006, Fabian Keil wrote: There was a request for Tor related problem reports a while ago, I couldn't find the message again, but I believe it was posted here. I'm very interested in tracking down this problem, but have had a lot of trouble getting reliable reports of problems -- i.e., ones where I could get any debugging information. I had a similar conversation on these lines yeterday with Roger (Tor author) here at the WEIS conference. If this is easily reproduceable, I would like you to do the following: - Compile in options DDB, options KDB, options BREAK_TO_DEBUGGER, options WITNESS, options WITNESS_SKIPSPIN, options INVARIANTS, options INVARIANT_SUPPORT. - Make sure to have a kernel with debugging symbols for the kernel. - Turn on core dumps. Done. I expect to get a chance to test the settings in the next 24 hours. The above debugging options will have a significant performance impact, and may or may not affect the probability of the race or deadlock being exercised. The first question is: - Are there any warnings on the console from WITNESS or other debugging options? If so, please copy/paste them into an e-mail for me. So far the logs show nothing unusual, but I noticed that the ssh connection gets unresponsive from time to time. I did a few pings with interesting results: [EMAIL PROTECTED] ~]$ ping 10.0.0.1 | grep 'time=[^0]' 64 bytes from 10.0.0.1: icmp_seq=25 ttl=64 time=1.104 ms 64 bytes from 10.0.0.1: icmp_seq=61 ttl=64 time=2.983 ms 64 bytes from 10.0.0.1: icmp_seq=167 ttl=64 time=1.112 ms 64 bytes from 10.0.0.1: icmp_seq=189 ttl=64 time=1.653 ms 64 bytes from 10.0.0.1: icmp_seq=222 ttl=64 time=1.748 ms 64 bytes from 10.0.0.1: icmp_seq=291 ttl=64 time=1.058 ms 64 bytes from 10.0.0.1: icmp_seq=334 ttl=64 time=1.020 ms 64 bytes from 10.0.0.1: icmp_seq=337 ttl=64 time=1.967 ms 64 bytes from 10.0.0.1: icmp_seq=562 ttl=64 time=1.027 ms 64 bytes from 10.0.0.1: icmp_seq=586 ttl=64 time=1.230 ms [EMAIL PROTECTED] ~]$ ping tor.fabiankeil.de | grep 'time=[^0]' 64 bytes from 81.169.155.246: icmp_seq=70 ttl=64 time=1.920 ms 64 bytes from 81.169.155.246: icmp_seq=79 ttl=64 time=1.587 ms 64 bytes from 81.169.155.246: icmp_seq=402 ttl=64 time=1.062 ms [EMAIL PROTECTED] ~]$ ping localhost | grep 'time=[^0]' 64 bytes from 127.0.0.1: icmp_seq=142 ttl=64 time=1.142 ms 64 bytes from 127.0.0.1: icmp_seq=497 ttl=64 time=1.227 ms 64 bytes from 127.0.0.1: icmp_seq=627 ttl=64 time=1.181 ms 10.0.0.1 is on lo1, 81.169.155.246 is on fxp0, both are filtered with pf. lo0 is skipped. The pings were run locally while tor was running, the usual ping response times are below 0.2 ms. I get even more obscene ping times if I ping from home, but my net connection isn't the best. I'd appreciate if someone with a reliable net connection could confirm the weirdness. Thanks for your time, Robert, I hope to have real information by tomorrow. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
How to enter DDB through a terminal server / remote console ... ?
'k, now that I'm up to 3 6-STABLE servers that are deadlocking, I'm spending time with the remote tech today to get a serial console put online ... how do I drop into DDB remotely, where the serial console is going through a Portmaster Terminal server? issuing CTL-ALT-ESC, I doubt, will work, will it? Thx Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.x CVSUP today crashes with zero load ...
On Wed, Jun 28, 2006 at 10:29:04AM -0400 I heard the voice of John Baldwin, and lo! it spake thus: There is an 'ACPI' feature bit, but I think it has to do with preserving the TSC rate while the CPU is throttled. It's not required for core ACPI operation. Ah, well, I stand corrected. I have a number of systems with ACPI, but none of them ever showed such a bit. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Tor issues (Once More, with Feeling)
Robert Watson [EMAIL PROTECTED] wrote: - Are there any warnings on the console from WITNESS or other debugging options? I just got: Jun 28 23:01:19 tor kernel: lock order reversal: Jun 28 23:01:19 tor kernel: 1st 0xc3795000 kqueue (kqueue) @ /usr/src/sys/kern/kern_event.c:1053 Jun 28 23:01:19 tor kernel: 2nd 0xc1043144 system map (system map) @ /usr/src/sys/vm/vm_map.c:2390 Jun 28 23:01:20 tor kernel: KDB: stack backtrace: Jun 28 23:01:20 tor kernel: kdb_backtrace(0,,c0711af0,c0713440,c06db624) at kdb_backtrace+0x29 Jun 28 23:01:20 tor kernel: witness_checkorder(c1043144,9,c06b90a8,956) at witness_checkorder+0x578 Jun 28 23:01:20 tor kernel: _mtx_lock_flags(c1043144,0,c06b90a8,956) at _mtx_lock_flags+0x5b Jun 28 23:01:20 tor kernel: _vm_map_lock(c10430c0,c06b90a8,956) at _vm_map_lock+0x26 Jun 28 23:01:20 tor kernel: vm_map_remove(c10430c0,c3bc6000,c3bc8000,d6f55b30,c0623361) at vm_map_remove+0x1f Jun 28 23:01:20 tor kernel: kmem_free(c10430c0,c3bc6000,2000,d6f55b48,c062524f) at kmem_free+0x25 Jun 28 23:01:20 tor kernel: page_free(c3bc6000,2000,22,2000,d6f55b60) at page_free+0x29 Jun 28 23:01:20 tor kernel: uma_large_free(c3ba5140) at uma_large_free+0x7b Jun 28 23:01:20 tor kernel: free(c3bc6000,c06d8980,c3bc6000,c483,1400) at free+0xc5 Jun 28 23:01:20 tor kernel: kqueue_expand(c3795000,c06d8a40,500,0) at kqueue_expand+0xd7 Jun 28 23:01:20 tor kernel: kqueue_register(c3795000,d6f55bf4,c3a8f480,1,0) at kqueue_register+0x1b8 Jun 28 23:01:20 tor kernel: kern_kevent(c3a8f480,3,19,200,d6f55cc8) at kern_kevent+0xc9 Jun 28 23:01:20 tor kernel: kevent(c3a8f480,d6f55d04,6,2,212) at kevent+0x55 Jun 28 23:01:20 tor kernel: syscall(2824003b,80e003b,bfbf003b,cb87000,80d5020) at syscall+0x22f Jun 28 23:01:20 tor kernel: Xint0x80_syscall() at Xint0x80_syscall+0x1f Jun 28 23:01:20 tor kernel: --- syscall (363, FreeBSD ELF32, kevent), eip = 0x282cc4af, esp = 0xbfbfe9fc, ebp = 0xbfbfea48 --- Looks similar to http://sources.zabbadoz.net/freebsd/lor.html#185. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
em device hangs on ifconfig alias ...
has anyone figured out why the em device 'hangs' for about 30-45 seconds whenever you ifconfig alias a new IP on to the device? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Deadlocks (Was: Re: vmstat 'b' (disk busy?) field keeps climbing ...)
On Mon, 26 Jun 2006, Kostik Belousov wrote: Core dumps are somewhat unconvenient in this situation. Better, sending report to me, follow my advise in http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html 'k, I'm working on getting a serial console working on one of the 3 servers that I'm getting these 'deadlocks' on ... I've upgraded the OS to the latest -STABLE (so that I'm not wasting ppls time on a bug that might already be fixed), and adding in the various options as detailed in the handbook URL above ... First question, what should I expect? A bunch of messages to the console? A slow as a dog server (ie. the INVARIANTS stuff)? or nothing until the deadlock actually occurs? thx ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
configuring sio1 for serial console ...
Following hte instructions in the Handbook, I've added the following line to my kernel config: device sio1 at isa? port IO_COM2 flags 0x10 irq 3 but, when I try to build it: config: /usr/src/sys/i386/conf/kernel:71: syntax error *** Error code 1 so, obviously that is wrong for 6.x? :( Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Tor issues (Once More, with Feeling)
On Wed, 28 Jun 2006, Fabian Keil wrote: Robert Watson [EMAIL PROTECTED] wrote: - Are there any warnings on the console from WITNESS or other debugging options? I just got: Jun 28 23:01:19 tor kernel: lock order reversal: Jun 28 23:01:19 tor kernel: 1st 0xc3795000 kqueue (kqueue) @ /usr/src/sys/kern/kern_event.c:1053 Jun 28 23:01:19 tor kernel: 2nd 0xc1043144 system map (system map) @ /usr/src/sys/vm/vm_map.c:2390 Jun 28 23:01:20 tor kernel: KDB: stack backtrace: Jun 28 23:01:20 tor kernel: kdb_backtrace(0,,c0711af0,c0713440,c06db624) at kdb_backtrace+0x29 Jun 28 23:01:20 tor kernel: witness_checkorder(c1043144,9,c06b90a8,956) at witness_checkorder+0x578 Jun 28 23:01:20 tor kernel: _mtx_lock_flags(c1043144,0,c06b90a8,956) at _mtx_lock_flags+0x5b Jun 28 23:01:20 tor kernel: _vm_map_lock(c10430c0,c06b90a8,956) at _vm_map_lock+0x26 Jun 28 23:01:20 tor kernel: vm_map_remove(c10430c0,c3bc6000,c3bc8000,d6f55b30,c0623361) at vm_map_remove+0x1f Jun 28 23:01:20 tor kernel: kmem_free(c10430c0,c3bc6000,2000,d6f55b48,c062524f) at kmem_free+0x25 Jun 28 23:01:20 tor kernel: page_free(c3bc6000,2000,22,2000,d6f55b60) at page_free+0x29 Jun 28 23:01:20 tor kernel: uma_large_free(c3ba5140) at uma_large_free+0x7b Jun 28 23:01:20 tor kernel: free(c3bc6000,c06d8980,c3bc6000,c483,1400) at free+0xc5 Jun 28 23:01:20 tor kernel: kqueue_expand(c3795000,c06d8a40,500,0) at kqueue_expand+0xd7 Jun 28 23:01:20 tor kernel: kqueue_register(c3795000,d6f55bf4,c3a8f480,1,0) at kqueue_register+0x1b8 Jun 28 23:01:20 tor kernel: kern_kevent(c3a8f480,3,19,200,d6f55cc8) at kern_kevent+0xc9 Jun 28 23:01:20 tor kernel: kevent(c3a8f480,d6f55d04,6,2,212) at kevent+0x55 Jun 28 23:01:20 tor kernel: syscall(2824003b,80e003b,bfbf003b,cb87000,80d5020) at syscall+0x22f Jun 28 23:01:20 tor kernel: Xint0x80_syscall() at Xint0x80_syscall+0x1f Jun 28 23:01:20 tor kernel: --- syscall (363, FreeBSD ELF32, kevent), eip = 0x282cc4af, esp = 0xbfbfe9fc, ebp = 0xbfbfea48 --- Looks similar to http://sources.zabbadoz.net/freebsd/lor.html#185. Could you run vmstat -z, netstat -m, and vmstat -m please? Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Where to start from
Hi, I have installed FreeBSD 5.5 . My computer is still not hooked to the network. I would like to start working on it. what should I start with as I have never worked with BSD before. are there any good tutorials to start with? Thanks -- What we see depends mainly on what we look for. -MIHIR ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Where to start from
On 6/28/06, Mihir Sanghavi [EMAIL PROTECTED] wrote: Hi, I have installed FreeBSD 5.5 . My computer is still not hooked to the network. I would like to start working on it. what should I start with as I have never worked with BSD before. are there any good tutorials to start with? FreeBSD has excellent documentation located at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ Also visit http://www.freebsddiary.org/ Good luck! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Where to start from
Mihir Sanghavi wrote: Hi, I have installed FreeBSD 5.5 . My computer is still not hooked to the network. I would like to start working on it. what should I start with as I have never worked with BSD before. are there any good tutorials to start with? Thanks Start again, this time install FreeBSD 6.1 instead. Then proceed to http://www.freebsd.org/docs.html . ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to enter DDB through a terminal server / remote console ... ?
On Wed, 28 Jun 2006, User Freebsd wrote: 'k, now that I'm up to 3 6-STABLE servers that are deadlocking, I'm spending time with the remote tech today to get a serial console put online ... how do I drop into DDB remotely, where the serial console is going through a Portmaster Terminal server? issuing CTL-ALT-ESC, I doubt, will work, will it? If configured to use a serial console (console=comconsole in loader.conf), you can enter the debugger with BREAK_TO_DEBUGGER in the kernel config by sending a serial break. With my portmasters, I telnet to a TCP port to connect to the serial console, so I send a telnet break, using ^]send break. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: configuring sio1 for serial console ...
On Wed, 28 Jun 2006, User Freebsd wrote: Following hte instructions in the Handbook, I've added the following line to my kernel config: device sio1 at isa? port IO_COM2 flags 0x10 irq 3 but, when I try to build it: config: /usr/src/sys/i386/conf/kernel:71: syntax error *** Error code 1 so, obviously that is wrong for 6.x? :( Instead of changing your kernel config, edit the sio1 entries in /boot/device.hints. (This assumes you left device sio in your kernel -- if not, you need to re-add it). Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to enter DDB through a terminal server / remote console ... ?
On Wed, 28 Jun 2006, Robert Watson wrote: On Wed, 28 Jun 2006, User Freebsd wrote: 'k, now that I'm up to 3 6-STABLE servers that are deadlocking, I'm spending time with the remote tech today to get a serial console put online ... how do I drop into DDB remotely, where the serial console is going through a Portmaster Terminal server? issuing CTL-ALT-ESC, I doubt, will work, will it? If configured to use a serial console (console=comconsole in loader.conf), you can enter the debugger with BREAK_TO_DEBUGGER in the kernel config by sending a serial break. With my portmasters, I telnet to a TCP port to connect to the serial console, so I send a telnet break, using ^]send break. Have you ever had a problem with this warning: (useful for remote diagnostics, but also dangerous if you generate a spurious BREAK on the serial port!) in the handbook? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: configuring sio1 for serial console ...
On Wed, June 28, 2006 2:58 pm, User Freebsd wrote: Following hte instructions in the Handbook, I've added the following line to my kernel config: device sio1 at isa? port IO_COM2 flags 0x10 irq 3 but, when I try to build it: config: /usr/src/sys/i386/conf/kernel:71: syntax error *** Error code 1 so, obviously that is wrong for 6.x? :( Here's how I did it (taken from our internal wiki so there's no real formatting): Enabling a Serial Console The following will allow you to use the Tyan SMDC hardware and Tyan TSO software to remotely connect to a FreeBSD box and control it as if you were sitting in front of it. It works at the hardware level, giving you remote access to the boot sequence, BIOS messages, hardware monitoring, and a serial console (over TCP/IP). You'll need to configure the OS to use a serial console in order to see anything once the boot loader and OS kernel take over. The following instructions will get things working on FreeBSD. 1. Edit /boot/loader.conf to enable output to serial and video consoles simultaneously: hint.sio.1.flags=0x30 console=comconsole vidconsole comconsole_speed=19200 boot_multicons=yes 2. Edit /etc/make.conf to set the serial console speed (used when we recompile the boot blocks): BOOT_COMCONSOLE_PORT=0x2F8 BOOT_COMCONSOLE_SPEED=19220 3. Edit /etc/ttys to enable the serial console and set the console speed used: ttyd1 /usr/libexec/getty std.19200 vt100 on secure 4. Rebuild the boot loader cd /usr/src/sys/boot make clean make make install 5. Install the new boot blocks bsdlabel -B /dev/ad4s1 6. Reboot shutdown -r now 7. Voila! All output will now go to the serial console and the video console simultaneously. Once the init process starts, a separate getty process will be loaded for the serial console. Connecting via the serial console will display a login screen, same as connecting via the video console, SSH, telnet, etc. Freddie Cash [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: configuring sio1 for serial console ...
On Wed, 28 Jun 2006, Robert Watson wrote: On Wed, 28 Jun 2006, User Freebsd wrote: Following hte instructions in the Handbook, I've added the following line to my kernel config: device sio1 at isa? port IO_COM2 flags 0x10 irq 3 but, when I try to build it: config: /usr/src/sys/i386/conf/kernel:71: syntax error *** Error code 1 so, obviously that is wrong for 6.x? :( Instead of changing your kernel config, edit the sio1 entries in /boot/device.hints. (This assumes you left device sio in your kernel -- if not, you need to re-add it). 'k, re-adding ... and I take it there is no more 'DDB_UNATTENDED' option? Something equivalent? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to enter DDB through a terminal server / remote console ... ?
On Wed, Jun 28, 2006 at 07:34:43PM -0300, User Freebsd wrote: On Wed, 28 Jun 2006, Robert Watson wrote: On Wed, 28 Jun 2006, User Freebsd wrote: 'k, now that I'm up to 3 6-STABLE servers that are deadlocking, I'm spending time with the remote tech today to get a serial console put online ... how do I drop into DDB remotely, where the serial console is going through a Portmaster Terminal server? issuing CTL-ALT-ESC, I doubt, will work, will it? If configured to use a serial console (console=comconsole in loader.conf), you can enter the debugger with BREAK_TO_DEBUGGER in the kernel config by sending a serial break. With my portmasters, I telnet to a TCP port to connect to the serial console, so I send a telnet break, using ^]send break. Have you ever had a problem with this warning: (useful for remote diagnostics, but also dangerous if you generate a spurious BREAK on the serial port!) in the handbook? You can use ALT_BREAK_TO_DEBUGGER which uses the CR ~ ^b sequence if you are worried about stray breaks. Andrew ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to enter DDB through a terminal server / remote console ... ?
On Wed, 28 Jun 2006, User Freebsd wrote: On Wed, 28 Jun 2006, Robert Watson wrote: On Wed, 28 Jun 2006, User Freebsd wrote: 'k, now that I'm up to 3 6-STABLE servers that are deadlocking, I'm spending time with the remote tech today to get a serial console put online ... how do I drop into DDB remotely, where the serial console is going through a Portmaster Terminal server? issuing CTL-ALT-ESC, I doubt, will work, will it? If configured to use a serial console (console=comconsole in loader.conf), you can enter the debugger with BREAK_TO_DEBUGGER in the kernel config by sending a serial break. With my portmasters, I telnet to a TCP port to connect to the serial console, so I send a telnet break, using ^]send break. Have you ever had a problem with this warning: (useful for remote diagnostics, but also dangerous if you generate a spurious BREAK on the serial port!) in the handbook? Yes. It's unusual, but once in a while I get a nervous serial port. If you experience this, type Cont to continue, and then recompile your kernel with ALT_BREAK_TO_DEBUGGER but without BREAK_TO_DEBUGGER. Here's the notes entry: # Solaris implements a new BREAK which is initiated by a character # sequence CR ~ ^b which is similar to a familiar pattern used on # Sun servers by the Remote Console. options ALT_BREAK_TO_DEBUGGER I've not had problem a problem on any recent hardware except for my soekris. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: configuring sio1 for serial console ...
On Wed, 28 Jun 2006, User Freebsd wrote: Instead of changing your kernel config, edit the sio1 entries in /boot/device.hints. (This assumes you left device sio in your kernel -- if not, you need to re-add it). 'k, re-adding ... and I take it there is no more 'DDB_UNATTENDED' option? Something equivalent? This is now KDB_UNATTENDED, since it affects by DDB and GDB. KDB is the common debugger framework backend used to implement front-end debuggins ervices. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em device hangs on ifconfig alias ...
In the last episode (Jun 28), User Freebsd said: has anyone figured out why the em device 'hangs' for about 30-45 seconds whenever you ifconfig alias a new IP on to the device? The em driver resets the card when you add an IP to it, and unless you've configured your switch not to autodetect fancy features on that port, it may very well take 45 seconds for it to come up. See: http://www.cisco.com/warp/public/473/12.html Using PortFast and Other Commands to Fix Workstation Startup Connectivity Delays -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Tor issues (Once More, with Feeling)
Robert Watson [EMAIL PROTECTED] wrote: On Wed, 28 Jun 2006, Fabian Keil wrote: Robert Watson [EMAIL PROTECTED] wrote: - Are there any warnings on the console from WITNESS or other debugging options? I just got: Jun 28 23:01:19 tor kernel: lock order reversal: Jun 28 23:01:19 tor kernel: 1st 0xc3795000 kqueue (kqueue) Looks similar to http://sources.zabbadoz.net/freebsd/lor.html#185. Could you run vmstat -z, netstat -m, and vmstat -m please? I wish I could. The machine died before I read your message. I was logged in on the serial console running tail -f /var/log/messages. Last messages were: Jun 29 00:42:20 tor kernel: Memory modified after free 0xc4275000(2048) val=a020c0de @ 0xc4275000 Jun 29 00:42:20 tor kernel: Memory modified after free 0xc4055800(2048) val=a020c0de @ 0xc4055800 Jun 29 00:42:20 tor kernel: Memory modified after free 0xc4ca(2048) val=a020c0de @ 0xc4ca Jun 29 00:42:20 tor kernel: Memory modified after free 0xc39ef000(2048) val=a020c0de @ 0xc39ef000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc4bd7000(2048) val=a020c0de @ 0xc4bd7000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc3c8a000(2048) val=a020c0de @ 0xc3c8a000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc33bd000(2048) val=a020c0de @ 0xc33bd000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc3f1d000(2048) val=a020c0de @ 0xc3f1d000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc45dc800(2048) val=a020c0de @ 0xc45dc800 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc429e000(2048) val=a020c0de @ 0xc429e000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc3aef800(2048) val=a020c0de @ 0xc3aef800 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc432a000(2048) val=a020c0de @ 0xc432a000 Jun 29 00:42:24 tor kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=34263674 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc3dff800(2048) val=a020c0d Ctrl+Alt+ESC didn't trigger any reaction, so I caused a reset through the ISP's webinterface. Now the system appears to be hosed, at least FreeBSD never reaches the login: PXELINUX 3.11 2005-09-02 Copyright (C) 1994-2005 H. Peter Anvin Booting from local disk... 1 Linux 2 FreeBSD 3 FreeBSD Default: 2 [nothing] Probably something which would be easy to resolve with keyboard access and a screen, but I think I'm forced to use the RecoveryManager. Unfortunately recovery means reinstalling the preconfigured GNU/Linux which I than can replace with FreeBSD again. If there ever was a core dump it will be gone, and so will be kernel.debug. On the bright side you can chose the OS to go with. Should I use Current to see if the problem still exists? Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Expensive timeout?
Just got this on the console of one of hte servers that has been causing problems ... Expensive timeout(9) function: 0xc0520e18(0xc8b223a0) 0.296959250 s not a very informative error, and that is all that was there, nothing before, nothing after ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Expensive timeout?
Oh, wait, does this have something to do with the Deadlock options I just added to the kernel? On Wed, 28 Jun 2006, User Freebsd wrote: Just got this on the console of one of hte servers that has been causing problems ... Expensive timeout(9) function: 0xc0520e18(0xc8b223a0) 0.296959250 s not a very informative error, and that is all that was there, nothing before, nothing after ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to enter DDB through a terminal server / remote console ... ?
On Wed, Jun 28, 2006 at 11:57:58PM +0100, Robert Watson wrote: ... Yes. It's unusual, but once in a while I get a nervous serial port. If you experience this, type Cont to continue, and then recompile your kernel with ALT_BREAK_TO_DEBUGGER but without BREAK_TO_DEBUGGER. Here's the notes entry: I use the ALT_BREAK_TO_DEBUGGER here. -- - [EMAIL PROTECTED] http://www.db.net/~db ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: configuring sio1 for serial console ...
On Wed, 28 Jun 2006, Robert Watson wrote: On Wed, 28 Jun 2006, User Freebsd wrote: Instead of changing your kernel config, edit the sio1 entries in /boot/device.hints. (This assumes you left device sio in your kernel -- if not, you need to re-add it). 'k, re-adding ... and I take it there is no more 'DDB_UNATTENDED' option? Something equivalent? This is now KDB_UNATTENDED, since it affects by DDB and GDB. KDB is the common debugger framework backend used to implement front-end debuggins ervices. Ya, figured this one out when I tried to compile ... someone might want to add a mention of the new options in the ddb man page though :) Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Expensive timeout?
Please don't top-post... User Freebsd wrote: On Wed, 28 Jun 2006, User Freebsd wrote: Just got this on the console of one of hte servers that has been causing problems ... Expensive timeout(9) function: 0xc0520e18(0xc8b223a0) 0.296959250 s not a very informative error, and that is all that was there, nothing before, nothing after ... Oh, wait, does this have something to do with the Deadlock options I just added to the kernel? Yes, if you look in /sys/kern/kern_timeout.c you'll note that the Expensive timeout(9) function printf is inside an #ifdef DIAGNOSTIC. -Jonathan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em device hangs on ifconfig alias ...
Dan Nelson said the following on 6/28/06 3:52 PM: In the last episode (Jun 28), User Freebsd said: has anyone figured out why the em device 'hangs' for about 30-45 seconds whenever you ifconfig alias a new IP on to the device? The em driver resets the card when you add an IP to it, and unless you've configured your switch not to autodetect fancy features on that port, it may very well take 45 seconds for it to come up. For me the em reset actually takes about a second or so per single IP alias. But more aliases you got, longer the timeout becomes. In case you have hundreds (like I do), a single reboot might cost you something like 10-15 minutes of downtime, just for the aliases to come up. That's the primary reason I stay away from the on-board 1Gbps em NICs that almost every Intel server board nowadays comes with. I simply disable them and use a good old (and cheap) Intel PRO/100 fxp compatible PCI NIC instead. It's fast enough and doesn't reset the card when you add an alias. The only downside is that it gives you 100Mbps at most. Does anybody know a better NIC driver alternative when dealing with lots of IP aliases? I have some newer machines with 2 Broadcom chips on-board. I plan to give them a try at some point in the future, but I'm not sure how stable the bge driver is when compared to fxp and em. Regards, Atanas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Expensive timeout?
On Wed, 28 Jun 2006, Jonathan Noack wrote: Please don't top-post... User Freebsd wrote: On Wed, 28 Jun 2006, User Freebsd wrote: Just got this on the console of one of hte servers that has been causing problems ... Expensive timeout(9) function: 0xc0520e18(0xc8b223a0) 0.296959250 s not a very informative error, and that is all that was there, nothing before, nothing after ... Oh, wait, does this have something to do with the Deadlock options I just added to the kernel? Yes, if you look in /sys/kern/kern_timeout.c you'll note that the Expensive timeout(9) function printf is inside an #ifdef DIAGNOSTIC. 'k, but is this something that I should be concerned about, or just ignore? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em device hangs on ifconfig alias ...
On Wed, 28 Jun 2006, Atanas wrote: I have some newer machines with 2 Broadcom chips on-board. I plan to give them a try at some point in the future, but I'm not sure how stable the bge driver is when compared to fxp and em. I'm using the bge driver on our new HP servers, and haven't noticed any problems with them to date ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
