Error building 5.3-STABLE
Hi folks, With a source of 5minutes ago I get this: cat curses.head curses.h.new AWK=awk _POSIX2_VERSION=199209 sh /usr/src/lib/libncurses/../../contrib/ncurses/include/MKkey_defs.sh /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps curses.h.new cat /usr/src/lib/libncurses/../../contrib/ncurses/include/curses.tail curses.h.new mv -f curses.h.new curses.h sh /usr/src/lib/libncurses/../../contrib/ncurses/include/MKhashsize.sh /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps hashsize.h AWK=awk sh /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKkeys_list.sh /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps | LC_ALL=C sort keys.list awk -f /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps awk -f /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps awk -f /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps awk -f /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps awk -f /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps awk -f /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps awk -f /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps awk -f /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps cat namehdr boolnames boolfnames numnames numfnames strnames strfnames nameftr names.c AWK=awk sh /usr/src/lib/libncurses/../../contrib/ncurses/include/MKncurses_def.sh /usr/src/lib/libncurses/../../contrib/ncurses/include/ncurses_defs ncurses_def.h sed /usr/src/lib/libncurses/../../contrib/ncurses/include/MKterm.h.awk.in MKterm.h.awk -e /@NCURSES_MAJOR@/s%%5% -e /@NCURSES_MINOR@/s%%2% -e /@NCURSES_CONST@/s%%const% -e /@NCURSES_XNAMES@/s%%1% awk -f MKterm.h.awk /usr/src/lib/libncurses/../../contrib/ncurses/include/Caps term.h.new sh /usr/src/lib/libncurses/../../contrib/ncurses/include/edit_cfg.sh /usr/src/lib/libncurses/ncurses_cfg.h term.h.new ** edit: HAVE_TCGETATTR 1 ** edit: HAVE_TERMIOS_H 1 ** edit: HAVE_TERMIO_H 0 ** edit: BROKEN_LINKER 0 mv -f term.h.new term.h sed /usr/src/lib/libncurses/../../contrib/ncurses/include/termcap.h.in termcap.h -e /@NCURSES_MAJOR@/s%%5% -e /@NCURSES_MINOR@/s%%2% -e /@NCURSES_CONST@/s%%const% -e /@NCURSES_OSPEED@/s%%short% sed /usr/src/lib/libncurses/../../contrib/ncurses/include/unctrl.h.in unctrl.h -e /@NCURSES_MAJOR@/s%%5% -e /@NCURSES_MINOR@/s%%2% cc -o make_keys -O -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -DTERMIOS /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/make_keys.c /usr/obj/usr/src/i386/usr/bin/ld: cannot find -lc *** Error code 1 Stop in /usr/src/lib/libncurses. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Cheers, Jonathan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Booting 5.3R on second disk using NTLDR
Hello. I've been struggling with a dual boot setup for the best part of two days here, and I'm not going to go outline the hazzles I've been through. This is where I am now: ad0 = Windows XP Professional ad1 = FreeBSD 5.3-RELEASE Both OSs were installed from scratch, and ad0 and ad1 are set to master and slave respectively. No cable select. I did the installation in this order: 1) Make sure ad0 is the only connected disk. 2) Install Windows XP Professional on it. 3) Make sure ad1 is the only connected disk. 3) Install a Standard FreeBSD installation. This because I'm in a paranoid state by now, so I want to make sure Windows don't mess the FreeBSD disk up (and vice versa by user error). During FreeBSD installation, I choose Install a standard MBR (no boot manager), I then booted the system with the kernel from the CD and the root from my new install, by doing boot -a and then specify ufs:ad1s1a as my root. When 5.3 was booted, I then did: 1) dd if=/dev/ad1s1 of=/tmp/bootsect.bsd bs=512 count=1 2) scp /tmp/bootsect.bsd other_host:/tmp 3) Halt the system 4) Connect ad0 5) Boot Windows XP 6) scp other_host:/tmp/bootsect.bsd c:\ 7) Append this to c:\boot.ini: c:\bootsect.bsd = FreeBSD 5.3-RELEASE 8) Reboot and choose FreeBSD 5.3-RELEASE at the NTLDR boot menu 9) Boot error Anyone know what I've done wrong? I've followed the short instructions at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NT-BOOTLOADER and I've Googled and read both boot(8) and boot0cfg(8) to look for something that I've done wrong or something that could help me get this to work. It was a long time since I set up a dual boot, but I need it this way because it's my parents new computer, and me and my brother want something else but Windows when we're there. I remember setting up NTLDR to boot Linux years ago, but then it was on the same disk. Thanks a lot for any answers! Best regards, Aron Stansvik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise FastTrak Tx4200 FreeBSD 5.3
Mark Kirkwood said: fredrik engberg wrote: Hey. I'm having some trouble getting my promise fasttrak tx4200 (PDC20619) to work on FreeBSD 5.3. It wont show up on dmesg or when i use atacontrol list. when i use pciconf -lv it give me this. [EMAIL PROTECTED]:8:0: class=0x010400 card=0x3519105a chip=0x3519105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' class = mass storage subclass = RAID Interesting - PDC20619 is listed in ata(4) manual page for 5.3 Release, so one would expect it to show up. From a quick look in sys/ata and Google the PDC20619 seems to be the TX4000 rather than the TX4200. Promise's website is, ... less than helpful in finding these sorts of things out. Cheers, Dominic Not sure if this is very useful, but here is what I see for a TX2000: $ pciconv -lv [EMAIL PROTECTED]:20:0: class=0x010485 card=0x4d68105a chip=0x6269105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20271 FastTrak TX2000 EIDE controller' class= mass storage subclass = RAID $ dmesg atapci1: Promise PDC20271 UDMA133 controller port 0xec00-0xec0f,0xe800-0xe803,0xe400-0xe407,0xe000-0xe003,0xdc00-0xdc07 mem 0xd900-0xd900 irq 11 at device 20.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 regards Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-STABLE failing to read 4.x-Stable hdd
What about fdisk? Is the 4.x one dangerously dedicated? I have a lot of data on the ad1 hdd from webpages i was hosting .. admittedly i got most backed up .. but there was a lot of other important data i cant re-retrieve without severe cost to myself which id rather very much not have to do. -- Yours Sincerely Shinjii http://www.shinji.nq.nu ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-STABLE failing to read 4.x-Stable hdd
I didn't suggest you trash it I just want to know if it was setup as dangerously dedicated, and what the output of the fdisk command on both drives is.. Soz mis understood.. *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 234436482 (114470 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED *** Working on device /dev/ad1 *** parameters extracted from in-core disklabel are: cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 234436482 (114470 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED -- Yours Sincerely Shinjii http://www.shinji.nq.nu ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
GMIRROR can be destroyed by ordinary users
Dear list, dear Pawel, I think it's a big error that ordinary users can issue a 'gmirror stop /dev/mirrir/sample' with success! Thanks, -Harry ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GMIRROR can be destroyed by ordinary users
On 2005.01.08 15:32:22 +0100, Emanuel Strobl wrote: Dear list, dear Pawel, I think it's a big error that ordinary users can issue a 'gmirror stop /dev/mirrir/sample' with success! Are you sure about that? I can't do it on my test system: [EMAIL PROTECTED]:~] gmirror stop /dev/mirror/sys0 Permission denied -- Simon L. Nielsen pgpUzXiw1H0rY.pgp Description: PGP signature
machine locks with PF (without using user dependent rules)
Dear all,
my machine hard locks with the attached ruleset.
If I set debug.mpsafenet to 0 everything is fine. This was a wild guess from
me, I could nowhere find the info that PF needs this tweaking and I think
it's not intended, otherwise it would be done in rc.conf e.g.
I read about user depending rules in IPFW and that one has to disable
mpsafenet, but I'm not using user based rules in my PF config!
Unfortunately this machine is a CF-Card based Router wher I cannot debug
anything, perhaps I can bring a witness-kernel on it, please tell me if this
problem is new to you and if I should do that.
Best regards,
-Harry
pf.conf: (note that the interface names are changed, so fxp0 is SDSL e.g.)
lan_net=172.23.0.0/16
by_net=192.168.0.0/24
sdsl_net=a.b.c.d/29
sdsl_addr=a.b.c.d
lan_addr=172.23.0.1
#pppoe_addr=10.0.0.1
by_addr=192.168.0.1
proxy=a.a.a.a
mta=b.b.b.b
dns=c.c.c.c
web=d.d.d.d
dns2=10.0.0.2
set block-policy return
scrub in all
nat on SDSL from $lan_net to !$sdsl_net - $sdsl_addr
rdr inet proto tcp from 62.245.232.135 to $sdsl_addr port 3389 - 172.23.2.1
port 3389
block in all
block out all
pass in on lo0 all
pass out on lo0 all
pass in on LAN from $lan_net to any keep state
pass in on SDSL from 62.245.232.135 to any keep state
pass in on SDSL proto tcp from any to $proxy port { 22, 80, 443 } keep state
pass in on SDSL proto tcp from any to $mta port 25 keep state
pass in on SDSL proto { udp, tcp } from any to $dns port 53 keep state
pass in on SDSL proto tcp from any to $web port { 80, 443 } keep state
pass out on SDSL from $sdsl_net keep state
pass out on LAN from $lan_addr to $lan_net keep state
P.S.: Why do I need the second line with the following rule? Shouldn't the
'keep state' open the internal interface for outgoing packets from the given
IP?
pass in on SDSL from 62.245.232.135 to any keep state
pass out on LAN from 62.245.232.135 to 172.23.2.1
pgpCLXDB1D0Gr.pgp
Description: PGP signature
syslog problem
Building stable I have this problem === lib/libc cc -pg -O -pipe -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386 -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DHESIOD -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libc/gen/syslog.c -o syslog.po /usr/src/lib/libc/gen/syslog.c: In function `connectlog': /usr/src/lib/libc/gen/syslog.c:336: error: `_PATH_LOG_PRIV' undeclared (first use in this function) /usr/src/lib/libc/gen/syslog.c:336: error: (Each undeclared identifier is reported only once /usr/src/lib/libc/gen/syslog.c:336: error: for each function it appears in.) *** Error code 1 Stop in /usr/src/lib/libc. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. this doing make buildworld anyone has some ideas? thanks Rick ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GMIRROR can be destroyed by ordinary users
Am Samstag, 8. Januar 2005 15:41 schrieb Simon L. Nielsen: I think it's a big error that ordinary users can issue a 'gmirror stop /dev/mirrir/sample' with success! Are you sure about that? I can't do it on my test system: [EMAIL PROTECTED]:~] gmirror stop /dev/mirror/sys0 Permission denied I'm quiet sure because I accidentally did it once, but unfortnately now I don't have a test machine. The only not so ordinary about my user is that it's in the group wheel. If you have a test machine, could you find out if that's the error? Thanks, -Harry pgpfrTVwJTank.pgp Description: PGP signature
Re: Booting 5.3R on second disk using NTLDR (Impossible?)
I did some in the comp.unix.bsd.freebsd news group, and I found some people with the same problem. I'm suspecting that it is impossible to boot FreeBSD by using NTLDR to load the FreeBSD boot sector from a file when FreeBSD is placed on a second disk. Can anyone confirm that this is the case? (the news group postings were very old). And why is it so? Thanks for any answers. Aron On Sat, 8 Jan 2005 11:56:09 +0100, Aron Stansvik [EMAIL PROTECTED] wrote: Hello. I've been struggling with a dual boot setup for the best part of two days here, and I'm not going to go outline the hazzles I've been through. This is where I am now: ad0 = Windows XP Professional ad1 = FreeBSD 5.3-RELEASE Both OSs were installed from scratch, and ad0 and ad1 are set to master and slave respectively. No cable select. I did the installation in this order: 1) Make sure ad0 is the only connected disk. 2) Install Windows XP Professional on it. 3) Make sure ad1 is the only connected disk. 3) Install a Standard FreeBSD installation. This because I'm in a paranoid state by now, so I want to make sure Windows don't mess the FreeBSD disk up (and vice versa by user error). During FreeBSD installation, I choose Install a standard MBR (no boot manager), I then booted the system with the kernel from the CD and the root from my new install, by doing boot -a and then specify ufs:ad1s1a as my root. When 5.3 was booted, I then did: 1) dd if=/dev/ad1s1 of=/tmp/bootsect.bsd bs=512 count=1 2) scp /tmp/bootsect.bsd other_host:/tmp 3) Halt the system 4) Connect ad0 5) Boot Windows XP 6) scp other_host:/tmp/bootsect.bsd c:\ 7) Append this to c:\boot.ini: c:\bootsect.bsd = FreeBSD 5.3-RELEASE 8) Reboot and choose FreeBSD 5.3-RELEASE at the NTLDR boot menu 9) Boot error Anyone know what I've done wrong? I've followed the short instructions at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NT-BOOTLOADER and I've Googled and read both boot(8) and boot0cfg(8) to look for something that I've done wrong or something that could help me get this to work. It was a long time since I set up a dual boot, but I need it this way because it's my parents new computer, and me and my brother want something else but Windows when we're there. I remember setting up NTLDR to boot Linux years ago, but then it was on the same disk. Thanks a lot for any answers! Best regards, Aron Stansvik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GMIRROR can be destroyed by ordinary users
On 2005.01.08 15:49:16 +0100, Emanuel Strobl wrote: Am Samstag, 8. Januar 2005 15:41 schrieb Simon L. Nielsen: I think it's a big error that ordinary users can issue a 'gmirror stop /dev/mirrir/sample' with success! Are you sure about that? I can't do it on my test system: [EMAIL PROTECTED]:~] gmirror stop /dev/mirror/sys0 Permission denied I'm quiet sure because I accidentally did it once, but unfortnately now I don't have a test machine. The only not so ordinary about my user is that it's in the group wheel. If you have a test machine, could you find out if that's the error? My user was also in wheel so that should not be the problem. If your user is in operator it might be another matter though (new test): [EMAIL PROTECTED]:~] id uid=2000(simon) gid=2000(simon) groups=2000(simon), 0(wheel), 5(operator), 68(dialer) [EMAIL PROTECTED]:~] ll /dev/mirror/sys0 crw-r- 1 root operator 233, 3 Jan 6 11:23 /dev/mirror/sys0 [EMAIL PROTECTED]:~] gmirror stop sys0 Cannot destroy device sys0 (error=16). [EMAIL PROTECTED]:~] gmirror stop -f sys0 hang I don't have a console on the system right now but I assume it got unhappy that I pulled the device under the file system :-). I'm not really sure it is expected that you can do that when being in the operator group. -- Simon L. Nielsen pgp73c4Zt8mCM.pgp Description: PGP signature
Re: Booting 5.3R on second disk using NTLDR (Impossible?)
Aron Stansvik wrote: I did some in the comp.unix.bsd.freebsd news group, and I found some people with the same problem. I'm suspecting that it is impossible to boot FreeBSD by using NTLDR to load the FreeBSD boot sector from a file when FreeBSD is placed on a second disk. Can anyone confirm that this is the case? (the news group postings were very old). And why is it so? Thanks for any answers. Aron No, it's not impossible. Unfortunately, I don't recall exactly how I did it, but the boot sector file that I used at the time is at http://people.freebsd.org/~scottl/bootsect.bsd.tgz. I don't know if it will work for you, but it's worth a try. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: syslog problem
On Sat, Jan 08, 2005 at 07:49:10AM -0700, RJ45 wrote: Building stable I have this problem /usr/src/lib/libc/gen/syslog.c:336: error: `_PATH_LOG_PRIV' undeclared I guess that you are building RELENG_5, rather than RELENG_4? The error suggests that either /usr/src/sys/sys/syslog.h is out of date (it should define _PATH_LOG_PRIV) or that you accidently did a make rather than make buildworld (in which case it is picking up the old syslog.h header in /usr/include). If you're trying to compile RELENG_4, then you probably have a mix of FreeBSD 4 and 5 sourcecode. David. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: machine locks with PF (without using user dependent rules)
On Sat, 8 Jan 2005, Harald Schmalzbauer wrote:
my machine hard locks with the attached ruleset. If I set
debug.mpsafenet to 0 everything is fine. This was a wild guess from me,
I could nowhere find the info that PF needs this tweaking and I think
it's not intended, otherwise it would be done in rc.conf e.g.
I read about user depending rules in IPFW and that one has to disable
mpsafenet, but I'm not using user based rules in my PF config!
Unfortunately this machine is a CF-Card based Router wher I cannot debug
anything, perhaps I can bring a witness-kernel on it, please tell me if
this problem is new to you and if I should do that.
I've CC'd Max Laier due to his extensive work with pf on FreeBSD. I think
a WITNESS+INVARIANTS kenrel would be quite helpful, if you could.
Thanks,
Robert N M Watson
Best regards,
-Harry
pf.conf: (note that the interface names are changed, so fxp0 is SDSL e.g.)
lan_net=172.23.0.0/16
by_net=192.168.0.0/24
sdsl_net=a.b.c.d/29
sdsl_addr=a.b.c.d
lan_addr=172.23.0.1
#pppoe_addr=10.0.0.1
by_addr=192.168.0.1
proxy=a.a.a.a
mta=b.b.b.b
dns=c.c.c.c
web=d.d.d.d
dns2=10.0.0.2
set block-policy return
scrub in all
nat on SDSL from $lan_net to !$sdsl_net - $sdsl_addr
rdr inet proto tcp from 62.245.232.135 to $sdsl_addr port 3389 - 172.23.2.1
port 3389
block in all
block out all
pass in on lo0 all
pass out on lo0 all
pass in on LAN from $lan_net to any keep state
pass in on SDSL from 62.245.232.135 to any keep state
pass in on SDSL proto tcp from any to $proxy port { 22, 80, 443 } keep state
pass in on SDSL proto tcp from any to $mta port 25 keep state
pass in on SDSL proto { udp, tcp } from any to $dns port 53 keep state
pass in on SDSL proto tcp from any to $web port { 80, 443 } keep state
pass out on SDSL from $sdsl_net keep state
pass out on LAN from $lan_addr to $lan_net keep state
P.S.: Why do I need the second line with the following rule? Shouldn't the
'keep state' open the internal interface for outgoing packets from the given
IP?
pass in on SDSL from 62.245.232.135 to any keep state
pass out on LAN from 62.245.232.135 to 172.23.2.1
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: machine locks with PF (without using user dependent rules)
On Saturday 08 January 2005 17:52, Robert Watson wrote:
On Sat, 8 Jan 2005, Harald Schmalzbauer wrote:
my machine hard locks with the attached ruleset. If I set
debug.mpsafenet to 0 everything is fine. This was a wild guess from me,
I could nowhere find the info that PF needs this tweaking and I think
it's not intended, otherwise it would be done in rc.conf e.g.
Yes, it is not intended. Please keep in mind that debug.mpsafenet cannot be
alterted at runtime, hence rc.conf would be too late anyway. Just making
that clear.
I read about user depending rules in IPFW and that one has to disable
mpsafenet, but I'm not using user based rules in my PF config!
Unfortunately this machine is a CF-Card based Router wher I cannot debug
anything, perhaps I can bring a witness-kernel on it, please tell me if
this problem is new to you and if I should do that.
I've CC'd Max Laier due to his extensive work with pf on FreeBSD. I think
a WITNESS+INVARIANTS kenrel would be quite helpful, if you could.
Yes, WITNESS would be interesting, though I don't expect to see any LORs, as
this is not an overly complicated ruleset. Actually, I am very surprised
that it does lock up - what hardware is this?
What version of FreeBSD are you running? RELENG_5_3? Could you try to move
`src/sys/contrib/pf' to RELENG_5 instead. There are some bugfixes in there,
that might help you. Specificly there was an endless loop in the state
matching code. Please tell me if that helped.
Best regards,
-Harry
pf.conf: (note that the interface names are changed, so fxp0 is SDSL
e.g.)
lan_net=172.23.0.0/16
by_net=192.168.0.0/24
sdsl_net=a.b.c.d/29
sdsl_addr=a.b.c.d
lan_addr=172.23.0.1
#pppoe_addr=10.0.0.1
by_addr=192.168.0.1
proxy=a.a.a.a
mta=b.b.b.b
dns=c.c.c.c
web=d.d.d.d
dns2=10.0.0.2
set block-policy return
scrub in all
nat on SDSL from $lan_net to !$sdsl_net - $sdsl_addr
rdr inet proto tcp from 62.245.232.135 to $sdsl_addr port 3389 -
172.23.2.1 port 3389
block in all
block out all
pass in on lo0 all
pass out on lo0 all
pass in on LAN from $lan_net to any keep state
pass in on SDSL from 62.245.232.135 to any keep state
pass in on SDSL proto tcp from any to $proxy port { 22, 80, 443 } keep
state pass in on SDSL proto tcp from any to $mta port 25 keep state
pass in on SDSL proto { udp, tcp } from any to $dns port 53 keep state
pass in on SDSL proto tcp from any to $web port { 80, 443 } keep state
pass out on SDSL from $sdsl_net keep state
pass out on LAN from $lan_addr to $lan_net keep state
P.S.: Why do I need the second line with the following rule? Shouldn't
the 'keep state' open the internal interface for outgoing packets from
the given IP?
pass in on SDSL from 62.245.232.135 to any keep state
pass out on LAN from 62.245.232.135 to 172.23.2.1
For the normal forwarding path that's true, but not for the RDR case. You can
use rdr pass to circumvent this.
--
/\ Best regards, | [EMAIL PROTECTED]
\ / Max Laier | ICQ #67774661
X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED]
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
pgpjLwFoZqzll.pgp
Description: PGP signature
Re: Booting 5.3R on second disk using NTLDR (Impossible?)
Aron Stansvik skrev: I did some in the comp.unix.bsd.freebsd news group, and I found some people with the same problem. I'm suspecting that it is impossible to boot FreeBSD by using NTLDR to load the FreeBSD boot sector from a file when FreeBSD is placed on a second disk. Can anyone confirm that this is the case? (the news group postings were very old). And why is it so? No, no, it is not impossible, I am using this method. I used BOOTPART to extract the bootblock and it works very well. Just enter bootpart at Google and it should turn up first in the list. Bernt ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: machine locks with PF (without using user dependent rules)
Am Samstag, 8. Januar 2005 18:24 schrieb Max Laier: Yes, it is not intended. Please keep in mind that debug.mpsafenet cannot be alterted at runtime, hence rc.conf would be too late anyway. Just making that clear. Right, but I meant that at least a note would pop up which tells me to modify loader.conf ar the script would do it itself ;) Like you say, it's not intended :) I've CC'd Max Laier due to his extensive work with pf on FreeBSD. I think a WITNESS+INVARIANTS kenrel would be quite helpful, if you could. Yes, WITNESS would be interesting, though I don't expect to see any LORs, as this is not an overly complicated ruleset. Actually, I am very surprised that it does lock up - what hardware is this? Please find the dmesg at bottom. I'll see that I can get physical access and change the CF-Card with a witness and INVARIANTS kernel What version of FreeBSD are you running? RELENG_5_3? Could you try to move `src/sys/contrib/pf' to RELENG_5 instead. There are some bugfixes in there, that might help you. Specificly there was an endless loop in the state matching code. Please tell me if that helped. I'm running -stable from January 4th, but haven't tried mpsafenet since RELENG_5 from mid Dezember, alas the lockup occured with RELENG_5 short before christmas. Best regards, -Harry [...] P.S.: Why do I need the second line with the following rule? Shouldn't the 'keep state' open the internal interface for outgoing packets from the given IP? pass in on SDSL from 62.245.232.135 to any keep state pass out on LAN from 62.245.232.135 to 172.23.2.1 For the normal forwarding path that's true, but not for the RDR case. You can use rdr pass to circumvent this. Thanks a lot for that hint! phobos:~30: dmesg Copyright (c) 1992-2005 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 5.3-STABLE #4: Tue Jan 4 17:57:01 CET 2005 [EMAIL PROTECTED]:/builder/obj/builder/src/sys/GA-6IEML WARNING: MPSAFE network stack disabled, expect reduced performance. ACPI APIC Table: GBTAWRDACPI Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(TM) CPU1300MHz (1339.16-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b4 Stepping = 4 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 267321344 (254 MB) avail memory = 251875328 (240 MB) ioapic0 Version 2.0 irqs 0-23 on motherboard acpi0: GBT AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0x4000-0x40bf,0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82815 (i815 GMCH) SVGA controller mem 0xe600-0xe607,0xe000-0xe3ff irq 16 at device 2.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 30.0 on pci0 pci1: ACPI PCI bus on pcib1 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xc000-0xc03fmem 0xe500-0xe501,0xe502-0xe503 irq 18 at device 0.0 on pci1 em0: [GIANT-LOCKED] em0: Ethernet address: 00:0e:0c:65:21:40 em0: Speed:N/A Duplex:N/A em1: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xc400-0xc43fmem 0xe506-0xe507,0xe504-0xe505 irq 21 at device 1.0 on pci1 em1: [GIANT-LOCKED] em1: Ethernet address: 00:0e:0c:65:20:6e em1: Speed:N/A Duplex:N/A em2: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xc800-0xc83fmem 0xe50a-0xe50b,0xe508-0xe509 irq 22 at device 2.0 on pci1 em2: [GIANT-LOCKED] em2: Ethernet address: 00:0e:0c:65:21:a5 em2: Speed:N/A Duplex:N/A fxp0: Intel 82801BA/CAM (ICH2/3) Pro/100 Ethernet port 0xcc00-0xcc3f mem 0xe50c-0xe50c0fff irq 20 at device 8.0 on pci1 miibus0: MII bus on fxp0 inphy0: i82562ET 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:20:ed:47:b5:c9 fxp0: [GIANT-LOCKED] isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 UDMA100 controller port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0xd000-0xd01f irq 19at device 31.2 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ichsmb0: Intel 82801BA (ICH2) SMBus controller port 0x5000-0x500f irq 17 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] smbus0: System Management Bus on ichsmb0 smb0: SMBus generic I/O on smbus0
Re: GMIRROR can be destroyed by ordinary users
On Sat, Jan 08, 2005 at 04:33:14PM +0100, Simon L. Nielsen wrote: + I'm not really sure it is expected that you can do that when being in + the operator group. Yes. If you want to change it you should do: # chmod 600 /dev/geom.ctl -- Pawel Jakub Dawidek http://www.wheel.pl [EMAIL PROTECTED] http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! pgpvVPOERXkQT.pgp Description: PGP signature
Re: GMIRROR can be destroyed by ordinary users
On 2005.01.08 19:39:42 +0100, Pawel Jakub Dawidek wrote: On Sat, Jan 08, 2005 at 04:33:14PM +0100, Simon L. Nielsen wrote: + I'm not really sure it is expected that you can do that when being in + the operator group. Yes. If you want to change it you should do: # chmod 600 /dev/geom.ctl Being in the operator group only gives read access to /dev/geom.ctl (it's root:operator crw-r-) so I think it's somewhat counter intuitive that one can stop the mirror without write permission there. Wouldn't it be better to only allow stopping the mirror (and similar) if the user has write access to geom.ctl? phk fixed some similar issues in some of the other GEOM classes not long ago, e.g. geom_bsd.c v. 1.71. -- Simon L. Nielsen pgpMo2UF4bc5i.pgp Description: PGP signature
Re: 5.3-STABLE failing to read 4.x-Stable hdd
On Sat, 2005-Jan-08 16:58:10 +1000, Warren wrote: I didn't suggest you trash it I just want to know if it was setup as dangerously dedicated, and what the output of the fdisk command on both drives is.. Soz mis understood.. Try running disklabel on ad0s1 and ad1s1. Slice numbers should now be treated as mandatory on sliced disks. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GMIRROR can be destroyed by ordinary users
On Sat, 2005-Jan-08 19:54:56 +0100, Simon L. Nielsen wrote: On 2005.01.08 19:39:42 +0100, Pawel Jakub Dawidek wrote: On Sat, Jan 08, 2005 at 04:33:14PM +0100, Simon L. Nielsen wrote: + I'm not really sure it is expected that you can do that when being in + the operator group. Yes. If you want to change it you should do: # chmod 600 /dev/geom.ctl Being in the operator group only gives read access to /dev/geom.ctl (it's root:operator crw-r-) so I think it's somewhat counter intuitive that one can stop the mirror without write permission there. Wouldn't it be better to only allow stopping the mirror (and similar) if the user has write access to geom.ctl? In some ways, it's not. The operator group is intended for users who perform backups (they can read the disks and therefore perform dumps of them). One approach to backing up mirrored systems is to detach one mirror and back it up. Once the backup is finished, you re-attach the mirror. Given this, it is reasonable for operators to be able to fiddle with mirrors. This approach is mostly obsoleted by soft-updates snapshots but is still relevant if: - you aren't running soft-updates for any reason - the filesystem is too dynamic and full for a snapshot to survive for the time needed for a backup. However, overall, I would agree with Simon that being able to make changes to a device that is opened read-only is counter-intuitive. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ucom and sio
M. Warner Losh wrote: In message: [EMAIL PROTECTED] Brandon Fosdick [EMAIL PROTECTED] writes: : Judging from the man page, ucom is limited to acting like a tty with no : support for sio. Is this true? Is there some magic config bit somewhere : that will enable hidden sio support? Ummm, I don't know what you are asking here. ucom supports all the rs232 stuff w/o problem. I use it all the time with my phone to dial into the network. Well, then I must be doing something wrong. The man page for ucom would seem to indicate that it is tty only... The ucom driver attaches to USB modems, serial ports, and other devices that need to look like a tty. The ucom driver shows a behavior like a tty(4). This means that normal programs such as tip(1) or pppd(8) can be used to access the device. If I use tip it works fine. But if I try to write a C program that opens the device it hangs on open, unless I set it to non-blocking. Then open returns and I set it back to blocking then try a read or a write. read() blocks regardless of whether any data has been sent by the other device (a terminal app on my palm pilot for debugging purposes) and write() blocks without sending anything. If I set the device to be non-blocking read() will return the data that was sent by the other device, but write() will still block. Oddly, I get the same behavior on my powerbook, so I thought the adapter was defective. But it works with terminal apps on freebsd, osx and windows, so I'm pretty sure its working. I have no idea what I'm doing wrong though. Once I figure out where I put the code for this thing I'll send the test program I've been using. I always seem to lose something when I travel... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mbufs on 5.3-STABLE possible bug
thanks I will try this out as soon as possible and report back. On Thu, 6 Jan 2005 17:38:54 -0500, Bosko Milekic [EMAIL PROTECTED] wrote: Please try the attached patch. It's not exactly perfect but it might solve your problem. Let me know. -Bosko On Thu, Jan 06, 2005 at 02:12:33PM +, Chris wrote: Hi After reading the release notes and upgrading my server's I had set the following in my /boot/loader.conf. kern.ipc.nmbclusters=0 This is supposed to make the limit to unlimited as I understood from the docs, but a user on one of my server's reported slow download speeds he was testing with wget and fetch, so we compared with another FreeBSD server (5.2.1) on the same network and sure enough there was a massive difference (45mbit on the other server 5mbit on mine), I spent ages checking all my tweaks and changes I made comparing between the 2 server's and ended up checking my loader.conf and tried setting a value and leaving it as auto, both of these changes fixed the download speed issue but setting to 0 introduces the problem. Has anyone else noticed this? Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bosko Milekic [EMAIL PROTECTED] [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Server locks up if more than one jail in running
I have a very bad problem. I need to seetup large number of jails (about 100) to do virtual hosting and i am doing it on 5.3-STABLE (not 5.3-RELEASE, i mean -STABLE which is cvsupped). So, when i setup one jail - everything runs fine for many days. If i setup one more jail or 3 or more - server locks up (freezes, hangs, becomes totally unsresponsive) within 48 hours. Sometime it runs only a couple hours, sometimes almost a couple of days. So, to diagnose the problem i setup a cron process which saves a lot of system statistics every minutes. The last working minute stats are included below as well as basic system configuration. Jails are complete distributions, but very basic services are running: cron, sshd. adjtimezone is disabled. All other records on /etc/crontab are left just like in distro. I really need help with this problem because i canno migrate to 5.3 because of it. And i really need 5.3 because of some new features. Maybe somone could help. SYSTEM: Multiprocessor. Dual XEON 2.667Ghz with HTT. 4GB DDR RAM. RAID 5 (4 SATA disks x 120gb) on 3Ware SATA controller in PCI 64 slot on Supermicro MB. dmesg -- Copyright (c) 1992-2004 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 5.3-STABLE #4: Wed Dec 22 10:25:48 MSK 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/OMNI ACPI APIC Table: PTLTDAPIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.66GHz (2665.92-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf25 Stepping = 5 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 4160225280 (3967 MB) avail memory = 4077481984 (3888 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard ioapic3 Version 2.0 irqs 72-95 on motherboard ioapic4 Version 2.0 irqs 96-119 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTD RSDT on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU (2 Cx states) on acpi0 cpu1: ACPI CPU (2 Cx states) on acpi0 cpu2: ACPI CPU (2 Cx states) on acpi0 cpu3: ACPI CPU (2 Cx states) on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: base peripheral, interrupt controller at device 28.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 29.0 on pci1 pci2: ACPI PCI bus on pcib2 pci1: base peripheral, interrupt controller at device 30.0 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 31.0 on pci1 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0x3000-0x303f mem 0xfc20-0xfc21 irq 28 at device 2.0 on pci3 em0: Ethernet address: 00:30:48:2a:2d:bc em0: Speed:N/A Duplex:N/A em1: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0x3040-0x307f mem 0xfc22-0xfc23 irq 29 at device 2.1 on pci3 em1: Ethernet address: 00:30:48:2a:2d:bd em1: Speed:N/A Duplex:N/A pcib4: ACPI PCI-PCI bridge at device 3.0 on pci0 pci4: ACPI PCI bus on pcib4 pci4: base peripheral, interrupt controller at device 28.0 (no driver attached) pcib5: ACPI PCI-PCI bridge at device 29.0 on pci4 pci5: ACPI PCI bus on pcib5 pci4: base peripheral, interrupt controller at device 30.0 (no driver attached) pcib6: ACPI PCI-PCI bridge at device 31.0 on pci4 pci6: ACPI PCI bus on pcib6 twe0: 3ware Storage Controller. Driver version 1.50.01.002 port 0x4000-0x400f mem 0xfc80-0xfcff irq 72 at device 1.0 on pci6 twe0: [GIANT-LOCKED] twe0: 4 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x2000-0x201f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801CA/CAM (ICH3) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801CA/CAM (ICH3) USB controller USB-B port 0x2020-0x203f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: Intel 82801CA/CAM (ICH3) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801CA/CAM (ICH3) USB controller USB-C port 0x2040-0x205f irq 18 at device 29.2 on pci0 uhci2:
Re: Server locks up if more than one jail in running
On 8 Jan 2005 [EMAIL PROTECTED] wrote: I have a very bad problem. I need to seetup large number of jails (about 100) to do virtual hosting and i am doing it on 5.3-STABLE (not 5.3-RELEASE, i mean -STABLE which is cvsupped). So, when i setup one jail - everything runs fine for many days. If i setup one more jail or 3 or more - server locks up (freezes, hangs, becomes totally unsresponsive) within 48 hours. Sometime it runs only a couple hours, sometimes almost a couple of days. So, to diagnose the problem i setup a cron process which saves a lot of system statistics every minutes. The last working minute stats are included below as well as basic system configuration. Jails are complete distributions, but very basic services are running: cron, sshd. adjtimezone is disabled. All other records on /etc/crontab are left just like in distro. I really need help with this problem because i canno migrate to 5.3 because of it. And i really need 5.3 because of some new features. Maybe somone could help. If you haven't already: could you compile the kernel with options DDB, options KDB, and options BREAK_TO_DEBUGGER and see if you can get into the debugger using a console or (preferably) a serial break? That way we can attempt to diagnose the state of the system once it is wedged. It would also be helpful if you could set the system up to run with options INVARIANTS, which will have some performance impact but turn on additional self-checking in the OS. Finally, depending on whether you can tolerate the performance hit, running with options WITNESS (and options WITNESS_SKIPSPIN to help a bit with performance) will allow us to generate additional debugging information. If you are able to get into the debugger, it would be helpful if you could run the following, and ideal send the output copied using a serial console: - show pcpu show pcpu 0 show pcpu 1 show pcpu 2 show pcpu 3 - ps - show threads - show alllocks # will only work with witness - show lockedvnods This is a substantial volume of output, so if you don't have access to a serial console so you can copy and paste on another box, it may be somewhat inconvenient. Robert N M Watson SYSTEM: Multiprocessor. Dual XEON 2.667Ghz with HTT. 4GB DDR RAM. RAID 5 (4 SATA disks x 120gb) on 3Ware SATA controller in PCI 64 slot on Supermicro MB. dmesg -- Copyright (c) 1992-2004 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 5.3-STABLE #4: Wed Dec 22 10:25:48 MSK 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/OMNI ACPI APIC Table: PTLTDAPIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.66GHz (2665.92-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf25 Stepping = 5 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 4160225280 (3967 MB) avail memory = 4077481984 (3888 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard ioapic3 Version 2.0 irqs 72-95 on motherboard ioapic4 Version 2.0 irqs 96-119 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTD RSDT on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU (2 Cx states) on acpi0 cpu1: ACPI CPU (2 Cx states) on acpi0 cpu2: ACPI CPU (2 Cx states) on acpi0 cpu3: ACPI CPU (2 Cx states) on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: base peripheral, interrupt controller at device 28.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 29.0 on pci1 pci2: ACPI PCI bus on pcib2 pci1: base peripheral, interrupt controller at device 30.0 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 31.0 on pci1 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0x3000-0x303f mem 0xfc20-0xfc21 irq 28 at device 2.0 on pci3 em0: Ethernet address: 00:30:48:2a:2d:bc em0: Speed:N/A Duplex:N/A em1: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0x3040-0x307f mem 0xfc22-0xfc23 irq 29 at device 2.1 on pci3 em1: Ethernet address: 00:30:48:2a:2d:bd em1: Speed:N/A Duplex:N/A pcib4: ACPI PCI-PCI bridge at device 3.0 on
Re: Promise FastTrak Tx4200 FreeBSD 5.3
Dominic Marks wrote: From a quick look in sys/ata and Google the PDC20619 seems to be the TX4000 rather than the TX4200. Promise's website is, ... less than helpful in finding these sorts of things out. You are right (on both counts ...). The lack of detection now makes it bit more sense, implying the chip is *not* one of those in the ata(4) list. I have fired off an email to Promise support asking what the chip PDC20XXX string is for the TX4200. Will post any useful reply obtained. Best wishes Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise FastTrak Tx4200 FreeBSD 5.3
On Jan 7, 2005, at 22:34, fredrik engberg wrote: Hey. I'm having some trouble getting my promise fasttrak tx4200 (PDC20619) to work on FreeBSD 5.3. It wont show up on dmesg or when i use atacontrol list. when i use pciconf -lv it give me this. It's a PDC20571, and support is underway. It will probably work in -CURRENT. Not sure when the support will be finished though. (This goes for FastTrak 579 and TX2200 also) Regards, Frode ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Suspend problem on FreeBSD 5.3-STABLE
Hi, I'm having trouble moving to FreeBSD 5.3-STABLE on my laptop. My problems concern the behaviour of the laptop when suspend/resume is used. Firstly I'd like to congratulate the FreeBSD team on this release. It resolves several problems that I had with FreeBSD 4.x on this hardware so the draw to upgrade to 5-STABLE is very strong. My problems all circulate around suspend/resume. My laptop is a Gateway 450ROG with 512Mb and 40Gb of Disk. I'm running 5.3 Stable cvsuped and built about last week monday. I'm running the GENERIC kernel and my configuration is fairly vanilla. Firstly what is definately broken: Suspend/resume kills the video display and seems to stop the kernel if dri is active under xorg's server. Turning off dri in the X configuration makes this problem go away. I plan to retest this with XFree86 as I believe that this is an Xorg problem. My video Chipset is an ati rage Mobility 7500 and my drm module is /boot/kernel/radeon.ko. Second, what I haven't been able to completely research: The PC card bus dies when on the first suspend resume. There seems to be no way to restart it. The second issue may be a configuration problem. I'm interested in hearing from anyone who is running 5.3-STABLE on a laptop so I can gather a list of all the configuration places and write a webpage on it. Any help anyone can provide would be appreciated. Thanks Chris Hilton -- Chris Hilton chilton-at-vindaloo-dot-com All I was doing was trying to get home from work! -- Rosa Parks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ucom and sio
On Sun, 9 Jan 2005 06:08, Brandon Fosdick wrote: If I use tip it works fine. But if I try to write a C program that opens the device it hangs on open, unless I set it to non-blocking. Then open returns and I set it back to blocking then try a read or a write. read() blocks regardless of whether any data has been sent by the other device (a terminal app on my palm pilot for debugging purposes) and write() blocks without sending anything. If I set the device to be non-blocking read() will return the data that was sent by the other device, but write() will still block. Is it blocking waiting for carrier detect to come up? Try using the cuaNN device instead. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpAQJuTJJ8AJ.pgp Description: PGP signature
Re: ucom and sio
Daniel O'Connor wrote: Is it blocking waiting for carrier detect to come up? Try using the cuaNN device instead. The software in question worked fine using a cuaNN device until said device died. Somebody else mentioned that I could set the device to ignore the carrier detect signal. How do I do that? Is it a flag to tcsetattr() or some kind of ioctl? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.10 kernel panic: Fatal trap 12: page fault while in kernel mode
On Wed, Dec 15, 2004 at 12:42:25PM -0800, Scott Sewall wrote:
I'm running FreeBSD 4.10-RELEASE-p3 that occasionally panics. The panic
occurs seems to happen when I'm running rsync of large directories
possibly in combination with reading or writing to a compact flash
attached to USB.
Having just looked into an identical panic, the problem is an
interface bug between bus_dmamem_alloc() and contigmalloc(). It's
nothing to do with USB and (AFAIK) exists in 4.x, 5.x and 6.x.
The relevant part of my backtrace looks like:
#15 0xc028aaef in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 0,
tf_esi = -980715140, tf_ebp = -1070676940, tf_isp = -1070676996,
tf_ebx = 0, tf_edx = 6867008, tf_ecx = -1056660992, tf_eax = 7261248,
tf_trapno = 12, tf_err = 0, tf_eip = -1072225192, tf_cs = 8,
tf_eflags = 66118, tf_esp = -1065633592, tf_ss = 0})
at /home/src/sys/i386/i386/trap.c:466
#16 0xc0172458 in tsleep (ident=0xc58b797c, priority=4,
wmesg=0xc02bfd27 swwrt, timo=0) at /home/src/sys/kern/kern_synch.c:436
#17 0xc021e60f in swap_pager_putpages (object=0xd03c6e04, m=0xc02ec50c,
count=1, sync=1, rtvals=0xc02ec4b0) at /home/src/sys/vm/swap_pager.c:1431
#18 0xc021ceaf in default_pager_putpages (object=0xd03c6e04, m=0xc02ec50c,
c=1, sync=0, rtvals=0xc02ec4b0) at /home/src/sys/vm/default_pager.c:133
#19 0xc0228ca4 in vm_pageout_flush (mc=0xc02ec50c, count=1, flags=0)
at /home/src/sys/vm/vm_pager.h:147
#20 0xc02285c9 in contigmalloc1 (size=36864, type=0xc02f4340, flags=1, low=0,
high=4294967295, alignment=1, boundary=0, map=0xc03372ac)
at /home/src/sys/vm/vm_page.c:1855
#21 0xc022887f in contigmalloc (size=36864, type=0xc02f4340, flags=1, low=0,
high=4294967295, alignment=1, boundary=0)
at /home/src/sys/vm/vm_page.c:1980
#22 0xc027bd3b in bus_dmamem_alloc (dmat=0xc176b4c0, vaddr=0xc1231a48,
flags=1, mapp=0xc1231a44) at /home/src/sys/i386/i386/busdma_machdep.c:351
#23 0xc0231be2 in usb_block_allocmem (tag=0x0, size=36864, align=1,
dmap=0xc17d8d3c) at /home/src/sys/dev/usb/usb_mem.c:186
...
#35 0xc022d4ea in uhci_intr (arg=0xc104f000)
at /home/src/sys/dev/usb/uhci.c:1175
#36 0xc02841f2 in cpu_idle () at /home/src/sys/i386/i386/machdep.c:1000
Basically, the USB code is trying to allocate ~36KB RAM within an
interrupt handler. usb_block_allocmem() invokes bus_dmamem_alloc()
with BUS_DMA_NOWAIT (advising that sleep()ing is not allowed).
Since more than one page of memory is requested, bus_dmamem_alloc()
uses contigmalloc() to allocate the requested memory. The BUS_DMA_NOWAIT
flag is mapped to M_NOWAIT but contigmalloc() does not support M_NOWAIT.
Unfortunately, I don't know enough about the VM code to be able to
suggest a fix.
--
Peter Jeremy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ucom and sio
On Sun, 9 Jan 2005 11:28, Brandon Fosdick wrote:
Daniel O'Connor wrote:
Is it blocking waiting for carrier detect to come up?
Try using the cuaNN device instead.
The software in question worked fine using a cuaNN device until said
device died.
Somebody else mentioned that I could set the device to ignore the
carrier detect signal. How do I do that? Is it a flag to tcsetattr() or
some kind of ioctl?
Something like this should work..
if ((sfd = open(portfname, O_RDWR | O_NONBLOCK)) == -1) {
fprintf(stderr, Couldn't open serial port - %s\n, strerror(errno));
exit(1);
}
if (tcgetattr(sfd, tp) == -1) {
fprintf(stderr, Couldn't get attr - %s\n, strerror(errno));
exit(1);
}
tp.c_cflag = CLOCAL;
if (tcflush(sfd, TCIOFLUSH) == -1) {
fprintf(stderr, Couldn't flush - %s\n, strerror(errno));
exit(1);
}
if (tcsetattr(sfd, TCSANOW, tp) == -1) {
fprintf(stderr, Couldn't set attrs - %s\n, strerror(errno));
exit(1);
}
ie setting CLOCAL.
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
pgpvjGg4XUwjq.pgp
Description: PGP signature
Re: ucom and sio
Daniel O'Connor wrote: ie setting CLOCAL. That fixed it, thanks. Is it worthwhile to change the ucom man page to not imply that it only works for tty? That led me astray. I think I would have eventually found CLOCAL if I hadn't stopped looking. Or am I the only one that finds it misleading? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.10 kernel panic: Fatal trap 12: page fault while in kernel mode
In message [EMAIL PROTECTED], Peter Jeremy wri tes: On Wed, Dec 15, 2004 at 12:42:25PM -0800, Scott Sewall wrote: I'm running FreeBSD 4.10-RELEASE-p3 that occasionally panics. The panic occurs seems to happen when I'm running rsync of large directories possibly in combination with reading or writing to a compact flash attached to USB. Having just looked into an identical panic, the problem is an interface bug between bus_dmamem_alloc() and contigmalloc(). It's nothing to do with USB and (AFAIK) exists in 4.x, 5.x and 6.x. The USB code is not entirely free of blame here however. It allocates numerous big chunks of contiguous memory for tranfer buffers instead of using the (admittedly limited) scatter-gather capabilities of the USB host controllers. Try applying the change from revision 1.6 of usb_mem.c. This fixed one particularly inefficient memory use behaviour in the USB code. That change is already in 5.x and 6.x, but wasn't merged to 4.x. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/usb_mem.c Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
4.10 vs. 5.3: iswcntrl
I am helping a friend work out problems with the latest release of streamripper. I run 5.3, he runs 4.10. The issue we currently have concerns iswcntrl, or rather the lack of iswcntrl in 4.10. Has thought been given to any sort of MFC to 4.11 or is his only recourse upgrading to 5.3? /Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
How to use growfs on GPT
The topic says all. I'd like to increase the size of the last GPT id (and there's space after the last sector of the last ID). Is it safe to delete it and create a new one with a bigger size? Thanks, -Harry pgphD0rfLb0i0.pgp Description: PGP signature
Re: How to use growfs on GPT
On Jan 8, 2005, at 7:54 PM, Emanuel Strobl wrote: The topic says all. I'd like to increase the size of the last GPT id (and there's space after the last sector of the last ID). Is it safe to delete it and create a new one with a bigger size? The gpt(8) utility does not destroy the partition contents. It is safe to destroy a partition and create a new one that's larger; from a partitioning point of view of course. -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED]
anyone using the umodem(4) module/driver?
If so I'd like to hear success/failure reports.. looking at closing or otherwise acting on: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/39341 however the original submitter has dissappeared. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
