Re: --- trap 0x1, eip = 0, esp = 0xd77cdd7c, ebp = 0 ---
On Mon, Nov 10, 2003 at 01:08:30PM +1030, Kris Kennaway wrote: On Mon, Nov 10, 2003 at 12:51:21PM +1030, Alex Wilkinson wrote: Not sure how to interpret these errors on the console ?? Running: FreeBSD 5.1-CURRENT #4: Thu Nov 6 16:49:21 CST 2003 Part of a backtrace from an error detected by WITNESS. There was more above that that you didn't post. Kris or anyone, What can I do to deal with this errror ? From the console this is the error that appears: backtrace(c0883a21,c0971e6c,c088a4f4,c088a4f4,c088b844) at backtrace+0x17 witness_lock(c0971e6c,8,c088b844,26d,d77cda24) at witness_lock+0x672 _mtx_lock_flags(c0971e6c,0,c088b844,26d,0) at _mtx_lock_flags+0xba tcp_usr_rcvd(c4e66000,80,c0690520,c0884028,3b9aca00) at tcp_usr_rcvd+0x30 soreceive(c4e66000,d77cda98,d77cdaa4,d77cda9c,0) at soreceive+0x8ef nfsrv_rcv(c4e66000,c4e26780,4,28,60f4) at nfsrv_rcv+0x87 sowakeup(c4e66000,c4e6604c,c088af2f,446,108) at sowakeup+0x91 tcp_input(c1d32900,14,c094b5d0,c094a820,2b3) at tcp_input+0x133e ip_input(c1d32900,0,c08891b3,89,0) at ip_input+0x92a netisr_processqueue(c09700d0,0,c08891b3,e5,c46f70c0) at netisr_processqueue+0x8e swi_net(0,0,c087e536,21f,c1d211e4) at swi_net+0x98 ithread_loop(c1d18580,d77cdd48,c087e39c,311,1) at ithread_loop+0x192 fork_exit(c0656420,c1d18580,d77cdd48) at fork_exit+0xb4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd77cdd7c, ebp = 0 --- Thanks - aW ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: taskqueue patch
On Mon, Nov 10, 2003 at 09:02:03AM +, Doug Rabson wrote: I wasn't involved in converting taskqueue from 4.x-style SWIs to kernel threads so I can't be sure but this does look reasonable. I've been wondering about the 'not exiting' diagnostic from init for a while myself. Hi Doug, What are SWIs ? - aW ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: erroneous message from locked-up machine
Can someone please elaborate on the acronym KVA ?
$ sysctl -d kern.ipc.maxpipekva
kern.ipc.maxpipekva: Pipe KVA limit
This doesn't tell me enough.
- aW
On Tue, Nov 11, 2003 at 04:46:47AM +1100, Bruce Evans wrote:
I came in to work today to find one of my -current machines unable to
open a pipe. (This probably had a lot to do with the spamd that went
stark raving nutters overnight, but that's a separate problem.) A
power cycle fixed the problem, but /var/log/messages was filled with:
Nov 10 11:05:44 bewilderbeast kernel: kern.maxpipekva exceeded, please see
tuning(7).
Interesting.
bewilderbeast~;sysctl kern.maxpipekva
sysctl: unknown oid 'kern.maxpipekva'
bewilderbeast~;
The following patch fixes this and some nearby style bugs:
- source style bug: line too line
- output style bugs: comma splice, verboseness (helps make the source line
too long), and kernel message terminated with a ..
%%%
Index: sys_pipe.c
===
RCS file: /home/ncvs/src/sys/kern/sys_pipe.c,v
retrieving revision 1.158
diff -u -2 -r1.158 sys_pipe.c
--- sys_pipe.c9 Nov 2003 09:17:24 - 1.158
+++ sys_pipe.c10 Nov 2003 17:21:47 -
@@ -331,5 +331,5 @@
if (error != KERN_SUCCESS) {
if (ppsratecheck(lastfail, curfail, 1))
- printf(kern.maxpipekva exceeded, please see
tuning(7).\n);
+ printf(kern.ipc.maxpipekva exceeded; see
tuning(7)\n);
return (ENOMEM);
}
%%%
And tuning(7) doesn't mention this, either.
Is this just work-in-progress, or did someone forget to commit something?
Seems like tuning pipe kva is completely absent in tuning(7) (so the above
message can be shortened further). You can tune kva generally as documented
there, but the pipe limit is separate.
PS: Lesson of the day: no pipe KVA, no su. Great fun on remote
machines! :-)
It's interesting that su was the point of failure. It uses a pipe hack
for IPC. Otherwise it doesn't use pipes, at least direectly. It
shouldn't need to use the pipe hack. My version uses signals instead.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel memory leak in ATAPI/CAM or ATAng?
On Thu, Nov 06, 2003 at 08:08:31AM -0800, Kevin Oberman wrote: Any ideas on where I can look for more information? I'm going to try doing some monitoring with vmstat while running to see if I can spot anything, but I am not sure just what I am looking for. The VM system is not something I know much about, but I did read Terry Lambert's excellent message to current on KVM tuning and I'm hoping that this might help, but, if there really is a memory leak, tuning will not fix it. Got a link to ...Terry Lambert's excellent message to current on KVM tuning.. ? Very keen to read it. - aW ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
--- trap 0x1, eip = 0, esp = 0xd77cdd7c, ebp = 0 ---
Not sure how to interpret these errors on the console ?? Running: FreeBSD 5.1-CURRENT #4: Thu Nov 6 16:49:21 CST 2003 backtrace(c0883a21,c0971e6c,c088a4f4,c088a4f4,c088b844) at backtrace+0x17 witness_lock(c0971e6c,8,c088b844,26d,d77cda24) at witness_lock+0x672 _mtx_lock_flags(c0971e6c,0,c088b844,26d,0) at _mtx_lock_flags+0xba tcp_usr_rcvd(c4e66000,80,c0690520,c0884028,3b9aca00) at tcp_usr_rcvd+0x30 soreceive(c4e66000,d77cda98,d77cdaa4,d77cda9c,0) at soreceive+0x8ef nfsrv_rcv(c4e66000,c4e26780,4,28,60f4) at nfsrv_rcv+0x87 sowakeup(c4e66000,c4e6604c,c088af2f,446,108) at sowakeup+0x91 tcp_input(c1d32900,14,c094b5d0,c094a820,2b3) at tcp_input+0x133e ip_input(c1d32900,0,c08891b3,89,0) at ip_input+0x92a netisr_processqueue(c09700d0,0,c08891b3,e5,c46f70c0) at netisr_processqueue+0x8e swi_net(0,0,c087e536,21f,c1d211e4) at swi_net+0x98 ithread_loop(c1d18580,d77cdd48,c087e39c,311,1) at ithread_loop+0x192 fork_exit(c0656420,c1d18580,d77cdd48) at fork_exit+0xb4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd77cdd7c, ebp = 0 --- Anyone have a clue ? - aW ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: --- trap 0x1, eip = 0, esp = 0xd77cdd7c, ebp = 0 ---
On Mon, Nov 10, 2003 at 01:08:30PM +1030, Kris Kennaway wrote: Not sure how to interpret these errors on the console ?? Running: FreeBSD 5.1-CURRENT #4: Thu Nov 6 16:49:21 CST 2003 Part of a backtrace from an error detected by WITNESS. There was more above that that you didn't post. There wasn't actually: Starting sshd. Starting sendmail. Initial i386 initialization:. Additional ABI support: linux. Starting cron. Local package initialization: Samba. Additional TCP options:. Starting moused:. Starting inetd. Starting background file system checks in 60 seconds. Mon Nov 10 10:38:35 CST 2003 FreeBSD/i386 (hostname.dsto.defence.gov.au) (ttyv0) login: backtrace(c0883a21,c0971e6c,c088a4f4,c088a4f4,c088b844) at backtrace+0x17 witness_lock(c0971e6c,8,c088b844,26d,d77cda24) at witness_lock+0x672 _mtx_lock_flags(c0971e6c,0,c088b844,26d,0) at _mtx_lock_flags+0xba tcp_usr_rcvd(c4e66000,80,c0690520,c0884028,3b9aca00) at tcp_usr_rcvd+0x30 soreceive(c4e66000,d77cda98,d77cdaa4,d77cda9c,0) at soreceive+0x8ef nfsrv_rcv(c4e66000,c4e26780,4,28,60f4) at nfsrv_rcv+0x87 sowakeup(c4e66000,c4e6604c,c088af2f,446,108) at sowakeup+0x91 tcp_input(c1d32900,14,c094b5d0,c094a820,2b3) at tcp_input+0x133e ip_input(c1d32900,0,c08891b3,89,0) at ip_input+0x92a netisr_processqueue(c09700d0,0,c08891b3,e5,c46f70c0) at netisr_processqueue+0x8e swi_net(0,0,c087e536,21f,c1d211e4) at swi_net+0x98 ithread_loop(c1d18580,d77cdd48,c087e39c,311,1) at ithread_loop+0x192 fork_exit(c0656420,c1d18580,d77cdd48) at fork_exit+0xb4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd77cdd7c, ebp = 0 --- How can I help debug this error ? - aW ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the PS/2 mouse problem
On Wed, Nov 05, 2003 at 08:33:58PM -0700, Scott Long wrote: One thought that I had was to make psmintr() be INTR_FAST. I need to stare at the code some more to fully understand it, but it looks like it wouldn't be all that hard to do. Basically just use the interrupt handler to pull all of the data out of the hardware and into a ring buffer in memory, and then a fast taskqueue to process that ring buffer. It would at least answer the question of whether the observed problems are due to ithread latency. And if done right, no locks would be needed in psmintr(). I seemed to have solved my mouse problem: [http://www.mail-archive.com/[EMAIL PROTECTED]/msg62824.html]. Solution: I disabled IPCA in the BIOS and the mouse problem went away. Does IPCA have anything to do with ACPI. Yes, I have googled and looked at anandtech forums and had no luck. In disabling IPCA have I disabled ACPI ? - aW ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[buildkernel fail] -Werror if_xe.c:1832: warning: `xe_reg_dump' defined but not used
CVSup'd today [Thu Nov 6 15:09:02 CST 2003]. buildkernel fails on a warning. $ make buildkernel ... cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/dev/wi/if_wi_pci.c cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/dev/xe/if_xe.c /usr/src/sys/dev/xe/if_xe.c:1832: warning: `xe_reg_dump' defined but not used *** 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. Regards - aW ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [buildkernel fail] -Werror if_xe.c:1832: warning: `xe_reg_dump' defined but not used
On Thu, Nov 06, 2003 at 03:33:25PM +1030, Kris Kennaway wrote: On Thu, Nov 06, 2003 at 03:10:49PM +1030, Alex Wilkinson wrote: CVSup'd today [Thu Nov 6 15:09:02 CST 2003]. buildkernel fails on a warning. Wasn't this fixed this morning? Yes. I didn't realise until investigation that I was missing a CTM delta. All ok now. - aW ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New PNP0303 and aPic question
On Tue, Nov 04, 2003 at 12:56:07PM -0500, John Baldwin wrote: Yes. As long as you have 'device apic' in your kernel config, APICs will be used to route interrupts even on UP machines if the machine includes an MP Table or ACPI is being used and it contains an MADT. Reading thread and not following the acronyms. Ok 2 questions: 1. what is an MP Table ? 2. What is MADT ? Thanks - aW ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Was: More ULE bugs fixed. Is: Mouse problem?
On Tue, Nov 04, 2003 at 11:13:26PM +0100, Morten Johansen wrote: Me too. Have had this problem since I got a Intellimouse PS/2 wheel-mouse. (It worked fine with previous mice (no wheel)). With any scheduler in 5-CURRENT and even more frequent in 4-STABLE, IIRC. Using moused or not doesn't make a difference. Get these messages on console: psmintr: out of sync, and the mouse freezes then goes wild for a few seconds. Can happen under load and sometimes when closing Mozilla (not often). It could be related to the psm-driver. Or maybe I have a bad mouse, I don't know. I will try another mouse, but it does work perfectly in Linux and Windogs... Yes, I have had this problem for a while now also. I have sent mail to current@ a while ago. Date: Thu, 2 Oct 2003 18:31:36 +0930 From: Alex Wilkinson [EMAIL PROTECTED] Subject: sec:u kernel: psmintr: out of sync To: [EMAIL PROTECTED] Hi all, I am switching between several OS's with a Cybex KVW switch. I now seem to have a problem with my mouse (after build world/kernel). FreeBSD 5.1-CURRENT #2: Wed Aug 20 13:28:54 CST 2003 I am getting these messages on the console when I move my mouse, the cursor moves in a very choppy motion (painfully slow). Oct 1 09:46:17 squirm kernel: psmintr: out of sync ( != 0008). Oct 1 09:46:17 squirm kernel: psmintr: discard a byte (1). Oct 1 09:46:17 squirm kernel: psmintr: out of sync ( != 0008). Oct 1 09:46:17 squirm kernel: psmintr: discard a byte (2). Oct 1 09:46:18 squirm kernel: psmintr: out of sync ( != 0008). Oct 1 09:46:18 squirm kernel: psmintr: discard a byte (3). Oct 1 09:46:18 squirm kernel: psmintr: out of sync ( != 0008). Oct 1 09:46:18 squirm kernel: psmintr: re-enable the mouse. Oct 1 09:46:18 squirm kernel: psm: DISABLE_DEV return code:00fa Oct 1 09:46:18 squirm kernel: psm: ENABLE_DEV return code:00fa Oct 1 09:46:20 squirm kernel: psmintr: out of sync ( != 0008). moused is running with the following: moused -p /dev/psm0 -t auto The mouse is a Microsoft IntelliMouse connected to the KVM via a USB-PS/2 adapter. If I boot the same machine into -STABLE this does *not* happen. I have tryed running moused with different protocols without any luck. Can anyone help me solve this problem ? I have to run -STABLE if I can't solve this problem, so any help would be appreciated. Thanks - aW p.s the mouse works fine with: FreeBSD -STABLE, RH Linux, Irix 6.5.20, Tru64, and WinXP. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Was: More ULE bugs fixed. Is: Mouse problem?
On Wed, Nov 05, 2003 at 12:27:04AM +0100, Eirik Oeverby wrote: Just for those interested: I do *not* get any messages at all from the kernel (or elsewhere) when my mouse goes haywire. And it's an absolute truth (just tested back and forth 8 times) that it *only* happens with SCHED_ULE and *only* with old versions (~1.50) and the very latest ones (1.75 as I'm currently running). 1.69 for instance did *not* show any such problems. I will, however, update my kernel again now, to get the latest sched_ule.c (if any changes have been made since 1.75) and to test with the new interrupt handler. I have a suspicion it might be a combination of SCHED_ULE and some signal/message/interrupt handling causing messages to get lost along the way. Because that's exactly how it feels... Question: How can I find out what verion of SCHED_ULE I am running ? - aW ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
buildworld failure: don't know how to make thr_atfork.c
CVSup'd today [Wed Nov 5 17:15:14 CST 2003] and buildworld fails. $ make buildworld . === lib/libpcap yacc -d -p pcapyy -o grammar.c /usr/src/lib/libpcap/../../contrib/libpcap/grammar.y ln -sf grammar.h tokdefs.h lex -t -Ppcapyy /usr/src/lib/libpcap/../../contrib/libpcap/scanner.l scanner.c sed 's/.*/char pcap_version[] = ;/' /usr/src/lib/libpcap/../../contrib/libpcap/VERSION version.c rm -f .depend mkdep -f .depend -a-DHAVE_CONFIG_H -Dyylval=pcapyylval -I/usr/src/lib/libpcap -I. -DINET6 -I/usr/src/lib/libpcap/../../contrib/libpcap grammar.c /usr/src/lib/libpcap/../../contrib/libpcap/pcap-bpf.c /usr/src/lib/libpcap/../../contrib/libpcap/pcap.c /usr/src/lib/libpcap/../../contrib/libpcap/inet.c /usr/src/lib/libpcap/../../contrib/libpcap/gencode.c /usr/src/lib/libpcap/../../contrib/libpcap/optimize.c /usr/src/lib/libpcap/../../contrib/libpcap/nametoaddr.c /usr/src/lib/libpcap/../../contrib/libpcap/etherent.c /usr/src/lib/libpcap/../../contrib/libpcap/savefile.c /usr/src/lib/libpcap/../../contrib/libpcap/bpf/net/bpf_filter.c /usr/src/lib/libpcap/../../contrib/libpcap/bpf_image.c /usr/src/lib/libpcap/../../contrib/libpcap/bpf_dump.c scanner.c version.c === lib/libpthread make: don't know how to make thr_atfork.c. Stop *** Error code 2 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. - aW ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel: psmintr: out of sync
Hi all, I am switching between several OS's with a Cybex KVW switch. I now seem to have a problem with my mouse (after build world/kernel). FreeBSD 5.1-CURRENT #2: Wed Aug 20 13:28:54 CST 2003 I am getting these messages on the console when I move my mouse, the cursor moves in a very choppy motion (painfully slow). Oct 1 09:46:17 squirm kernel: psmintr: out of sync ( != 0008). Oct 1 09:46:17 squirm kernel: psmintr: discard a byte (1). Oct 1 09:46:17 squirm kernel: psmintr: out of sync ( != 0008). Oct 1 09:46:17 squirm kernel: psmintr: discard a byte (2). Oct 1 09:46:18 squirm kernel: psmintr: out of sync ( != 0008). Oct 1 09:46:18 squirm kernel: psmintr: discard a byte (3). Oct 1 09:46:18 squirm kernel: psmintr: out of sync ( != 0008). Oct 1 09:46:18 squirm kernel: psmintr: re-enable the mouse. Oct 1 09:46:18 squirm kernel: psm: DISABLE_DEV return code:00fa Oct 1 09:46:18 squirm kernel: psm: ENABLE_DEV return code:00fa Oct 1 09:46:20 squirm kernel: psmintr: out of sync ( != 0008). moused is running with the following: moused -p /dev/psm0 -t auto The mouse is a Microsoft IntelliMouse connected to the KVM via a USB-PS/2 adapter. If I boot the same machine into -STABLE this does *not* happen. I have tryed running moused with different protocols without any luck. Can anyone help me solve this problem ? I have to run -STABLE if I can't solve this problem, so any help would be appreciated. Thanks - aW p.s the mouse works fine with: RH Linux, Irix 6.5.20, Tru64, and WinXP. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
