Re: Disk/FS I/O issues in -CURRENT
Thanks. I'll be keeping my eyes wide open for this one. /Eirik On Mon, 30 Jun 2003 15:30:06 -0500 Alan L. Cox [EMAIL PROTECTED] wrote: Peter Holm wrote: On Mon, Jun 30, 2003 at 03:26:13PM +0200, Eirik Oeverby wrote: Hi, Good to see I'm not the only one. I'm currently going back to a kernel dated 2003.06.27.12.00.00, and I'll test again with that one. Ok. I see that alc@ made some recent changes to the vm (vm_pageout.c). I don't know if there's any connection to this problem? I've been able to reproduce what I believe is the problem. (In my case, I reset my machine and watched the background fsck slowly grind to a halt. Foreground fsck is fine.) The problem actually appears to be in vm_page_alloc(), not vm_pageout.c. Look for a commit to resolve this in a few hours. Regards, Alan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Updated ec-burst.diff patch
Please download and try the new version. It correctly implements burst mode to the best of the 2.0 spec. Like the previous message, please report the appropriate dmesgs (acpi_ec0* and EC Waited*) and any errors or regression. I've tested du -a / while plugging/unplugging the power cable on my laptop many times with no errors. I haven't received any feedback yet. This WILL hit the tree in a few weeks because it fixes known problems. Test it now or test it then. :) Thanks, -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated ec-burst.diff patch
Hi, Can you be a bit more specific as to which other problems it fixes? I would love to try, because I have had some pretty nasty ACPI problems in the past, but I only have this one box to test on (my workstation) so I don't feel like going through the compile/install/fail/restore process if there isn't a good reason (for myself) to do so ;) (Just spent a weekend trying to find another kernel regression, I need to get some real work done soon) /Eirik On Tue, 1 Jul 2003 01:07:53 -0700 (PDT) Nate Lawson [EMAIL PROTECTED] wrote: Please download and try the new version. It correctly implements burst mode to the best of the 2.0 spec. Like the previous message, please report the appropriate dmesgs (acpi_ec0* and EC Waited*) and any errors or regression. I've tested du -a / while plugging/unplugging the power cable on my laptop many times with no errors. I haven't received any feedback yet. This WILL hit the tree in a few weeks because it fixes known problems. Test it now or test it then. :) Thanks, -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
should fdisk -BI still work?
Hi, Should fdisk -BI ad0 still work on current? I have a script that I use to prepare flash disks that have worked for a long time on older versions of FreeBSD, but it seems a little broken on -current. It actually started with the one from Warner's site people.../~imp/diskprep.pl and tweaked it over time to keep it running. On current I get an error when doing fdisk -BI ad0: fdisk: invalid fdisk partition table found So how is one supposed to create a FreeBSD slice nowadays from a script? John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[-CURRENT tinderbox] failure on ia64/ia64
TB --- 2003-07-01 08:28:05 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2003-07-01 08:28:05 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-01 08:33:16 - building world TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64/src TB --- /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. [...] @DØa0hª 8-ÀÄÀ_: not found : not found : not found : not found 0bÀ x À: not found À: not found À: not found ./mkinit: 16: Syntax error: ( unexpected (expecting )) *** Error code 2 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/bin/sh. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/rescue/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/rescue/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. TB --- 2003-07-01 09:16:40 - /usr/bin/make returned exit code 1 TB --- 2003-07-01 09:16:40 - ERROR: failed to build world TB --- 2003-07-01 09:16:40 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[-CURRENT tinderbox] failure on sparc64/sparc64
TB --- 2003-07-01 09:16:40 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-07-01 09:16:40 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-01 09:18:45 - building world TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. [...] yacc -d /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/arith.y cp y.tab.c arith.c lex -t -8 /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/arith_lex.l arith_lex.c cd /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh; sh mkbuiltins /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/rescue/rescue/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh cc -O -pipe -DSHELL -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh -DRESCUE -c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/mkinit.c cc -O -pipe -DSHELL -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh -DRESCUE -static mkinit.o -o mkinit ./mkinit /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/alias.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/eval.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/exec.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/input.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/jobs.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/options.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/parser.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/redir.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/trap.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/var.c ./mkinit: 1: Syntax error: end of file unexpected *** Error code 2 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/rescue/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/rescue/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src. TB --- 2003-07-01 09:56:23 - /usr/bin/make returned exit code 1 TB --- 2003-07-01 09:56:23 - ERROR: failed to build world TB --- 2003-07-01 09:56:23 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
netstat
Hi,
Is there any reason that the interface name in netstat is truncated at 5
chars? I have a box with ~100 vlans so the interface name gets chopped
after vlan9.
Here is a patch to increase it to 7 chars. Any probs?
thanks,
Andy
--- usr.bin/netstat/if.c.orig Tue Jul 1 22:37:14 2003
+++ usr.bin/netstat/if.cTue Jul 1 22:38:59 2003
@@ -188,7 +188,7 @@
return;
if (!pfunc) {
- printf(%-5.5s %5.5s %-13.13s %-17.17s %8.8s %5.5s,
+ printf(%-7.7s %5.5s %-13.13s %-17.17s %8.8s %5.5s,
Name, Mtu, Network, Address, Ipkts,
Ierrs);
if (bflag)
printf( %10.10s,Ibytes);
@@ -254,7 +254,7 @@
drops = ifnet.if_snd.ifq_drops;
if (ifaddraddr == 0) {
- printf(%-5.5s %5lu , name, ifnet.if_mtu);
+ printf(%-7.7s %5lu , name, ifnet.if_mtu);
printf(%-13.13s , none);
printf(%-17.17s , none);
} else {
@@ -271,7 +271,7 @@
(u_long)TAILQ_NEXT(ifaddr.ifa,
ifa_link);
continue;
}
- printf(%-5.5s %5lu , name, ifnet.if_mtu);
+ printf(%-7.7s %5lu , name, ifnet.if_mtu);
switch (sa-sa_family) {
case AF_UNSPEC:
printf(%-13.13s , none);
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: netstat
On Tue, 1 Jul 2003, 22:45+1200, Andrew Thompson wrote: Hi, Is there any reason that the interface name in netstat is truncated at 5 chars? I have a box with ~100 vlans so the interface name gets chopped after vlan9. Here is a patch to increase it to 7 chars. Any probs? bin/52349 -- Maxim Konovalov, [EMAIL PROTECTED], [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/src/libexec/talkd notification broken on pty's when useris using misc/screen ports in -CURRENT
On Mon, 30 Jun 2003, Juli Mallett wrote: * Vincent Poy [EMAIL PROTECTED] [ Date: 2003-06-30 ] [ w.r.t. /usr/src/libexec/talkd notification broken on pty's when user is using misc/screen ports in -CURRENT ] Greetings evertone: /usr/src/libexec/talkd aka /usr/libexec/ntalkd appears to be broken when one runs the screen-3.9.15_1 from ports and has the pty sessions under screen. Prior to running screen, ntalkd is showing the incoming talk request. After running screen, the talk request doesn't show up on any of the pty's the user is currently using under the primary login pty. The issue seems to be caused by the following commits done by jmallett: src/libexec/talkd/announce.c v1.16, Thu Apr 3 05:13:27 2003 UTC jmallett src/libexec/talkd/extern.h v1.3, Thu Apr 3 05:13:27 2003 UTC jmallett src/libexec/talkd/print.c v1.12, Thu Apr 3 05:13:27 2003 UTC jmallett src/libexec/talkd/table.c v1.9, Thu Apr 3 05:13:27 2003 UTC jmallett src/libexec/talkd/talkd.c v1.14, Thu Apr 3 05:13:27 2003 UTC jmallett which has the log: MFp4 @27667: WARNS=5 cleanup on i386. Remove the unused FILE\ *tf from print_mesg args, and the bogus passing in of an uninitialised FILE* for it. Call a timeval 'now' instead of 'clock' due to shadowing. Remove a nested localtime declaration. Make the delete invite argument match the ID type, u_int32_t. Use const for pointers to const items. Cast to long where printing as such. Include netinet/in.h for htonl/htons. Reviewed by:imp Reverting to the following previous versions of the files and rebuilding ntalkd fixes the issue. src/libexec/talkd/announce.c v1.15, Tue Feb 5 21:06:56 2002 UTC imp src/libexec/talkd/extern.h v1.2, Tue Feb 5 21:07:47 2002 UTC imp src/libexec/talkd/print.c v1.11, Mon Feb 18 20:35:19 2002 UTC mike src/libexec/talkd/table.c v1.8, Tue Feb 5 21:06:56 2002 UTC imp src/libexec/talkd/talkd.c v1.13, Tue Feb 5 21:06:56 2002 UTC imp This may be a bit frustrating, but can you back out deltas by hand and try to tell me which change it was that caused the problem? Hi Juli and Cy: It isn't the changes that caused the problem because here is what I did just to verify the behavior of before and after the changes you did. before, in screen-3.9.15 with both the port and if I compile it on my own with the configure script and then make, the ntalkd daemon doesn't do the notification in any of the pty's while running under screen except when I am in a ytalk session where the prompt will come up if I want to talk to [EMAIL PROTECTED] with screen-3.9.13, screen-3.9.11 which I compiled on my own with the configure script and then make, the ntalkd daemon doesn't do the notification in any of the pty's while running under screen except when I am in a ytalk session where the prompt will come up if I want to talk to [EMAIL PROTECTED] with the screen-3.9.10 binary I compiled from ports before, ntalkd works correctly: Message from [EMAIL PROTECTED] at 5:09 on 2003/07/01 ... talk: connection requested by [EMAIL PROTECTED] talk: respond with: talk [EMAIL PROTECTED] With the changes you did, the screen-3.9.15 port as well as screen-3.9.15, screen-3.9.13, screen-3.9.11 which I compiled on my own with the configure script and then make, the ntalkd daemon doesn't do the notification in any of the pty's while running under screen and the prompt doesn't come up in a ytalk session either if I want to talk to [EMAIL PROTECTED] with the screen-3.9.10 binary I compiled from ports before, ntalkd works correctly: Message from [EMAIL PROTECTED] at 5:49 on 2003/07/01 ... talk: connection requested by [EMAIL PROTECTED] talk: respond with: talk [EMAIL PROTECTED] So it seems that it is not the changes you did but everything after newer than screen-3.9.10, the talkd daemon isn't working when the pty's are under screen. So it's probably more of a bug under screen than anything else. I couldn't find the contact info for the author for screen to find out how to fix this. Cheers, Vince - [EMAIL PROTECTED] - Vice President __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] [EMAIL PROTECTED] - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
fsck background mode for gbde crypted disc?
Hi I wonder if I can do a background check after mounting an crypted part or does the check have to be b4 ? best regards, Christophe -- Christophe Zwecker mail: [EMAIL PROTECTED] Hamburg, Germanyfon: +49 179 3994867 http://www.zwecker.de Who is General Failure ? And why is he reading my disk ?? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best way to get max KVA setting?
Terry Lambert ([EMAIL PROTECTED]) wrote: It was for a guy who was was running with PAE enabled on an 8G machine, and the autotuning was shooting him in the foot when it tried to grab enough memory to create kmem_map entries for the 8G of RAM in his 2G KVA space, and its head exploded. Wrong, the big problem he had with the auto tuning code was that vm_kmem_size was overflowing and he was left with a 20MB kmem_map size instead of 200. Once alc fixed the the scaling for # of vnodes, or if we set maxvnodes to a sane value, we no longer saw panics due to kmem_map being too small. --- revision 1.126 date: 2003/06/11 05:18:59; author: ps; state: Exp; lines: +4 -4 Don't overflow when calculating vm_kmem_size. This fixes kmem_map too small panics on PAE machines which have odd 4GB sizes (4.5 gig would render a 20MB of KVA for kmem_map instead of 200MB). Submitted by: John Cagle [EMAIL PROTECTED], jeff Reviewed by:jeff, peter, scottl, lots of USENIX folks --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: Atheros 802.11 support
In message: [EMAIL PROTECTED] Gregory P. Smith [EMAIL PROTECTED] writes: : On Fri, Jun 27, 2003 at 11:40:13PM -0700, Sam Leffler wrote: : My work to support the Atheros 802.11 hardware is now entirely in the tree : and enabled for use. The ath driver supports all Atheros hardware devices : and makes FreeBSD the first open source system to support 802.11a and : 802.11g*. There are still issues with the driver. man ath(4) for details. : : Sam : : *First by a few days--there is also a Linux version of this software : available at http://sourceforge.net/projects/madwifi/. : : maybe not, another linux driver already existed: http://team.vantronix.net/ar5k/ OK, sam had the first WORKING driver. I tried this driver and apart from light a few LEDs, it most definitely didn't work for any useful definition of work. hey, I have this web page, can I count as first doesn't count as first. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ftream errors under g++ 3.2.2
In message: [EMAIL PROTECTED] Jeffrey Hsu [EMAIL PROTECTED] writes: :file IO using fstream gives error messages about implicit typenames :being deprecated, and I can't for the life of me figure out what to do :my code to make the compiler happy : : Change your /usr/include/g++/fstream as follows: I've sent these changes to the gnu folks, but it looks like they haven't made it back to FreeBSD yet. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.2-RELEASE TODO
This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list. The live version of this list is available at: http://www.FreeBSD.org/releases/5.2R/todo.html Automated mailing of this list will continue through the release of FreeBSD 5.2. FreeBSD 5.2 Open Issues Open Issues This is a list of open issues that need to be resolved for FreeBSD 5.2. If you have any updates for this list, please e-mail [EMAIL PROTECTED] Must Resolve Issues for 5.2-RELEASE ++ |Issue| Status | Responsible | Description | |-+--+-+-| | | | | KSE M:N threading | | | | | support is reaching | | | | | experimental yet| | | | Julian | usable status on| | Production-quality | In | Elischer, David | i386 for| | M:N threading | progress | Xu, Daniel | 5.1-RELEASE. M:N| | | | Eischen | threading should be | | | | | productionable and | | | | | usable on all | | | | | platforms by| | | | | 5.2-RELEASE.| |-+--+-+-| | | | | Currently, the MD | | | | | elements of KSE are | | | | | present only for| | | | | the i386 platform, | | | | | limiting use of KSE | | | | | to the i386 | | | | | platform. It is | | | | | highly desirable to | | KSE support for | | Jake| make KSE available | | sparc64, alpha, | -- | Burkholder, --, | on non-i386 | | ia64| | -- | platforms for | | | | | 5.2-RELEASE so that | | | | | KSE can see more| | | | | broad exposure, and | | | | | the performance | | | | | benefits of KSE can | | | | | be visible to users | | | | | of the 64-bit | | | | | FreeBSD | | | | | architectures. | |-+--+-+-| | | | | Kris Kennaway | | | | | reports high| | | | | instability of | | | | | 5-CURRENT on ia64 | | | In | Marcel | machines, such as | | ia64 stability | Progress | Moolenaar | the pluto* | | | | | machines. These | | | | | problems need to be | | | | | fixed in order to | | | | | get a successful| | | | | package build. | |-+--+-+-| | | | | ia64 serial console | | | | | support is reported | | | | | to not be | | | | | functional on HP| | | In | Marcel | Itanium2 platforms. | | ia64 sio support| progress | Moolenaar, | A reworking of the | | | | Warner Losh | sio driver to | | | | | improve platform| | | | | independence and| | | | | bus handling is | | | |
Re: should fdisk -BI still work?
On Tue, Jul 01, 2003 at 11:15:49AM +0200, John Hay wrote: Hi, Should fdisk -BI ad0 still work on current? I have a script that I use to prepare flash disks that have worked for a long time on older versions of FreeBSD, but it seems a little broken on -current. It actually started with the one from Warner's site people.../~imp/diskprep.pl and tweaked it over time to keep it running. On current I get an error when doing fdisk -BI ad0: fdisk: invalid fdisk partition table found So how is one supposed to create a FreeBSD slice nowadays from a script? I'm not using -BI, but I am using -I in a version of diskprep. Are you sure you don't have any slices (or partitions inside those slices) open? I remember getting all sorts of weird errors when I forgot about that while developing my new scripts. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgp0.pgp Description: PGP signature
Re: /usr/src/libexec/talkd notification broken on pty's when useris using misc/screen ports in -CURRENT
On Tue, 1 Jul 2003, Vincent Poy wrote: On Mon, 30 Jun 2003, Juli Mallett wrote: * Vincent Poy [EMAIL PROTECTED] [ Date: 2003-06-30 ] [ w.r.t. /usr/src/libexec/talkd notification broken on pty's when user is using misc/screen ports in -CURRENT ] Greetings evertone: /usr/src/libexec/talkd aka /usr/libexec/ntalkd appears to be broken when one runs the screen-3.9.15_1 from ports and has the pty sessions under screen. Prior to running screen, ntalkd is showing the incoming talk request. After running screen, the talk request doesn't show up on any of the pty's the user is currently using under the primary login pty. The issue seems to be caused by the following commits done by jmallett: src/libexec/talkd/announce.c v1.16, Thu Apr 3 05:13:27 2003 UTC jmallett src/libexec/talkd/extern.h v1.3, Thu Apr 3 05:13:27 2003 UTC jmallett src/libexec/talkd/print.c v1.12, Thu Apr 3 05:13:27 2003 UTC jmallett src/libexec/talkd/table.c v1.9, Thu Apr 3 05:13:27 2003 UTC jmallett src/libexec/talkd/talkd.c v1.14, Thu Apr 3 05:13:27 2003 UTC jmallett which has the log: MFp4 @27667: WARNS=5 cleanup on i386. Remove the unused FILE\ *tf from print_mesg args, and the bogus passing in of an uninitialised FILE* for it. Call a timeval 'now' instead of 'clock' due to shadowing. Remove a nested localtime declaration. Make the delete invite argument match the ID type, u_int32_t. Use const for pointers to const items. Cast to long where printing as such. Include netinet/in.h for htonl/htons. Reviewed by: imp Reverting to the following previous versions of the files and rebuilding ntalkd fixes the issue. src/libexec/talkd/announce.c v1.15, Tue Feb 5 21:06:56 2002 UTC imp src/libexec/talkd/extern.h v1.2, Tue Feb 5 21:07:47 2002 UTC imp src/libexec/talkd/print.c v1.11, Mon Feb 18 20:35:19 2002 UTC mike src/libexec/talkd/table.c v1.8, Tue Feb 5 21:06:56 2002 UTC imp src/libexec/talkd/talkd.c v1.13, Tue Feb 5 21:06:56 2002 UTC imp This may be a bit frustrating, but can you back out deltas by hand and try to tell me which change it was that caused the problem? Hi Juli and Cy: It isn't the changes that caused the problem because here is what I did just to verify the behavior of before and after the changes you did. before, in screen-3.9.15 with both the port and if I compile it on my own with the configure script and then make, the ntalkd daemon doesn't do the notification in any of the pty's while running under screen except when I am in a ytalk session where the prompt will come up if I want to talk to [EMAIL PROTECTED] with screen-3.9.13, screen-3.9.11 which I compiled on my own with the configure script and then make, the ntalkd daemon doesn't do the notification in any of the pty's while running under screen except when I am in a ytalk session where the prompt will come up if I want to talk to [EMAIL PROTECTED] with the screen-3.9.10 binary I compiled from ports before, ntalkd works correctly: Message from [EMAIL PROTECTED] at 5:09 on 2003/07/01 ... talk: connection requested by [EMAIL PROTECTED] talk: respond with: talk [EMAIL PROTECTED] With the changes you did, the screen-3.9.15 port as well as screen-3.9.15, screen-3.9.13, screen-3.9.11 which I compiled on my own with the configure script and then make, the ntalkd daemon doesn't do the notification in any of the pty's while running under screen and the prompt doesn't come up in a ytalk session either if I want to talk to [EMAIL PROTECTED] with the screen-3.9.10 binary I compiled from ports before, ntalkd works correctly: Message from [EMAIL PROTECTED] at 5:49 on 2003/07/01 ... talk: connection requested by [EMAIL PROTECTED] talk: respond with: talk [EMAIL PROTECTED] So it seems that it is not the changes you did but everything after newer than screen-3.9.10, the talkd daemon isn't working when the pty's are under screen. So it's probably more of a bug under screen than anything else. I couldn't find the contact info for the author for screen to find out how to fix this. Okay, I found the problem... It is not related to ntalkd or screen. The issue is that -CURRENT uses devfs which I assume generates all the devices in /dev. The ssh tty /dev/ttyp0 does get the correct user vince group tty for the ownership. However, the screen tty's which are ttyp1-ttypa has user vince and the group is users. Doing chown :tty /dev/ttyp1 fixes the problem so the problem lies in the group for the tty being used being the group of the user and not tty. Cheers, Vince - [EMAIL PROTECTED] - Vice President __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / /
Re: Problems running Quake 3 on -CURRENT / X 4.3.0
It looks like this problem is still around. Short problem description: all inputs are lagging behind when running Quake 3 Arena with Radeon video adapters (hardware accelerated), and the graphics look like they are generated in bursts, while framerate is just fine. I just noticed that I get the same problem with quake2lnx (games/quake2lnx) when I start it with 'sdlquake2' or 'quake2 +set vid_ref glx' and play at a resolution of 1024x768 or higher. I can play it without many problems at 800x600. Same as before, the movements themselves look smooth, but they are lagging, and occasionally there is a glitch where it seems like the system is trying to keep up with what is actually happening. My system is a Athlon XP 2000+ with a ATi Radeon R100. I doubt that it is too slow to run Quake 2. As this one is not Linux-emulated, I guess it's not in the Linux emulation - more likely in X. Does anyone know what causes this, or maybe it is already fixed in the XFree86 CVS? Also, can anyone running -STABLE see if this problem only affects -CURRENT or not? Best regards, Arjan This is the last I've seen on this issue on the lists: On Thursday 24 April 2003 22:49, Eric Anholt wrote: On Thu, 2003-04-24 at 11:21, John Baldwin wrote: On 23-Apr-2003 Arjan van Leeuwen wrote: Hi, Quake 3 is behaving strange when running it from -CURRENT with XFree86 4.3.0 on my Radeon (R100). Other people are experiencing the same problems with a Radeon 7500. Does reverting revision 1.42 of sys/compat/linux/linux_signal.c fix things? I've been seeing this problem for weeks, so no. I saw it a few times while using 4.2.0 (never figured out what caused it), but now with 4.3.0 it's all the time. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[-CURRENT tinderbox] failure on alpha/alpha
TB --- 2003-07-01 16:00:01 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-07-01 16:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-01 16:03:35 - building world TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. [...] yacc -d /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh/arith.y cp y.tab.c arith.c lex -t -8 /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh/arith_lex.l arith_lex.c cd /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh; sh mkbuiltins /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/rescue/rescue/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh cc -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -DSHELL -I. -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh -DRESCUE -c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh/mkinit.c cc -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -DSHELL -I. -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh -DRESCUE -static mkinit.o -o mkinit ./mkinit /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh/alias.c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh/eval.c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh/exec.c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh/input.c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh/jobs.c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh/options.c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh/parser.c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh/redir.c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh/trap.c /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh/var.c ./mkinit: 1: Syntax error: ( unexpected *** Error code 2 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/bin/sh. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/rescue/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/rescue/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src. TB --- 2003-07-01 16:52:18 - /usr/bin/make returned exit code 1 TB --- 2003-07-01 16:52:18 - ERROR: failed to build world TB --- 2003-07-01 16:52:18 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated ec-burst.diff patch
On Tue, 1 Jul 2003, Florian Smeets wrote: with this patch i get a lot of these errors: ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed [\\_SB_.BAT0._STA] (Node 0xc2502760), AE_ERROR ACPI-0175: *** Error: Method execution failed [\\_SB_.BAT0._STA] (Node 0xc2502760), AE_ERROR ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed [\\_SB_.BAT0._BST] (Node 0xc2502720), AE_ERROR ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed [\\_TZ_.TZN0._TMP] (Node 0xc2502b80), AE_ERROR And also the kernel is seting the power profile from economy to performance and back to economy and so on. Also when i unplugg the power cable it's not recognized anymore. Before this patch ACPI was working flawlessly on my laptop. Would you please turn on hw.acpi.verbose=1 in loader.conf? It should explain the cause of those errors. Also, I would like the output of dmesg | egrep acpi_ec0\|EC\ Wait. Thanks, Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated ec-burst.diff patch
On Tue, 1 Jul 2003, Eirik Oeverby wrote: Can you be a bit more specific as to which other problems it fixes? I would love to try, because I have had some pretty nasty ACPI problems in the past, but I only have this one box to test on (my workstation) so I don't feel like going through the compile/install/fail/restore process if there isn't a good reason (for myself) to do so ;) (Just spent a weekend trying to find another kernel regression, I need to get some real work done soon) There are a ton of problems with the current version, the largest that its default behavior expects IBF/OBF events to be reported correctly by the GPE but in fact implementations vary widely in their support. This can be worked around by setting hw.acpi.event_driven=1 but I want to make it work by default. The event_driven sysctl is not a full solution because it uses DELAY heavily. To reduce the load in DELAY, I implemented burst mode support. However, since no open source EC code uses burst mode, it is unknown how good its hw support is. So my code has lots of tests of your EC and I need the dmesg output from it to know how to proceed from here. That's why I need wide testing. The patch is not a complete implementation but it should help identify any hw problems in burst mode support. I won't put it into the tree without making sure it can fall back correctly. Also, since I forgot the URL the second time: http://root.org/~nate/freebsd/ec-burst.diff -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated ec-burst.diff patch
On Tue, 1 Jul 2003, Florian Smeets wrote: with this patch i get a lot of these errors: ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed [\\_SB_.BAT0._STA] (Node 0xc2502760), AE_ERROR ACPI-0175: *** Error: Method execution failed [\\_SB_.BAT0._STA] (Node 0xc2502760), AE_ERROR ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed [\\_SB_.BAT0._BST] (Node 0xc2502720), AE_ERROR ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed [\\_TZ_.TZN0._TMP] (Node 0xc2502b80), AE_ERROR Also, please report how adding hw.acpi.ec.burst_mode=0 to loader.conf changes things (but turn on hw.acpi.verbose first so we get good msgs). -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[-CURRENT tinderbox] failure on amd64/amd64
TB --- 2003-07-01 16:52:19 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2003-07-01 16:52:19 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-01 16:54:09 - building world TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64/src TB --- /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. [...] ./mkinit /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/bin/sh/alias.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/bin/sh/eval.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/bin/sh/exec.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/bin/sh/input.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/bin/sh/jobs.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/bin/sh/options.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/bin/sh/parser.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/bin/sh/redir.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/bin/sh/trap.c /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/bin/sh/var.c ELF: not found ./mkinit: [EMAIL PROTECTED]@FreeBSDm¥èãèêáÃATUS LgHcÃHlÇH-ãq Û~3Ht,HGH½HÂ8t:/u HBH¤HÿÂ:uè¸H ÀtH÷è: not found ./mkinit: TUS LgHcÃHlÇH-ãq Û~3Ht,HGH½HÂ8t:/u HBH¤HÿÂ:uè¸H ÀtH÷è: not found H ÀtH÷è: not found [EMAIL PROTECTED]: not found è: not found ./mkinit: 8: Syntax error: word unexpected (expecting )) *** Error code 2 Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/bin/sh. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/obj/amd64/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/rescue/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/rescue/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src. TB --- 2003-07-01 17:39:40 - /usr/bin/make returned exit code 1 TB --- 2003-07-01 17:39:40 - ERROR: failed to build world TB --- 2003-07-01 17:39:40 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck background mode for gbde crypted disc?
In message [EMAIL PROTECTED], Christophe Zwecker writes: Hi I wonder if I can do a background check after mounting an crypted part or does the check have to be b4 ? That should just work, a filesystem on GBDE is no different than any other filesystem. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1-RELEASE Windows XP dual-boot issues
On Tue, 2003-07-01 at 01:34, Jud wrote: to boot FreeBSD with no problems at all, but when I went to boot up Windows, I received the dreaded 'NTLDR missing' message. [grub stuff snipped] A few comments about the thread so far: ISTM the easiest thing for you to do is install booteasy on *both* drives. That should work fine. I don't think that will make any difference in my case. Just a recap: I have two physical drives (ad0, ad1). XP is on ad0 (the first drive) and FreeBSD is on ad1 (the second drive). I have been using booteasy on the *first* drive with a regular mbr on the second and that worked just fine until I did a fresh install of 5.1. What I'm trying to get at is how best to re-install windows (or work around the 'NTLDR is missing' message) *without* then rendering my FreeBSD install unbootable because we all know that Windows overwrites the mbr by default because it thinks it's supreme ruler of the universe. I think Jesse Guardini's suggestion works when Win and FreeBSD are on the same drive. You can still use the NT/2K/XP bootloader when the OSs are on different drives, but problem is, I could never figure out exactly what the FAQ was trying to tell me on that score. You might take a look at the FAQ and see if it's clear to you. The FAQ's do seem to assume that the OS's are on the same physical drive which doesn't actually help me much. Grub is a fine bootloader, but I've heard it doesn't like UFS2 filesystems, and I've also heard 5.1 uses UFS2 for / as default, causing grub not to work. Is your / UFS1 or UFS2? (Or to ask another way, did you upgrade via cvsup (resulting in UFS1 root) or install 5.1 from scratch (resulting in UFS2 root)? If you can use grub and decide you'd like to do so, the rootnoverify line is no longer necessary with Win2K. 5.1 does indeed use UFS2 by default and, hence, my filesystem is UFS2. I did a fresh install of 5.1, not a source upgrade. Again, what I'm really looking for are suggestions as to how to go about reinstalling Windows (which will wipe out booteasy on the first drive, thus making the second drive - FreeBSD - unbootable) and then installing a boot manager that will pick up the FreeBSD install on the second drive and allow me to boot it or Windows. You may want to have a look at GAG, which is freeware, open source, graphical, and rather automagic. Worked out of the box on my setup, which involves dual booting Win2K and FreeBSD from a RAID0 array. Thanks, I will take a look at it. -Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Virus Detected by Network Associates, Inc. Webshield SMTP V4.5 MR1a
Southern Illinois University-Edwardsville Office of Information Technology detected the W32/[EMAIL PROTECTED] virus in the your_details.zip attachment sent to [EMAIL PROTECTED] and it was Deleted. If you are affiliated with SIUE, please call the Customer Support Center at 650-3739 for immediate assistance with your infected computer. If you are not affiliated with SIUE, please contact your local personal computer support organization. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ULE problems on HTT SMP
On 28-Jun-2003 Jeff Roberson wrote: On Fri, 27 Jun 2003, John Baldwin wrote: On 27-Jun-2003 Andrew Gallatin wrote: Jeff Roberson writes: Can you call kseq_print(0) and kseq_print(1) from ddb? I found a different problem which is nearly as interesting. Note that ps thinks sysctl is on cpu 255... #define NOCPU 0xff/* For when we aren't on a CPU. (SMP) */ So that isn't but so interesting. :) The problem is that the logical cpu halting code does not put the halted CPU in the stopped cpus set. ULE has no way of knowing that it can not migrate a thread to this cpu. I'd prefer it if you could make this change John, but I can certainly do it if you're busy. Probably we should add a flags field to struct pcpu and add a flag meaning that a CPU is disabled and magic code to choosethread() or some other appropriate place that doesn't schedule real threads on a disabled CPU. The logical CPU halting code could then be changed to set this flag on the appropriate CPUs. Thanks, Jeff db ps pid proc addruid ppid pgrp flag stat wmesgwchan cmd 62 c41ec000 d8d9a00006042 0004002 [CPU 255] sysctl 60 c4175d3c d7bcc00005842 002 [SLP]wait 0xc4175d3c] sh 58 c4175790 d7ba200005142 002 [SLP]wait 0xc4175790] sh 51 c4175b58 d7bcb00004242 002 [SLP]wait 0xc4175b58] sh 42 c4025b58 d7b660000 142 0004002 [SLP]wait 0xc4025b58] sh 41 c4025d3c d7b670000 0 0 204 [SLP]nfsidl 0xc03f9b8c] nfsiod 3 40 c4173000 d7b960000 0 0 204 [SLP]nfsidl 0xc03f9b88] nfsiod 2 39 c41731e4 d7b970000 0 0 204 [SLP]nfsidl 0xc03f9b84] nfsiod 1 38 c41733c8 d7b980000 0 0 204 [SLP]nfsidl 0xc03f9b80] nfsiod 0 37 c41735ac d7b990000 0 0 204 [SLP]vlruwt 0xc41735ac] vnlru 36 c4173790 d7b9a0000 0 0 204 [SLP]syncer 0xc03cacc0] syncer 35 c4173974 d7b9b0000 0 0 204 [SLP]psleep 0xc03f7e3c] bufdaemon 34 c4173b58 d7b9c0000 0 0 20c [SLP]pgzero 0xc03ffc08] pagezero 9 c4173d3c d7b9d0000 0 0 204 [SLP]psleep 0xc03ffc34] vmdaemon 8 c4175000 d7b9e0000 0 0 204 [SLP]psleep 0xc03ffc20] pagedaemon 33 c41751e4 d7b9f0000 0 0 204 new [IWAIT] irq8: rtc 32 c3f795ac d7b2b0000 0 0 204 new [IWAIT] irq0: clk 31 c3f79790 d7b2c0000 0 0 204 [IWAIT] irq6: fdc0 30 c3f79974 d7b2d0000 0 0 204 new [IWAIT] irq7: ppc0 29 c3f79b58 d7b2e0000 0 0 204 new [IWAIT] irq3: sio1 28 c3f79d3c d7b2f0000 0 0 204 new [IWAIT] irq4: sio0 27 c4025000 d7b390000 0 0 204 [IWAIT] swi0: tty:sio 26 c40251e4 d7b3a0000 0 0 204 new [IWAIT] irq11: em0 25 c40253c8 d7b3b0000 0 0 204 [IWAIT] irq15: ata1 24 c40255ac d7b3c0000 0 0 204 [IWAIT] irq14: ata0 23 c4025790 d7b3d0000 0 0 204 new [IWAIT] irq5: fxp0 7 c4025974 d7b3e0000 0 0 204 [SLP]actask 0xc04e40cc] acpi_task2 6 c150a1e4 d69290000 0 0 204 [SLP]actask 0xc04e40cc] acpi_task1 5 c150a3c8 d692a0000 0 0 204 [SLP]actask 0xc04e40cc] acpi_task0 22 c150a5ac d692b0000 0 0 204 new [IWAIT] irq9: acpi0 21 c150a790 d692c0000 0 0 204 [IWAIT] swi3: cambio 20 c150a974 d692d0000 0 0 204 new [IWAIT] swi2: camnet 19 c150ab58 d692e0000 0 0 204 new [IWAIT] swi5:+ 18 c150ad3c d69560000 0 0 204 new [IWAIT] swi6: task queue 17 c3f79000 d7b280000 0 0 204 [IWAIT] swi6: acpitaskq 16 c3f791e4 d7b290000 0 0 204 [SLP]sleep 0xc03b5dc0] random 4 c3f793c8 d7b2a0000 0 0 204 [SLP]- 0xc03c41fc] g_down 3 c1503000 d68d20000 0 0 204 [SLP]- 0xc03c41f8] g_up 2 c15031e4 d69210000 0 0 204 [SLP]- 0xc03c41f0] g_event 15 c15033c8 d69220000 0 0 204 new [IWAIT] swi4: vm 14 c15035ac d69230000 0 0 20c [IWAIT] swi7: tty:sio clock 13 c1503790 d69240000 0 0 204 new [IWAIT] swi1: net 12 c1503974 d69250000 0 0 20c [CPU 0] idle: cpu0 11 c1503b58 d69260000 0 0 20c [CPU 1] idle: cpu1 1 c1503d3c d69270000 0 1 0004200 [SLP]wait 0xc1503d3c] init 10 c150a000 d69280000 0 0 204 [CV]ktrace 0xc03c7794] ktrace 0 c03c42c0 c05130000 0 0 200 [SLP]sched 0xc03c42c0] swapper db sho pcpu cpuid= 0 curthread= 0xc1504980: pid 12 idle: cpu0 curpcb = 0xd68edda0 fpcurthread = none idlethread = 0xc1504980: pid 12 idle: cpu0 currentldt = 0x28 spin locks held: db sho
Re: ULE problems on HTT SMP
On Mon, 30 Jun 2003, Andrew Gallatin wrote: Jeff Roberson writes: On Fri, 27 Jun 2003, John Baldwin wrote: On 27-Jun-2003 Andrew Gallatin wrote: Jeff Roberson writes: Can you call kseq_print(0) and kseq_print(1) from ddb? I found a different problem which is nearly as interesting. Note that ps thinks sysctl is on cpu 255... #define NOCPU 0xff/* For when we aren't on a CPU. (SMP) */ So that isn't but so interesting. :) The problem is that the logical cpu halting code does not put the halted CPU in the stopped cpus set. ULE has no way of knowing that it can not migrate a thread to this cpu. I'd prefer it if you could make this change John, but I can certainly do it if you're busy. Does this mean that if, as a temporary measure, I disable machdep.cpu_idle_hlt, ULE should work for me? Yes, but it needs to be disabled before booting so you'll have to adjust it in the code. See i386/i386/mp_machdep.c Cheers, Jeff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: Atheros 802.11 support
On Tue, Jul 01, 2003 at 07:56:50AM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Gregory P. Smith [EMAIL PROTECTED] writes: : On Fri, Jun 27, 2003 at 11:40:13PM -0700, Sam Leffler wrote: : My work to support the Atheros 802.11 hardware is now entirely in the tree : and enabled for use. The ath driver supports all Atheros hardware devices : and makes FreeBSD the first open source system to support 802.11a and : 802.11g*. There are still issues with the driver. man ath(4) for details. : :Sam : : *First by a few days--there is also a Linux version of this software : available at http://sourceforge.net/projects/madwifi/. : : maybe not, another linux driver already existed: http://team.vantronix.net/ar5k/ OK, sam had the first WORKING driver. I tried this driver and apart from light a few LEDs, it most definitely didn't work for any useful definition of work. hey, I have this web page, can I count as first doesn't count as first. Hehe. I haven't tried either as i don't have 802.11a hardware. I was mostly posting the link to let people know another driver exists as a potential reference. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rescue/ broke cross compiles
On Mon, Jun 30, 2003 at 05:35:16PM -0700, Marcel Moolenaar wrote: Build tools are most of the time so small or trivial (gcc is probably the exception, before that perl probably was) that building them again is lost in creating the rescue bits itself. Please no, don't pessimize the build even more than it absolutely has to be. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/src/libexec/talkd notification broken on pty's when user is using misc/screen ports in -CURRENT
Mine configures as follows: /* * define PTYMODE if you do not like the default of 0622, which allows * public write to your pty. * define PTYGROUP to some numerical group-id if you do not want the * tty to be in your group. * Note, screen is unable to change mode or group of the pty if it * is not installed with sufficient privilege. (e.g. set-uid-root) * define PTYROFS if the /dev/pty devices are mounted on a read-only * filesystem so screen should not even attempt to set mode or group * even if running as root (e.g. on TiVo). */ #define PTYMODE 0620 #define PTYGROUP 4 /* #undef PTYROFS */ What does your /etc/group look like? Could send me a copy of /etc/devfs.conf. I'd like to see an ls -l of /dev too. I'm preparing to host a Canada Day barbecue at my house, so I may not have a chance to check for email later on today. Please bear with me. Thanks. I'm cc'ing this to current@ just in the chance that someone there might solve this before I do. Cheers, -- Cy Schubert [EMAIL PROTECTED]http://www.komquats.com/ BC Government . FreeBSD UNIX [EMAIL PROTECTED] . [EMAIL PROTECTED] http://www.gov.bc.ca/ .http://www.FreeBSD.org/ In message [EMAIL PROTECTED], Vincent Poy writes : On Tue, 1 Jul 2003, Cy Schubert wrote: In message [EMAIL PROTECTED], Vincent Poy writes : [a bunch of lines edited out for brevity, see archives] Hi Cy: I found the problem. In 5.1-CURRENT and I think 5.1-RELEASE, /dev uses the devfs for the devices so it no longer has to be manually generated. I login to the system using /dev/ttyp0 which shows up as: crw--w 1 vince tty- 5, 0 Jul 1 08:28 /dev/ttyp0 However, the 10 tty's that screen uses is ttyp1-pa which has the group as users or the same as my login: crw--w 1 vince users- 5, 1 Jul 1 08:28 /dev/ttyp1 crw--- 1 vince users - 5, 2 Jul 1 08:26 /dev/ttyp2 crw--w 1 vince users - 5, 3 Jun 30 16:18 /dev/ttyp3 crw--w 1 vince users - 5, 4 Jun 29 00:35 /dev/ttyp4 crw--w 1 vince users - 5, 5 Jun 29 00:35 /dev/ttyp5 crw--w 1 vince users - 5, 6 Jun 29 00:35 /dev/ttyp6 crw--w 1 vince users - 5, 7 Jun 29 00:35 /dev/ttyp7 crw--w 1 vince users - 5, 8 Jun 29 00:35 /dev/ttyp8 crw--w 1 vince users - 5, 9 Jul 1 08:18 /dev/ttyp9 crw--w 1 vince users - 5, 10 Jul 1 08:28 /dev/ttypa As soon as I changed the ttyp1 to the group tty, everything started working correctly. So it seems that the /dev has the incorrect group whe n the tty is from screen. No problems here. cwsys$ ll ttyp? crw-rw-rw- 1 root wheel5, 0 Jun 26 13:19 ttyp0 crw--w 1 cytty 5, 1 Jul 1 10:05 ttyp1 crw--w 1 cytty 5, 2 Jul 1 10:05 ttyp2 crw--w 1 cytty 5, 3 Jul 1 10:05 ttyp3 crw--w 1 cytty 5, 4 Jul 1 10:05 ttyp4 crw--w 1 cytty 5, 5 Jul 1 10:05 ttyp5 crw--w 1 cytty 5, 6 Jul 1 10:05 ttyp6 crw--w 1 cytty 5, 7 Jul 1 10:05 ttyp7 crw--w 1 cytty 5, 8 Jul 1 10:05 ttyp8 crw--w 1 cytty 5, 9 Jul 1 10:05 ttyp9 crw--w 1 cytty 5, 10 Jul 1 10:05 ttypa crw--w 1 cytty 5, 11 Jul 1 10:05 ttypb crw--w 1 cytty 5, 12 Jul 1 10:05 ttypc crw--w 1 cytty 5, 13 Jul 1 10:05 ttypd crw--w 1 cytty 5, 14 Jul 1 10:05 ttype crw--w 1 cytty 5, 15 Jul 1 10:05 ttypf cwsys$ I have a locally built package here at http://komquats.com/pkg/screen-3. 9.15_1.tbz/. It's built from the stock 3.9.15_1. See if it makes a difference. Other than that it could be a myriad of configuration things on your system. Anyhow give it a try and let us know your results. I tried your package with the extracted bin/screen binary and yours work correctly. [EMAIL PROTECTED] [11:20am][~] tty /dev/ttypb [EMAIL PROTECTED] [11:20am][~] dir /dev/ttypb crw--w 1 vince tty - 5, 11 Jul 1 11:20 /dev/ttypb [EMAIL PROTECTED] [11:20am][~] Message from [EMAIL PROTECTED] at 11:20 on 2003/07/01 ... talk: connection requested by [EMAIL PROTECTED] talk: respond with: talk [EMAIL PROTECTED] [EMAIL PROTECTED] [11:20am][~] So this means that the configure script might have something configured incorrectly. I just tried to rebuild the port and it's the configure script which generates the config.h with the wrong PTYGROUP. /* * define PTYMODE if you do not like the default of 0622, which allows * public write to your pty. * define PTYGROUP to some numerical group-id if you do not want the * tty to be in your group. * Note, screen is unable to change mode or group of the pty if it * is not installed with sufficient
DAC960
Hi, I have DAC960 RAID and SCSI CD-ROM. When I boot FreeBSD 4.8 on this machine, then it doesn't want to mount / partition autimatically. I have problems with top, vmstat and memcontrol list command too. triton# top top: nlist failed triton# vmstat vmstat: undefined symbols: _kmemstatistics _bucket _zlist triton# memcontrol list memcontrol: can't size range descriptor array: Operation not supported triton# I attached a dmesg.boot file. Kind regards, Dusan Kozic [EMAIL PROTECTED]Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-RELEASE #0: Thu Apr 3 10:53:38 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz CPU: Pentium/P54C (133.31-MHz 586-class CPU) Origin = GenuineIntel Id = 0x52c Stepping = 12 Features=0x3bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC real memory = 68153344 (66556K bytes) avail memory = 61124608 (59692K bytes) Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 mlx0: Mylex version 2 RAID interface port 0x9000-0x907f irq 15 at device 2.0 on pci0 mlx0: DAC960P/PD, 2 channels, firmware 2.73-0-00, 4MB RAM mlxd0: Mylex System Drive on mlx0 mlxd0: 32768MB (67108864 sectors) RAID 5 (online) fxp0: Intel Pro 10/100B/100+ Ethernet port 0x9080-0x90bf mem 0x4000-0x4001,0x4002-0x40020fff irq 14 at device 4.0 on pci0 fxp0: Ethernet address 00:02:b3:bc:c3:cb inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI to ISA bridge (vendor=1014 device=000a) port 0x500-0x507 at device 6.0 on pci0 isa0: ISA bus on isab0 chip1: PCI to MCA bridge (vendor=1014 device=0020) port 0-0x1ff,0x510-0x517,0x508-0x50f at device 8.0 on pci0 pci0: Cirrus Logic GD5430 SVGA controller at 10.0 irq 0 ahc0: Adaptec aic7870 SCSI adapter port 0xc00-0xcff mem 0x3000-0x3fff irq 11 at device 12.0 on pci0 aic7870: Wide Channel A, SCSI Id=7, 16/253 SCBs eisa0: EISA bus on motherboard mainboard0: ADP7870 (System Board) on eisa0 slot 0 orm0: Option ROMs at iomem 0xc-0xc7fff,0xc8000-0xc97ff,0xc9800-0xc9fff,0xea000-0xea7ff on isa0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: cannot reserve I/O port range Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: ARCHIVE IBM4326NP/RP !D 5500 Removable Sequential Access SCSI-2 device sa0: 7.812MB/s transfers (7.812MHz, offset 15) Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:/dev/da0s1a cd0 at ahc0 bus 0 target 6 lun 0 cd0: IBM CDRM00203\\000\\000\\000\\000\\000!K BZ26 Removable CD-ROM SCSI-2 device cd0: 5.000MB/s transfers (5.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present ? List valid disk boot devices empty line Abort manual input mountroot 8\^H \^Hufs:/dev/mlxd0s1a Mounting root from ufs:/dev/mlxd0s1a ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Deadlock between background fsck and cvsup, both stuck in snaplk
Hi, I recently reinstalled my scratch box, last time I turned it off, I didn't shut it down nicely so when I booted it today the file systems needed a fsck. While bgfsck was still running I started a cvsup to update /usr/ports/, which ran fine for a while, and then stopped, and now both cvsup and fsck are waiting for snaplk The box is running 5.1-CURRENT as of June 8th When it booted it logged this ... da0 at ahc0 bus 0 target 0 lun 0 da0: IBM DCAS-34330 S65A Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da1 at ahc1 bus 0 target 0 lun 0 da1: IBM DORS-32160W WA6A Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) Mounting root from ufs:/dev/da0s1a WARNING: / was not properly dismounted /: mount pending error: blocks 4 files 0 WARNING: /usr was not properly dismounted /usr: superblock summary recomputed WARNING: /usr/obj was not properly dismounted WARNING: /var was not properly dismounted acquiring duplicate lock of same type: vnode interlock 1st vnode interlock @ /usr/src/sys/ufs/ffs/ffs_snapshot.c:477 2nd vnode interlock @ /usr/src/sys/ufs/ffs/ffs_snapshot.c:480 Stack backtrace: But the backtrace isn't in the output of dmesg nor in /var/log/messages The processes currently waiting for snaplk are olive# ps auxl | grep snaplk root 41 0.0 0.0 0 12 ?? DL8:47PM 0:01.44 (syncer)0 0 0 -4 0 snaplk root 496 0.0 1.5 2280 1848 ?? DN8:49PM 0:08.78 fsck_ufs -p -B / 0 481 0 -4 4 snaplk root 537 0.0 4.2 6192 5280 p0 D 8:53PM 0:34.17 /usr/local/bin/c 0 1 0 -4 0 snaplk root 590 0.0 0.1 328 180 p0 R+9:08PM 0:00.01 grep snaplk 0 520 0 108 0 - Any ideas ? /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: should fdisk -BI still work?
On Tue, 1 Jul 2003, John Hay wrote: fdisk: invalid fdisk partition table found That's not a fatal error, it just means there wasn't a slice table there before you wiped it with -I. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DAC960
On Tue, 1 Jul 2003, Dusan Kozic wrote: I have DAC960 RAID and SCSI CD-ROM. When I boot FreeBSD 4.8 on this machine, then it doesn't want to mount / partition autimatically. Verify /etc/fstab is correct. I have problems with top, vmstat and memcontrol list command too. Are you not using /boot/loader? Or are you using tools leftover from an earlier 4.X install? triton# top top: nlist failed triton# vmstat vmstat: undefined symbols: _kmemstatistics _bucket _zlist triton# memcontrol list memcontrol: can't size range descriptor array: Operation not supported triton# These are the classic symptoms of a world kernel out of sync usually, or lack of use of loader. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DAC960
On Tue, Jul 01, 2003 at 09:25:30PM +0200, Dusan Kozic wrote: Hi, I have DAC960 RAID and SCSI CD-ROM. When I boot FreeBSD 4.8 on this machine, then it doesn't want to mount / partition autimatically. I don't know what this is doing on -current but anyway You don't say what has changed on the machine. Is this a new install? At some point between FreeBSD 2.2 and 4.6 (don't ask) I could install from the CD but not boot off the RAID disk later. Changing a DAC960 BIOS option from 2GB to 8GB made it boot. I have problems with top, vmstat and memcontrol list command too. triton# top top: nlist failed triton# vmstat vmstat: undefined symbols: _kmemstatistics _bucket _zlist triton# memcontrol list memcontrol: can't size range descriptor array: Operation not supported triton# That looks like the mundane kernel/world out of sync. One suggestion based on your dmesg... Have you disabled the bios on your Adaptec SCSI Adapter? If not, it may be loading before the DAC960 bios and only be looking for a bootable disk on that controller. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-RELEASE #0: Thu Apr 3 10:53:38 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz CPU: Pentium/P54C (133.31-MHz 586-class CPU) mlx0: Mylex version 2 RAID interface port 0x9000-0x907f irq 15 at device 2.0 on pci0 mlx0: DAC960P/PD, 2 channels, firmware 2.73-0-00, 4MB RAM mlxd0: Mylex System Drive on mlx0 mlxd0: 32768MB (67108864 sectors) RAID 5 (online) ahc0: Adaptec aic7870 SCSI adapter port 0xc00-0xcff mem 0x3000-0x3fff irq 11 at device 12.0 on pci0 aic7870: Wide Channel A, SCSI Id=7, 16/253 SCBs Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: ARCHIVE IBM4326NP/RP !D 5500 Removable Sequential Access SCSI-2 device sa0: 7.812MB/s transfers (7.812MHz, offset 15) Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:/dev/da0s1a cd0 at ahc0 bus 0 target 6 lun 0 cd0: IBM CDRM00203\\000\\000\\000\\000\\000!K BZ26 Removable CD-ROM SCSI-2 device cd0: 5.000MB/s transfers (5.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present ? List valid disk boot devices empty line Abort manual input mountroot 8\^H \^Hufs:/dev/mlxd0s1a Mounting root from ufs:/dev/mlxd0s1a -- Scott LambertKC5MLE Unix SysAdmin [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ipf and ipnat
Hello I am running ipf and ipnat on CURRENT as of today 4 PM CEST (july 1 2003) and I have enabled the following in my kernel options IPFILTER options IPFILTER_LOG options IPSTEALTH options RANDOM_IP_ID in /etc/rc.conf I have enabled ipf and ipnat according to the handbook when I put this box on the network, all outbound NAT works fine, i,e the MAP statements in /etc/ipnat.rules however the BIMAP statements does not work, a host identified in the BIMAP statement cannot pass through the fw, outbound and cannot be reached inbound from the internet. if I do ipnat -l I can see the MAP and BIMAP statements in the table and ipf is not blocking the packets according to the logs running the exact same config on a STABLE box works fine Have I missed something obvious? Matt Douhan www.fruitsalad.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[-CURRENT tinderbox] failure on ia64/ia64
TB --- 2003-07-01 20:38:30 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2003-07-01 20:38:30 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-01 20:41:35 - building world TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64/src TB --- /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. [...] @DØa0hª 8-ÀÄÀ_: not found : not found : not found : not found 0bÀ x À: not found À: not found À: not found ./mkinit: 16: Syntax error: ( unexpected (expecting )) *** Error code 2 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/bin/sh. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/rescue/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/rescue/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. TB --- 2003-07-01 21:35:39 - /usr/bin/make returned exit code 1 TB --- 2003-07-01 21:35:39 - ERROR: failed to build world TB --- 2003-07-01 21:35:39 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[-CURRENT tinderbox] failure on sparc64/sparc64
TB --- 2003-07-01 21:35:40 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-07-01 21:35:40 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-01 21:38:04 - building world TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. [...] yacc -d /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/arith.y cp y.tab.c arith.c lex -t -8 /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/arith_lex.l arith_lex.c cd /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh; sh mkbuiltins /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/rescue/rescue/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh cc -O -pipe -DSHELL -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh -DRESCUE -c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/mkinit.c cc -O -pipe -DSHELL -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh -DRESCUE -static mkinit.o -o mkinit ./mkinit /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/alias.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/eval.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/exec.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/input.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/jobs.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/options.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/parser.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/redir.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/trap.c /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh/var.c ./mkinit: 1: Syntax error: end of file unexpected *** Error code 2 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/bin/sh. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/rescue/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/rescue/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/rescue. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src. TB --- 2003-07-01 22:23:15 - /usr/bin/make returned exit code 1 TB --- 2003-07-01 22:23:15 - ERROR: failed to build world TB --- 2003-07-01 22:23:15 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated ec-burst.diff patch
Nate Lawson wrote: Also, please report how adding hw.acpi.ec.burst_mode=0 to loader.conf changes things (but turn on hw.acpi.verbose first so we get good msgs). Well with hw.acpi.verbose=1 the messages look like this: Jul 2 00:30:39 lappi kernel: ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR Jul 2 00:30:39 lappi kernel: ACPI-1287: *** Error: Method execution failed [\_SB_.BAT0._BST] (Node 0xc2502700), AE_ERROR Jul 2 00:30:39 lappi kernel: acpi_cmbat0: error fetching current battery status -- AE_ERROR Jul 2 00:30:54 lappi kernel: acpi_ec0: EcCommand: no response to 82 Jul 2 00:30:54 lappi kernel: acpi_ec0: EcCommand: no response to 80 Jul 2 00:30:54 lappi kernel: ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR Jul 2 00:30:54 lappi kernel: ACPI-1287: *** Error: Method execution failed [\_TZ_.TZN0._TMP] (Node 0xc2502b60), AE_ERROR Jul 2 00:30:54 lappi kernel: acpi_tz0: error fetching current temperature -- AE_ERROR Jul 2 00:31:09 lappi kernel: acpi_ec0: EcCommand: no response to 80 Jul 2 00:31:09 lappi kernel: ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR Jul 2 00:31:09 lappi kernel: ACPI-1287: *** Error: Method execution failed [\_SB_.ADP0._PSR] (Node 0xc2502880), AE_ERROR Jul 2 00:31:24 lappi kernel: acpi_ec0: EcCommand: no response to 80 Jul 2 00:31:24 lappi kernel: ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR Jul 2 00:31:24 lappi kernel: ACPI-1287: *** Error: Method execution failed [\_TZ_.TZN0._TMP] (Node 0xc2502b60), AE_ERROR Jul 2 00:31:24 lappi kernel: acpi_tz0: error fetching current temperature -- AE_ERROR Jul 2 00:31:39 lappi kernel: acpi_ec0: EcCommand: no response to 80 Jul 2 00:31:39 lappi kernel: ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR Jul 2 00:31:39 lappi kernel: ACPI-1287: *** Error: Method execution failed [\_SB_.ADP0._PSR] (Node 0xc2502880), AE_ERROR Jul 2 00:31:39 lappi kernel: acpi_ec0: EcCommand: no response to 80 Jul 2 00:31:39 lappi kernel: ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR Jul 2 00:31:39 lappi kernel: ACPI-1287: *** Error: Method execution failed [\_SB_.BAT0._BST] (Node 0xc2502700), AE_ERROR Jul 2 00:31:39 lappi kernel: acpi_cmbat0: error fetching current battery status -- AE_ERROR here is the output of dmesg | egrep acpi_ec0\|EC\ Wait acpi_ec0: embedded controller port 0x66,0x62 on acpi0 EC Waited max 17 cycles, event occurred acpi_ec0: EcCommand: no response to 80 acpi_ec0: EcCommand: no response to 80 [...] acpi_ec0: EcCommand: no response to 80 acpi_ec0: EcCommand: no response to 82 acpi_ec0: EcRead: Failed waiting for EC to send data. acpi_ec0: EcCommand: no response to 80 acpi_ec0: EcCommand: no response to 80 The complete dmesg is available at http://flds.dyndns.org/dmesg . I set hw.acpi.ec.burst_mode=0 in loader.conf but when i was trying to chek if it was set to 0 with sysctl hw.acpi.ec.burst_mode i got : [EMAIL PROTECTED] [~] 15 #sysctl hw.acpi.ec.burst_mode sysctl: unknown oid 'hw.acpi.ec.burst_mode' Let me know if i can do something else. Regards, flo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cardbus network problem with -current
Can you turn on the following debugging and try again? Also, please post questions relating to cardbus/pccard to mobile@ since I read that more often than I read [EMAIL PROTECTED] Thanks much. hw.cardbus.debug: 1 hw.cardbus.cis_debug: 1 hw.cbb.debug: 1 Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/src/libexec/talkd notification broken on pty's when useris using misc/screen ports in -CURRENT
On Tue, 1 Jul 2003, Cy Schubert wrote: Mine configures as follows: /* * define PTYMODE if you do not like the default of 0622, which allows * public write to your pty. * define PTYGROUP to some numerical group-id if you do not want the * tty to be in your group. * Note, screen is unable to change mode or group of the pty if it * is not installed with sufficient privilege. (e.g. set-uid-root) * define PTYROFS if the /dev/pty devices are mounted on a read-only * filesystem so screen should not even attempt to set mode or group * even if running as root (e.g. on TiVo). */ #define PTYMODE 0620 #define PTYGROUP 4 /* #undef PTYROFS */ What does your /etc/group look like? # $FreeBSD: src/etc/group,v 1.28 2003/04/27 05:49:53 imp Exp $ # wheel:*:0:root,vince daemon:*:1: kmem:*:2: sys:*:3: tty:*:4: operator:*:5:root mail:*:6: bin:*:7: news:*:8: man:*:9: games:*:13: staff:*:20: sshd:*:22: smmsp:*:25: mailnull:*:26: guest:*:31: users:*:32:root bind:*:53: majordom:*:54: uucp:*:66: dialer:*:68: network:*:69: pgsql:*:70: www:*:80: mysql:*:88: nogroup:*:65533: nobody:*:65534: cyrus:*:60: Could send me a copy of /etc/devfs.conf. # Copyright (c) 2003 The FreeBSD Project # All rights reserved. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions # are met: # 1. Redistributions of source code must retain the above copyright # notice, this list of conditions and the following disclaimer. # 2. Redistributions in binary form must reproduce the above copyright # notice, this list of conditions and the following disclaimer in the # documentation and/or other materials provided with the distribution. # # THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND # ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE # ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE # FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL # DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS # OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT # LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF # SUCH DAMAGE. # # $FreeBSD: src/etc/devfs.conf,v 1.1 2003/05/06 01:10:33 dougb Exp $ # These are examples of how to configure devices using /etc/rc.d/devfs. # The first parameter is always the action to take, the second is always the # existing device created by devfs, and the last is what you want to change. # The name of the action is only significant to the first unique character. # # Examples: # Historically X depended on this, but version 4.3.0 doesn't seem to anymore #link ttyv0 vga # Commonly used by many ports #link acd0cdrom # Allow a user in the wheel group to query the smb0 device #perm smb00660 # Allow members of group operator to cat things to the speaker #ownspeaker root:operator #perm speaker 0660 I'd like to see an ls -l of /dev too. [EMAIL PROTECTED] [5:19pm][/usr/ports/misc/screen] /bin/ls -l /dev total 1 crw-r--r-- 1 root operator 117, 0 Jun 29 00:10 acd0 crw-r--r-- 1 root wheel 152, 0 Jun 29 00:10 acpi crw-r- 1 root operator4, 10 Jun 29 00:10 ad0 crw-r- 1 root operator4, 11 Jun 29 00:10 ad0s1 crw-r- 1 root operator4, 12 Jun 28 17:10 ad0s1a crw-r- 1 root operator4, 13 Jun 29 00:10 ad0s1b crw-r- 1 root operator4, 14 Jun 29 00:10 ad0s1c crw-r- 1 root operator4, 15 Jun 28 17:10 ad0s1d crw--- 1 root wheel 148, 0 Jun 29 00:10 agpgart crw-rw-r-- 1 root operator 39, 0 Jun 29 00:10 apm crw--- 1 root operator 159, 0 Jun 29 00:10 ata crw-rw-rw- 1 root wheel 30, 4 Jun 29 00:10 audio0.0 crw-rw-rw- 1 root wheel 30, 0x00010004 Jun 29 00:10 audio0.1 crw-rw-rw- 1 root wheel 30, 0x00020004 Jun 29 00:10 audio0.2 crw-rw-rw- 1 root wheel 21, 0 Jun 29 00:10 bpsm0 crw--- 1 root wheel 0, 0 Jul 1 17:09 console crw--- 1 root wheel 12, 255 Jun 28 17:10 consolectl crw-rw-rw- 1 root wheel 1, 0 Jun 29 00:10 ctty crw-rw 1 uucp dialer 28, 128 Jun 29 00:10 cuaa0 crw-rw 1 uucp dialer 28, 160 Jun 29 00:10 cuaia0 crw-rw 1 uucp dialer 28, 192 Jun 29 00:10 cuala0 crw--- 1 root wheel 173, 0 Jun 29 00:10 devctl cr 1 root wheel 250, 0 Jun 29 00:10 devstat crw-rw-rw- 1 root wheel 30, 3 Jun 29 00:12 dsp0.0 crw-rw-rw- 1 root wheel 30, 0x00010003 Jun 29 00:10 dsp0.1 crw-rw-rw- 1 root wheel 30, 0x00020003 Jun 29 00:10 dsp0.2 crw-rw-rw- 1 root wheel 30, 5 Jun 29
Re: Updated ec-burst.diff patch
On Wed, 2 Jul 2003, Florian Smeets wrote: I set hw.acpi.ec.burst_mode=0 in loader.conf but when i was trying to chek if it was set to 0 with sysctl hw.acpi.ec.burst_mode i got : [EMAIL PROTECTED] [~] 15 #sysctl hw.acpi.ec.burst_mode sysctl: unknown oid 'hw.acpi.ec.burst_mode' It's a tunable, not a sysctl. So you can only set it in loader.conf. Are there any messages when you boot with that in your loader.conf? Would you please post a separate dmesg for that case? Thanks, Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [acpi-jp 2363] Updated ec-burst.diff patch
Hi Nate, From: Nate Lawson [EMAIL PROTECTED] Date: Tue, 1 Jul 2003 01:07:53 -0700 ::Please download and try the new version. It correctly implements burst ::mode to the best of the 2.0 spec. Like the previous message, please ::report the appropriate dmesgs (acpi_ec0* and EC Waited*) and any ::errors or regression. I've tested du -a / while plugging/unplugging the ::power cable on my laptop many times with no errors. I Just tested it on my Vaio Z505V/BP, and seems to work just fine :) FYI, % dmesg | egrep acpi_ec0\|EC\ Wait acpi_ec0: embedded controller port 0x66,0x62 on acpi0 EC Waited max 7 cycles, event occurred % Regards, Haro =-- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Internet Solution Dept., Kubota Graphics Technologies Inc. /|\ |_| |_|_| 2-8-8 Shinjuku Shinjuku-ku Tokyo 160-0022, Japan Tel: +81-3-3225-0767 Fax: +81-3-3225-0740 Email: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Current Courier-mta
Hi, I wonder if we can hope to get a current courier-mta in ports, or whats the status on that. thx alot -- Christophe Zwecker mail: [EMAIL PROTECTED] Hamburg, Germanyfon: +49 179 3994867 http://www.zwecker.de Who is General Failure ? And why is he reading my disk ?? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
p5-GD-1.41 wont build
Hi, when trying to build above I get this: === Building for p5-GD-1.41 cc -c -I/usr/local/include -I/usr/local/include/gd -I/usr/local/include/freetype -I@@X11BASE@@/include -I@@X11BASE@@/include/X11 -O -pipe -mcpu=pentiumpro -O -pipe -mcpu=pentiumpro-DVERSION=\1.41\ -DXS_VERSION=\1.41\ -DPIC -fPIC -I/usr/local/lib/perl5/5.6.1/mach/CORE -DHAVE_JPEG -DHAVE_TTF -DHAVE_XPM GD.c GD.xs: In function `newDynamicCtx': GD.xs:342: structure has no member named `free' GD.xs: In function `XS_GD__Image_newFromPngData': GD.xs:395: structure has no member named `free' GD.xs: In function `XS_GD__Image_newFromGdData': GD.xs:412: structure has no member named `free' GD.xs: In function `XS_GD__Image_newFromGd2Data': GD.xs:429: structure has no member named `free' GD.xs: In function `XS_GD__Image_newFromJpegData': GD.xs:472: structure has no member named `free' GD.xs: In function `XS_GD__Image_newFromWBMPData': GD.xs:494: structure has no member named `free' *** Error code 1 any clue whats going wrong here ? thx for any hints -- Christophe Zwecker mail: [EMAIL PROTECTED] Hamburg, Germanyfon: +49 179 3994867 http://www.zwecker.de Who is General Failure ? And why is he reading my disk ?? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: p5-GD-1.41 wont build
From: Christophe Zwecker [EMAIL PROTECTED] any clue whats going wrong here ? One of the port-commiters updated the gd 1.x port to gd 2.0.15. This has been backed out as of 8 hours ago. Uninstall gd-2.0.15 and re-cvsup your ports collection. Scot ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
BIOCSSEESENT ioctl on 5.1 ...
Question,
Is there somthing magic about setting this flag? I wrote a small program
( built on 5.1 ) that uses the bpf to read broadcast packets off a local
private network, forward them to a peer ( over IPSEC ) who in turn drops them
onto its private network ( and visa-versa ). To prevent looping, I was hoping
to set the BIOCSSEESENT flag on the fd. Unfortunately, when this option is
set I no longer receive any packets on the interface. Here is the relevent
code.
// open the berkley packet filter device
int32_t hbpf;
int32_t mnum = 0;
char device[ 25 ];
do
{
sprintf( device,/dev/bpf%d, mnum );
mnum++;
hbpf = open( device, O_RDWR );
}
while( hbpf 0 errno == EBUSY );
if( hbpf == -1 )
{
printf( failed to open a packet filter device\n );
printf( exiting ...\n );
return -1;
}
printf( using filter device '%s'\n, device );
// assign the filter to a network device
struct ifreq ifr;
strcpy( ifr.ifr_name, config.get_service_iface() );
if( ioctl( hbpf, BIOCSETIF, ( uint32_t ) ifr ) == -1 )
{
printf( unable to assign filter to network device
\'%s\'\n,
ifr.ifr_name );
printf( exiting ... );
return -1;
}
printf( using network device \'%s\'\n, ifr.ifr_name );
// dont buffer packet data
uint32_t value = 1;
if( ioctl( hbpf, BIOCIMMEDIATE, value ) == -1 )
{
printf( unable to set BIOCIMMEDIATE option for filter
device\n );
printf( exiting ...\n );
return -1;
}
// use promiscuous mode
if( ioctl( hbpf, BIOCPROMISC, value ) == -1 )
{
printf( unable to set BIOCPROMISC option for filter
device\n );
printf( exiting ...\n );
return -1;
}
// use non-blocking io
if( ioctl( hbpf, FIONBIO, value ) == -1 )
{
printf( unable to set FIONBIO option for filter device\n
);
printf( exiting ...\n );
return -1;
} // disable header complete mode
if( ioctl( hbpf, BIOCSHDRCMPLT, value ) == -1 )
{
printf( unable to set BIOCGHDRCMPLT option for filter
device\n );
printf( exiting ...\n );
return -1;
}
// don't return localy generated packets
value = 0;
if( ioctl( hbpf, BIOCSSEESENT, value ) == -1 )
{
printf( unable to set BIOCGSEESENT option for filter
device\n );
printf( exiting ...\n );
return -1;
}
// get the filter buffer size
int32_t buff_size;
if( ioctl( hbpf, BIOCGBLEN, buff_size ) == -1 )
{
printf( unable to obtain filter buffer size\n );
printf( exiting ...\n );
return -1;
}
// setup our bpf filter machine data
uint32_t ins_count = 8;
uint32_t ins_index = 0;
struct bpf_insn * insns = new struct bpf_insn[ ins_count ];
if( !insns )
{
printf( unable to alloc filter macine data\n );
printf( exiting ...\n );
return -1;
} insns[ ins_index ].code = BPF_LD+BPF_H+BPF_ABS; //
load data ( half word )
insns[ ins_index ].k = 12; // offset (
protocol )
ins_index++;
insns[ ins_index ].code = BPF_JMP+BPF_JEQ+BPF_K; // cmp
equality and jmp
insns[ ins_index ].jt = 0; // true
offset
insns[ ins_index ].jf = 5; // false
offset
insns[ ins_index ].k = 0x0800; // value
ins_index++;
insns[ ins_index ].code = BPF_LD+BPF_B+BPF_ABS; // load data
( byte )
insns[ ins_index ].k = 23; // offset (
transport type )
ins_index++;
insns[ ins_index ].code = BPF_JMP+BPF_JEQ+BPF_K; // cmp
equality and jmp
insns[ ins_index ].jt = 0; // true
offset
insns[ ins_index ].jf = 3; // false
offset
insns[ ins_index ].k = 0x11; // value
ins_index++;
/*
* TODO : check for a matching port
*/
insns[ ins_index ].code = BPF_LD+BPF_W+BPF_ABS; // load data
( word )
insns[ ins_index ].k = 30; // offset (
destination addre
ins_index++;
insns[ ins_index ].code = BPF_JMP+BPF_JEQ+BPF_K; // cmp
equality and jmp
insns[ ins_index ].jt = 0; // true
offset
insns[ ins_index ].jf = 1; // false
offset
insns[ ins_index ].k = 0x; // value
ins_index++;
insns[ ins_index ].code = BPF_RET+BPF_K; // return (
passed )
insns[ ins_index ].k = ( u_int ) -1; // accept
byte count ( everyt
ins_index++;
insns[ ins_index ].code = BPF_RET+BPF_K; // return (
failed )
Re: BIOCSSEESENT ioctl on 5.1 ...
Woops, Please disregard the previous post ... amature programmer at play. Can an ioctl call return before processing the request? When I started using seperate variables for the int=1 and int=0 ioctl values, everything works fine. -Matthew Question, Is there somthing magic about setting this flag? .. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1-RELEASE Windows XP dual-boot issues
On 01 Jul 2003 18:12:20 +, Scott Reese [EMAIL PROTECTED] wrote: On Tue, 2003-07-01 at 01:34, Jud wrote: to boot FreeBSD with no problems at all, but when I went to boot up Windows, I received the dreaded 'NTLDR missing' message. [grub stuff snipped] A few comments about the thread so far: ISTM the easiest thing for you to do is install booteasy on *both* drives. That should work fine. I don't think that will make any difference in my case. Costs nothing to try, eh? Since you're planning to Win-ize the MBR anyway. Just a recap: I have two physical drives (ad0, ad1). XP is on ad0 (the first drive) and FreeBSD is on ad1 (the second drive). I have been using booteasy on the *first* drive with a regular mbr on the second and that worked just fine until I did a fresh install of 5.1. What I'm trying to get at is how best to re-install windows (or work around the 'NTLDR is missing' message) *without* then rendering my FreeBSD install unbootable because we all know that Windows overwrites the mbr by default because it thinks it's supreme ruler of the universe. Short of reinstalling the entire Win OS, you can save time and trouble by booting from your XP CD and electing to repair your XP installation, either automatically or from the console by using the 'fixmbr' and 'fixboot' commands. Or if you happen to have a Win98 rescue floppy hanging around, you can boot off that and do 'fdisk /mbr'. [snip] You may want to have a look at GAG, which is freeware, open source, graphical, and rather automagic. Worked out of the box on my setup, which involves dual booting Win2K and FreeBSD from a RAID0 array. Thanks, I will take a look at it. -Scott Let us know how things turn out. Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
usb video devices
Are there any inexpensive vga out video devices that support FreeBSD and X? Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
features of ICH5/ICH5-R supported in -current or 5.1-RELEASE?
Hi all, I'm wondering if some of the features of the ICH5 found in the springdale and canterwood platforms (i865/i875) are currently supported in either 5.1-RELEASE or -CURRENT? I've read through some of the ATA code commits and see a few comments related to ICH5 and I believe I spotted where the plain ATA controller is recognized (and in theory fully supported as this shouldn't have changed from ICH4). But I still have questions about the following: 1) S-ATA: Is the S-ATA controller in ICH5 supported and if not, are there plans to support it? If not, is the problem documentation or hardware to test with? 2) RAID: The ICH5-R supports RAID0 (and I guess RAID1 as well). Will this be a supported platform for RAID? 3) Is the 3COM 3C940 Gigabit ethernet card supported? I checked in the 4.8's and 5.1's hardware release notes but couldn't find mention of it. Thanks for any information, -Jr ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb video devices
On Tue, Jul 01, 2003 at 09:25:38PM -0600, M. Warner Losh wrote: Are there any inexpensive vga out video devices that support FreeBSD and X? And while we are at it, any camera devices? I am talking about webcams for both netmeeting kind of stuff and, well, webcam stuff. greets, t. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
