Re: non-recursive mutex, sbc, pcm, kernel panic
On Sunday 09 May 2004 03:40 pm, Don Lewis wrote: > Typically the proper fix in this case would be to remove the > sb_lock() call from sb_reset_dsp() and always let the caller do the > locking. The patch below should do the trick, though I believe the > added locking and unlocking (the second section of the patch) could be > omitted in sb16_attach() since no other thread can access the device > while the attach is in progress. Just a nit: I would add an assertion that the lock is held when sb_reset_dsp() is called as both documentation and to ensure that all callers hold it during testing and future development. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GATEKEEPER.MCAST.NET again (unexpected traffic)
On Mon, 10 May 2004, TSaplin Mikhail wrote: > On Monday 10 May 2004 12:31, you wrote: > > On Sun, 9 May 2004, TSaplin Mikhail wrote: > > > Recently I wrote, that I have litle traffic to GATEKEEPER.MCAST.NET, > > > (tcpdump show this: > > > 20:32:41.496039 129dial.supernet.kz.52075 > GATEKEEPER.MCAST.NET.1718: > > > udp 31 ) > > I know that H.323 protocol is used by ip-phones and releated > software. And i don't understand why it sitting on my clean system > (i've installed it without packages, except ltmdm(modem driver)). It just dawned on me that you are connected to your ISP when you see this, and those packets are probably coming from someone _else_ (you were probably not 129dial.supernet.kz when you saw these). Depending on your ISP's network configuration, you may see multicast and broadcast packets generated by other users. Generally harmless. -- Chris Dillon - cdillon(at)wolves.k12.mo.us FreeBSD: The fastest, most open, and most stable OS on the planet - Available for IA32, IA64, AMD64, PC98, Alpha, and UltraSPARC architectures - PowerPC, ARM, MIPS, and S/390 under development - http://www.freebsd.org Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Reminder! Call for March-April 2004 Status reports
All, It's time again for bi-monthly status reports. As always, the template is at http://www.freebsd.org/news/status/report-sample.xml. Please make submissions to [EMAIL PROTECTED] by May 12 for inclusion. Any projects that relate to FreeBSD development, documentation, ports, etc, are welcome. Previous reports can be found at http://www.freebsd.org/news/status. Again, the due date is May 12. Thanks! Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GATEKEEPER.MCAST.NET again (unexpected traffic)
On Monday 10 May 2004 12:31, you wrote: > On Sun, 9 May 2004, TSaplin Mikhail wrote: > > Recently I wrote, that I have litle traffic to GATEKEEPER.MCAST.NET, > > (tcpdump show this: > > 20:32:41.496039 129dial.supernet.kz.52075 > GATEKEEPER.MCAST.NET.1718: > > udp 31 ) > > > > David Malone <[EMAIL PROTECTED]> on my question wrote: > > >Does sockstat show which process is using port 52075? > > > > No, sockstat show nothing about this. > > > > I've installed new system due express installation - but packets is steel > > going. > > > > Maybe this is going on your 5.1 system, and is this right? > > Those are multicast UDP packets being sent by an H.323 endpoint > application trying to find a local H.323 gatekeeper. Since they are > multicast, they will stay within your LAN unless you have explicitly > configured a router or tunnel to carry them out of it. Totally > harmless, unless you really don't want any H.323-enabled applications > installed and running. Use sockstat to look for anything listening on > the 224.0.1.41 (gatekeeper.mcast.net) address. I know that H.323 protocol is used by ip-phones and releated software. And i don't understand why it sitting on my clean system (i've installed it without packages, except ltmdm(modem driver)). what form of sockstat i should use? Now `sockstat -l` shows: USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS misher kget 649 12 udp4 *:* *:* misher xmms 639 6 stream /var/tmp/xmms_misher.0 misher kdeinit637 12 stream /tmp/.ICE-unix/637 misher kdeinit606 12 stream /tmp/ksocket-misher/klauncherLN4Xwj.slave-socket misher kdeinit602 5 stream /tmp/.ICE-unix/dcop602-1084169543 misher kdeinit599 8 stream /tmp/ksocket-misher/kdeinit-:0 root XFree86580 1 stream /tmp/.X11-unix/X0 mysqlmysqld 565 5 tcp4 *:3306*:* mysqlmysqld 565 6 stream /tmp/mysql.sock root inetd 540 4 tcp4 *:21 *:* root inetd 540 5 tcp4 *:23 *:* root inetd 540 6 udp4 *:518 *:* www httpd 480 3 tcp46 *:80 *:* www httpd 479 3 tcp46 *:80 *:* www httpd 478 3 tcp46 *:80 *:* www httpd 477 3 tcp46 *:80 *:* www httpd 476 3 tcp46 *:80 *:* root httpd 461 3 tcp46 *:80 *:* root sendmail 422 4 tcp4 *:25 *:* root sendmail 422 5 tcp4 *:587 *:* root sshd 417 3 tcp6 *:22 *:* root sshd 417 4 tcp4 *:22 *:* bind named 275 4 udp4 *:49152 *:* bind named 275 5 stream /var/run/ndc bind named 275 20 udp4 127.0.0.1:53 *:* bind named 275 21 tcp4 127.0.0.1:53 *:* bind named 275 22 udp4 192.168.0.1:53*:* bind named 275 23 tcp4 192.168.0.1:53*:* bind named 275 24 udp4 192.168.0.2:53*:* bind named 275 25 tcp4 192.168.0.2:53*:* root syslogd267 3 dgram /var/run/log root syslogd267 4 udp6 *:514 *:* root syslogd267 5 udp4 *:514 *:* `sockstat` without args: USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS misher kmail 1059 5 stream -> /tmp/.ICE-unix/dcop602-1084169543 misher kmail 1059 6 stream -> /tmp/.X11-unix/X0 misher kmail 1059 7 stream -> /tmp/.ICE-unix/637 misher kdeinit1023 5 stream -> /tmp/ksocket-misher/klauncherLN4Xwj.slave-socket misher kdeinit885 5 stream -> /tmp/.ICE-unix/dcop602-1084169543 misher kdeinit885 6 stream -> /tmp/.X11-unix/X0 misher kdeinit885 7 stream -> /tmp/.ICE-unix/637 misher kdeinit651 5 stream -> /tmp/.X11-unix/X0 misher kdeinit651 6 stream -> /tmp/.ICE-unix/637 misher kdeinit651 11 stream -> /tmp/.ICE-unix/dcop602-1084169543 misher kget 649 5 stream -> /tmp/.ICE-unix/dcop602-1084169543 misher kget 649 6 stream -> /tmp/.X11-unix/X0 misher kget 649 7 stream -> /tmp/.ICE-unix/637 misher kget 649 12 udp4 *:* *:* misher xscreensav 645 3 stream -> /tmp/.X11-unix/X0 misher kdeinit644 5 stream -> /tmp/.ICE-unix/dcop602-1084169543 misher kdeinit644 6 stream -> /tmp/.X11-unix/X0 misher kdeinit644 7 stream -> /tmp/.ICE-unix/637 misher kdeinit641 5 stream -> /tmp/.ICE-unix/dcop602-1084169543 misher kdeinit641 6 stream -> /tmp/.X11-unix/X0 misher kdeinit641 7 stream -> /tmp/.ICE-unix/637 misher xmms 639 5 stream -> /tmp/.X11-unix/X0 misher xmms 639 6 stream /var/tmp/xmms_misher.0 misher xmms
